CORE WEB VITALS RESOURCE PAGE

Everything you need to know about CWV

Core Web Vitals are a set of three Google user experience and website performance metrics that measure loading speed, page interactivity and visual stability. You can measure how websites score with different Google Tools and identify areas for improvement. Ivarii's platform is optimized for Core Web Vitals and websites built with Ivarii have led the industry in all three metrics since it's launch in January 2025.

DATE TECHNOLOGY ORIGINS PERCENT GOOD INP PERCENT GOOD CWV
Feb 2025 Ivarii / Duda 41,341 93.01% 78.21%
Feb 2025 WordPress 3,200,541 85.93% 43.34%
Feb 2025 Shopify 378,797 90.03% 75.83%
Feb 2025 Wix 204,593 88.93% 65.12%
Feb 2025 Squarespace 102,596 95.34% 62.84%
Jan 2025 Ivarii / Duda 39,504 93.02% 76.03%
Jan 2025 WordPress 3,150,225 86.05% 42.58%
Jan 2025 Shopify 375,794 89.9% 75.35%
Jan 2025 Wix 201,632 88.92% 61.94%
Jan 2025 Squarespace 100,050 95.47% 60.97%

Visit Google's Looker Studio for the most recent CWV reports.

WHAT EXACTLY ARE CORE WEB VITALS?

Google announced its Core Web Vitals algorithm update back in May 2020. The Core Web Vitals are three metrics that attempt to summarize the experience of loading a web page in a web browser and first interacting with it. The three metrics are:


  • Largest Contentful Paint (LCP) — measures page speed by using the loading time of the largest object above the fold as a proxy for overall speed. Anything under 2.5 seconds is a good score. 
  • First Input Delay (FID) — measures the interactivity of a web page by checking how long it takes from a user’s first interaction with a page until the browser responds. Anything less than 100 milliseconds is a good score. 
  • Cumulative Layout Shift (CLS) — measures the visual stability of a web page by gauging the degree to which page components move around while the page loads. Anything under 0.1 is a good score. 


The Core Web Vitals are a subset of a wider range of page experience signals that Google uses to rank websites and web pages. Some of the other page experience signals are HTTPS (secure browsing), Safe Browsing, mobile-friendly pages, and not using intrusive overlays, banners, or popup ads on pages. 


Google’s increased focus on the overall experience of browsing a web page reinforces the notion that Google’s primary goal is to serve the best search results to users for given search queries. With the Core Web Vitals, website owners and businesses have a set of benchmark targets they can hit to improve page experience. It used to be unclear what went into the page experience ranking signals, so the current level of transparency actually benefits website owners and managers. 


While the Core Web Vitals are definitely important to optimize, it’s worth noting that page speed, performance, and experience signals are important ranking factors, but they are not the primary ranking factors. You can view the Core Web Vitals as helpful indicators to Google that you’re doing your best to optimize the experience of browsing your site. The top three ranking factors are still:


  1. The content posted on a website
  2. The backlinks pointing to a website’s pages
  3. The overall relevance of a page in answering the query that a user typed in Google


LIGHTHOUSE UPDATES

At the same time as the Core Web Vitals announcement, Google also announced the release of Lighthouse version 6.0, which is the latest version of the company’s open-source web page quality auditing tool. Lighthouse has a big focus on performance with a particular emphasis on different page speed metrics. 


Version 6 essentially includes the Core Web Vitals metrics in the Lighthouse scoring calculations. Anything above 70 on Lighthouse is a strong score even though Google sets a high bar by categorizing scores above 90 as “green”. In the previous version of Lighthouse, which was not dissimilar from version 6, just 10 percent of websites scored over 70, so 70 and above is definitely still a really solid score. 


The average Lighthouse score of websites built using Ivarii is 70. Some of the factors that can slow down your site and give a poor Lighthouse score include:


  • Heavy 3rd party widget use above the fold 9e.g. Image sliders and maps)
  • Externally hosted video embeds on platforms such as Vimeo or YouTube
  • Custom code in your site’s header
  • Tracking pixels that gather information about website visitors

How Ivarii optimizes core web vitals and page speed scores

The time lag between Google’s Core Web Vitals announcement in May 2020 and their use as a ranking factor in July 2021 gave website builders the chance to optimize these metrics for their users. Since Core Web Vitals went live in Google’s algorithms, Ivarii is the leading website builder in terms of the proportion of sites that score “Good” in the Core Web Vitals metrics. 


Some of the practices Ivarii uses out of the box to help our users achieve such consistently high scores with no effort at all include:


  • Image and video optimization
  • Lazy loading images and heavy widgets
  • Using WebP images by default
  • Minifying CSS code and deferring non-critical CSS 
  • Minifying and compressing network payloads
  • Preloading critical assets for better loading speed
  • Serving static assets using an efficient cache policy


SPEED AND PERFORMANCE TIPS FOR WEBSITES

  • Handling resource-intensive pages:


Some of a website’s pages may need to load bulky resources, such as maps, for example, to display the locations of a business. For these types of pages, you can make sure you have something at the top of the page above the fold, such as text, that will load first before the map does. Then, lower down the page, you can place your map element(s). This will help reduce the impact of the map on your Core Web Vitals score by optimizing the initial page load as much as possible.


  • Don’t use too many web fonts on one page:


Google fonts are third-party Google-hosted fonts that Google serves to web browsers from a CDN. There is a lot of complex logic behind how Google serves these fonts to users, so it’s not advisable to host them on anything other than Google’s CDN. What is advisable, however, is to limit the number of fonts on each of your web pages because each different font adds a performance overhead that can slow down your page loading speed.


Ivarii helps combat this problem by only downloading the fonts that you actually use on your page and by only downloading the specific characters from each font that appear on a given page. So, by limiting the number of fonts on a site’s page and leveraging Ivarii’s own best practices for font loading, you can reduce potential font-related performance issues on any sites you manage or own.


  • Minimize heavy content on the homepage:


Most users enter websites from the homepage rather than inner pages. Having a homepage full of heavy content negatively impacts that initial interaction with a site from a user’s perspective. Furthermore, it’s going to be difficult to score well with Google’s page experience and speed metrics if you have 10-20 high-quality images, social media feeds, or 4K videos loading on your homepage. A solid homepage is a mix of text, some icons, and a few images that lead people into the main areas of a website.

Optimizing performance and speed is important in today’s competitive landscape both in terms of ranking well and providing the best possible experience to people visiting any websites you own or manage. Ivarii provides a slew of automatic optimizations to improve both speed and performance for sites built using our platform. By publishing great content and using the best practices previously outlined, you can build with Ivarii, and create a winning website.

Core web vitals FAQs

  • Why do my scores fluctuate?

    It is normal to see a small fluctuation in your scores over a short period of time. These fluctuations can be caused by variations in server response, domain lookup, and asset loading times. How quickly assets load can be affected by other programs running simultaneously on the device that is trying to access your site.


    If you see large score fluctuations over a long period of time this can be attributed to Google making adjustments to their scoring system.

  • What should I do with unused JS, CSS, and Google Fonts?

    If you added the unused JS, CSS, or Google fonts to your site, you can remove them wherever you originally added them.


    When checking Web Vitals, your report might reference JS and CSS that can be removed. Typically, this is not referencing the code you have added, but is referencing default code that cannot be changed or removed.

  • Can I access the JS and CSS source files?

    You cannot access JS and CSS source files because they are a core part of the platform.

  • Google sent me an email saying Core Web Vitals INP issues were detected on my site. What does this mean?

    INP is an existing metric that was previously not officially measured, though Google has recently announced it will be replacing the FID metric in March 2024. The INP score would not impact CWV until March 2024. However, in preparation for this transition, Google has started to inform site owners when INP issues are detected.


    Prior to the announcement from Google, Ivarii had already started addressing this metric. As a result many sites already score well on INP, though we are continuing to optimize it.


    We are continuing to learn about INP and identifying the optimal practices for both backend operations and site creators. We will update you on what best practices you can put in place are as we learn more. In the interim, if you receive a notice from Google reporting your site has INP issues, please review your site to ensure it is following the current best practices.

  • How do I remove render-blocking resources?

    If you added JS to the site head, it can block your page content from loading while the JS renders. For this reason, we recommend moving your JS to the body and adding either async or defer keywords. Using async tells the browser to load the script and page contents at the same time. Using defer tells the browser to run the script after the page contents have loaded.

  • What are the best templates for page speed?

    All templates are well optimized, but the most recent templates have been optimized for current guidelines. To determine which templates were most recently released, look for the new icon on the template.

  • Should I add scripts to the head or body?

    We recommend adding scripts to the body. If your scripts are in the head, they will have to parse before any HTML or CSS can load. This can cause a delay in LCP and FID.

  • Why is my mobile score lower than my desktop score?

    In general, mobile devices are slower than desktop computers because they rely on data. For example, a video loads faster on a desktop computer than it would on a mobile phone using data.