Google Page Speed Drop，说我可以节省更多的加载时间，即使什么都没有改变 [英] Google Page Speed Drop, says I can save more loading time, even though nothing changed
问题描述
我每天都要测试我的Pagespeed几次.我的页面通常获得94到98之间的评分，主要问题是:
I'm testing my pagespeed everyday several times. My page often receives a grade between 94 to 98, with the main problems being:
消除渲染阻止资源-保存0.33
Eliminate render-blocking resources - Save 0.33
推迟未使用的CSS-节省0.15秒
Defer unused CSS - Save 0.15 s
在实验室数据中，所有值均为绿色.
And in Lab data, all values are green.
从昨天开始，页面速度突然下降到大约80-91的范围， 问题是:
Since yesterday, suddenly page speed has dropped, to about 80-91 range, with the problems being:
消除渲染阻止资源-保存〜0.33
Eliminate render-blocking resources - Save ~0.33
推迟未使用的CSS-节省〜0.60 s
Defer unused CSS - Save ~0.60 s
这也表示我的First CPU idle慢~4,5ms
time to interactive，~4.7
有时speed index也很慢.
它也开始显示Minimize main-thread work建议，但之前没有显示.
It also started to show Minimize main-thread work advice, which didn't show earlier.
问题是，我没有更改页面中的任何内容.仍然是相同的HTML，CSS和JS.这也不是服务器问题，我没有CPU过度使用问题.
The thing is, I did not change anything in the page. Still same HTML, CSS and JS. This also not a server issue, I don't have a CPU overuse problem.
在Gtmetrix上，我仍然获得相同的100％分数和相同的87％的Yslow分数，页面完全加载在1.1s到1.7s之间，使22个HTTP请求的总大小为259kb，就像以前一样.
On Gtmetrix I'm still getting the same 100% score and same 87% Yslow score, with the page being fully loaded somewhere between 1.1s to 1.7s, making 22 HTTP requests in total size of 259kb, just like before.
在Pingdom上，我也获得了与以前相同的91级成绩，页面加载速度约为622ms至750ms.
On Pingdom I also get the same 91 grade as before, with page load speed around 622ms to 750ms.
因此，我无法理解Google分析我的页面的方式的突然变化. 我很担心这会影响我的排名.
Therefore, I can't understand this sudden change in the way Google analyzes my page. I'm worried of course it will affect my rankings.
你知道是什么原因造成的吗?
Any idea what is causing this?
推荐答案
此错误已被Google确认，现已修复.请参阅 https://groups.google.com/论坛/#！topic/pagespeed-insights-discuss/by9-TbqdlBM
This bug was acknowledged by Google and now has been fixed. Refer to https://groups.google.com/forum/#!topic/pagespeed-insights-discuss/by9-TbqdlBM
从2019年2月1日到2月4日，PSI有一个导致性能降低的错误 分数.现在，此错误已解决.
From Feb 1 to Feb 4 2019, PSI had a bug that led to lower performance scores. This bug is now resolved.
PageSpeed Insights使用的无头Chrome基础设施具有
报告未压缩(post-gzip)大小的错误，就好像它们是
压缩的传输大小.这导致错误的计算
性能指标，最终得分较低.邮件清单
标题为
The headless Chrome infrastructure used by PageSpeed Insights had a bug that reported uncompressed (post-gzip) sizes as if they were the compressed transfer sizes. This led to incorrect calculations of the performance metrics and ultimately a lower score. The mailing list thread titled [BUG] [compression] Avoid enormous network payloads / Defer unused CSS doesn't consider compression covered this issue in greater detail. Thanks for Raul and David for their help.
从太平洋标准时间2月4日(星期一)下午5点开始，该错误已通过新 生产推广.
As of Monday Feb 4, 5pm PST, the bug is completely addressed via a new production rollout.
这篇关于Google Page Speed Drop，说我可以节省更多的加载时间，即使什么都没有改变的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
