Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

YSlow hit #62

Open
danyj opened this issue Jul 1, 2018 · 1 comment
Open

YSlow hit #62

danyj opened this issue Jul 1, 2018 · 1 comment

Comments

@danyj
Copy link

danyj commented Jul 1, 2018

Original GA is reported as Leverage browser caching on both GT Metrics and pingdom ,
with ga-lite the hit is moved from PageSpeed to YSlow so you are getting hit either way

http://i.prntscr.com/6EctdfeoQnGYtfyyOejfcw.png

Scores with Google Analytics

Speed: 98
YSlow: 86

with ga-lite

Speed: 99
YSlow: 84

@jehna
Copy link
Owner

jehna commented Jul 1, 2018

Allowing caching an analytics response does not make much sense, ad that request should always be guaranteed to hit origin.

Interestingly the official google analytics seems to somehow get around this. Listing some potential theories how this can happen:

  • YSlow has whitelisted/blacklisted the official Google Analytics plugin/request, and leaves it out of the report
  • Official Google Analytics somehow detects that it's running in YSlow and does not run analytics call
  • There's a correct cache header in the endpoint that official Google Analytics uses, but the library breaks cache with some other mean (e.g. url param)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants