Store owner is getting 90/100 desktop 84/100 mobile using Google PageSpeed Insights but
F - First Byte Time
A - Keep-alive Enabled
A- Compressed Transfer
N/A - Compressed Images
C - Cache static content
X - Effective use of CDN
The First Byte Time is 0.980s, while Google PageSpeed Insights is reporting that the server responded in 0.43 seconds. Are these two measurements measuring the same thing?
Some precious milliseconds seem to be tied up in the SSL Negotiation as reported by WebPagetest.org. Since Google wants all SSL does it not ding it like WebPagetest.org seems to be doing?
Also something else I may be seeing in WebPagetesting is that it runs all the code on the page and doesn't differentiate between desktop and mobile like Google does. It almost seems to penalize for the second running.
I have also tested the storefront page at GTmetrix. The site gets a PageSpeed Score of A (94%) but a YSlow Score of C (73%). So which tests should be considered the important ones to pay attention to?
F - First Byte Time
A - Keep-alive Enabled
A- Compressed Transfer
N/A - Compressed Images
C - Cache static content
X - Effective use of CDN
The First Byte Time is 0.980s, while Google PageSpeed Insights is reporting that the server responded in 0.43 seconds. Are these two measurements measuring the same thing?
Some precious milliseconds seem to be tied up in the SSL Negotiation as reported by WebPagetest.org. Since Google wants all SSL does it not ding it like WebPagetest.org seems to be doing?
Also something else I may be seeing in WebPagetesting is that it runs all the code on the page and doesn't differentiate between desktop and mobile like Google does. It almost seems to penalize for the second running.
I have also tested the storefront page at GTmetrix. The site gets a PageSpeed Score of A (94%) but a YSlow Score of C (73%). So which tests should be considered the important ones to pay attention to?
Comment