Get your website's instant CoreWeb Vitals metrics

Core Web Vitals UX score check

• 

  Largest Contentful Paint

  • 75% of all pageviews is seeing the biggest element within 0.0seconds
  • 0% is still having an experience of above 2.5 seconds;
  • This often is a hero- or productimage, which is a confirmation to the user that they reached what they were looking for
  • If TTFB or FCP are healthy, check your rendering strategy and image attributes (lazyload, fetchpriority)

  Too many visitors clicked away too fast or before any other interaction to allow Google to report a trustworthy number for the LCP metric

• 

  Interaction to Next Paint

  • 25% of interacting users have to wait for more than 000ms for (visual) feedback
  • 0% is still having an experience of above 200ms;
  • When this happens during 'add to cart' or on-site searching, it could result in rage-clicking
  • Analyze XHR response times or JavaScript tasks

  There were too few interactions to allow Google to report a trustworthy number for the INP metric.

• 

  Cumulative Layout Shift

  • 25% of all pageviews is disturbed by a layout shift of 0.0 or more
  • 0% is still having a CLS experience of more than 0.10;
  • Layout shifts are likely to distract users, or frustrate them when they just started interacting
  • This is often caused by incomplete CSS or dynamically injecting new contents

  Too many visitors clicked away too fast or before any other interaction to allow Google to report a trustworthy number for the CLS metric

• 

  First Contentful Paint

  • 25% are forced to look at a white screen for more than 0.0seconds
  • 0% is still having an experience of above 1.8 seconds;
  • This is an issue as FCP is important for first user engagement + bounce
  • You might want to look at JS (such as A/B testing) or externally hosted files first

  Apparently, Google wasn't able to collect a sufficient amount of FCP data

• 

  First Input Delay

  • 25% of all pageviews is experiencing a delay of 00msmilliseconds or more
  • 0% is still having an experience of above 100ms;
  • The first interaction is an important one. Too much delay right away could scare visitors away
  • This is often caused by long rendering or JavaScript tasks

  There were too few interactions to allow Google to report a trustworthy number for the FID metric.

• 

  Time to First Byte

  • In 25% of all pageviews, the browser is waiting more than 000ms for a (server) response
  • 0% is still having an experience of above 800ms;
  • If your FCP isn't making up for this, then fixing this will be a shortcut to improved user engagement
  • Investigate waiting-, DNS- and TCP time, server side caching rules and plugins

  Apparently, Google wasn't able to collect a sufficient amount of TTFB data