Core Web Vitals & Page Speed – What To Do (and Not Do) with Your Website
Recap: The Page Experience Update is introducing Core Web Vitals to Google’s search ranking algorithm for the first time. Core Web Vitals are a series of pagespeed scores relating to how quickly a page loads, how quickly that page is interactive, and how stable that page is visually. Google started introducing elements of this update to their algorithm in mid-June, with the goal for it to play a full role by the end of August 2021. Check out our SEO News page to learn more. Over the past several months, our Carrot Engineering Team has been identifying, optimizing, and improving features and elements that directly contribute to better user experience and site speed metrics. As that work continues to make our sites faster and better than ever, we’ve compiled some of the most common questions, issues, and misconceptions we’ve seen as a resource for you to be ahead of the game on your end. DO Understand Testing Tools We get this question a lot: how do you test your site speed and Core Web Vitals and what tool should you use? At Carrot, we recommend using Google’s PageSpeed Insights Tool because – regardless of which tool you choose – the most important consideration is that you be consistent. To us, using Google’s own tool makes the most sense. If you’re using the Chrome Browser, the Lighthouse Tool in the Developer Tools is another great option. That said, we always want to be sure that our members understand the differences and caveats between those snapshot scores provided by tools and the scores that are actually being used in Google’s algorithm. Google differentiates them into two categories: lab data and field data. Lab Data – Provided By Testing Tools Lab data is exactly what it sounds like – data collected in a lab, or in this case, a single snapshot report performed by Google’s PageSpeed Insights Tool or any other third-party testing tool. It uses your own browser or another emulated device to load your website in a simulated environment and capture the key metrics that contribute to Core Web Vitals and Page Experience. These scores are meant to be consistent baselines and are not necessarily reflective of actual user experience. Just like in a real lab, you want to control for all variables when running experiments and tests on your website. Google’s page speed tool (and most other tools) do this by loading your site on a simulated older generation smartphone with only a 3G connection to determine mobile “site speed” scores. This is meant to represent the absolute baseline and used as a tool for debugging any performance issues with your site. It’s useful for looking at where you can improve your scores, but it’s not useful for understanding real user experience. Most users are on newer mobile devices with better connections and WiFi. Their experience is better than in the simulated snapshot and contributes to field data – the real scores used by Google’s search ranking algorithm. Field Data – Provided By Real User Experience Like we said above – field data is what Google is actually introducing to their search algorithm. It represents the actual user experiences collected by the Chrome User Experience Report (or CrUX) when users visit your site. Google then looks at the 75th percentile of those scores, and that’s your actual “score” used by their algorithm. Just like with Google’s more commonly-known ranking indicators, we lose visibility and transparency the closer we get to the algorithm. So while snapshot lab data scores can be accessed whenever we feel like running a tool, user experience field data is more ambiguous and inaccessible. There are … Continued