Are exchanged or reciprocal links okay with Google?
Etmagnis dis parturient montes, nascetur ridiculus mus. Donec lorem ipsum dolor sit amet, et consectetuer adipiscing elit. Aenean commodo ligula eget consyect etur dolor.

Contact Info

(+888)-123-4587

121 King St, Melbourne VIC 3000, Australia

info@example.com

Folow us on social

PageSpeed ​​Insights now displays more field data

PageSpeed ​​Insights now displays more field data

PageSpeed ​​Insights and the API have been updated to now display more field data than before. The updated PageSpeed ​​Insights score is live and should reflect the new way of handling field data.

PageSpeed ​​Insights previously only displayed field data if all field data was collected.

This was problematic because 30% of web pages do not register one of the metrics, First Input Delay (FID).

Field data in PageSpeed ​​Insights

Field data is page speed metrics for real users that Google collects through Chrome mobile browsers that have chosen to send anonymized performance information from site visitors’ actual experience to a webpage, which is then used to calculate page speed metrics.

Advertising

Continue reading below

Labdata is what is used in Google Lighthouse, a tool used to estimate what a PageSpeed ​​score might be.

Guy sends in the Chrome browser and drives the dev tools.

Right-clicking anywhere on a webpage opens Chrome Dev Tools, and from there, the guy can be used to simulate what PageSpeed ​​metrics are.

But these are only simulations, estimates of what the values ​​may be.

The actual data that Google may use for ranking purposes is called field data and it is the data collected from real users who download actual pages on mobile devices under real circumstances.

Advertising

Continue reading below

Available field data is now displayed

The change that Google made in the PageSpeed ​​Insights API and tool is that Google displays the field measurements that have been collected even though other field data has not been collected.

Previously, Google only reported if all the data collected complied with a certain data threshold.

According to Google Rick Viscomi on Twitter, he calls this a big deal because the missing data happens with 30% of the origin in the Chrome User Experience Report, where data on First Input Delay is missing while the other data was there.

“In the past, you would see ‘no data’ if you were just missing FID data. Now you can see what’s available.

This is a big thing because ~ 30% of the origins of CrUX were missing FID data! ”

Why is First Input Delay (FID) missing?

First Input Delay is a measurement that measures the response of a website by measuring the delay in processing an event such as clicking a button, pressing a menu or entering data with a keyboard press and the time it takes for the web page to respond .

Scrolling and zooming in on text or images does not count as an interaction with the web page.

Advertising

Continue reading below

According to Google’s Web.dev page on FID, many users do not interact with a webpage and therefore Chrome User Experience Report (CrUX) will not detect this metric.

“Not all users will interact with your site every time they visit. And not all interactions are relevant to FID …

… FID is a metric that can only be measured in the field, as it requires a real user to interact with your site. ”

Rick Viscomi explained in one follow-up tweet why First Input Delay (FID) tends to miss:

FID in particular tends to be absent because, unlike other Web Vitals, it is dependent on a user interaction being measured. Almost all page views have an LCP or CLS, but not all have user interaction! ”

Advertising

Continue reading below

This is a positive step from Google because the additional information allows more publishers to make better decisions about what to fix in relation to PageSpeed ​​metrics.

This is how Google’s official announcement explained it:

“Field data for PageSpeed ​​Insights is now provided for pages and origins that may not have sufficient data for one metric, but sufficient data for other metrics.

Previously, field data was only displayed if all metrics for a page or origin complied with a data threshold.

Now any metric that meets the data threshold will be delivered.

This is reflected in loadingExperience and originLoadingExperience objects in the API and also in the frontend. ”

Advertising

Continue reading below

Good news for web publishers, developers and SEOs

This is good news for community publishing because field data reflects the actual visitor user experience on a web page.

The more field data publishers there are, the more accurate and complete can be taken to solve problems in the real world.

Video illustrating how the first input delay is measured

Quotes

Release notes for PageSpeed ​​Insights API and PageSpeed ​​Insights UI

Advertising

Continue reading below

Differences between field data in PSI and CrUX

Google Web.dev First Input Delay (FID) Page
What if a user never interacts with your site?

PageSpeed ​​Insights API documentation

PageSpeed ​​Insights tool

How to open Chrome Dev tools

    Leave Your Comment

    Your email address will not be published.*