PageSpeed Insights Update Thread

3 373 просмотра
Перейти к первому непрочитанному сообщению

Paul Irish

не прочитано,
5 февр. 2019 г., 12:36:2205.02.2019
– pagespeed-insights-discuss
We'll update this thread with any user-visible changes to PageSpeed Insights, including the API, score calculation, etc.

Please start a new thread for any comments or questions.

Paul Irish

не прочитано,
5 февр. 2019 г., 12:41:1105.02.2019
– pagespeed-insights-discuss
As of late January 30, 2019, PageSpeed Insights is running Lighthouse 4.1.0. 

Lately we have been working to make desktop measurement more accurate.  Desktop scoring has been recalibrated to stay on par with the fast moving world of desktop browsing based on the most current data on global page speeds. You should expect desktop scores to be lower now than they had been. Mobile performance scoring should be unchanged.   

In addition to these changes to desktop measurement we have made some changes that improve user experience in more subtle ways:
  • The mobile viewport scaling more accurately reflects the true screen size of a Nexus 5X.
  • Audits that encounter warnings will now show a helpful warning inline.
  • Lighthouse errors and the accessibility category are now localized to 42 languages.
  • There's a new audit: FCP on 3G networks. It does not have an effect on performance scoring, but is useful for 3G diagnostics.
For API users, the SEO category has a new audit to evaluate if tap targets are a reasonable size and don't overlap with other elements.

See the detailed Lighthouse 4.1 Release Notes for more.

Paul Irish

не прочитано,
5 февр. 2019 г., 12:45:2705.02.2019
– pagespeed-insights-discuss
From Feb 1 to Feb 4 2019, PSI had a bug that led to lower performance scores. This bug is now resolved.

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.

As of Monday Feb 4, 5pm PST, the bug is completely addressed via a new production rollout.
Сообщение удалено

Paul Irish

не прочитано,
2 мая 2019 г., 16:55:0502.05.2019
– pagespeed-insights-discuss
We'll be deploying some changes to PageSpeed Insights next week. The changes are expected to go live on Wednesday May 8th.

The TL;DR: 
  • Introducing Stack packs
  • New report UI
  • Lower global latency
  • PWA now works 100%
  • SEO and A11y available in 42 languages
  • CrUX data and scoring updated
See the Lighthouse v5 on PSI Release notes for details and screenshots.

We do expect some changes to performance scores, though nothing too significant. 
They are detailed in the Changes that affect scoring section.

As mentioned previously, please start a new thread for any comments or questions.

Paul Irish

не прочитано,
7 авг. 2019 г., 13:26:4807.08.2019
– pagespeed-insights-discuss
Today, we're upgrading the Lighthouse version used by PageSpeed Insights v5 API (and the PSI site) from v5.0.0 to v5.2.0.  You can view the release notes for v5.2.0 and v5.1.0 on github for more details on what is included in these versions.

These upgrades should have little to no effect on performance scoring.

Jasmine Yan

не прочитано,
7 дек. 2020 г., 14:45:1407.12.2020
– pagespeed-insights-discuss
As of December 3, 2020, PageSpeed Insights (PSI) is using the Chrome User Experience Report (CrUX) API as its source of field data. Previously, PSI was using its own custom data pipeline similar to CrUX, but this change brings the two in closer alignment. In the API, this affects the loadingExperience and originLoadingExperience objects. Specifically, the values of percentiles and proportions of field data metrics should now be identical across APIs.

Note that PSI users who have been monitoring their metrics over time may have noticed a small jump when the data source of the API was switched over. Most users should not notice any significant changes in their results, but please start a new thread to let us know if you see anything unusual or have any questions.
Ответить всем
Отправить сообщение автору
Это обсуждение заблокировано
Нельзя отвечать и выполнять другие действия в заблокированных обсуждениях.
0 новых сообщений