7

There is a new feature in PageSpeed Insights that shows you the experience of real users. Now I checked one of my websites with this feature on mobile and I got this message:

"Core Web Vitals Assessment: Failed Computed from the Core Web Vitals metrics over the latest 28-day collection period. Learn more"

Why is PageSpeed returning me this answer? It seems all ok in Google Search Console under Core web vitals.

TongaLife
  • 124
  • 1
  • 1
  • 8
  • 1
    They may have just changed the message. They normally need a certain amount of data before they will show this. Do you happen to know where the "learn more" link goes as I would imagine that will answer your question and will be useful information for others. – GrahamTheDev Nov 17 '21 at 17:36
  • 1
    Ah ok, thanks. Now I understand. The link goes to this site https://web.dev/vitals/ – TongaLife Nov 18 '21 at 09:09
  • Does the Core Web Vitals page in Search Console show that all the URLs are "good"? – kh_ Nov 22 '21 at 17:22
  • Yes, but the website must have enough interaction and Google Search Console must have enough data. – TongaLife Nov 22 '21 at 17:41

2 Answers2

1

Core Web Vitals result is based on 3 metrics below

  1. Largest Contentful Paint (LCP)
  2. First Input Delay (FID)
  3. Cumulative Layout Shift (CLS)

All 3 metric's score is divided into 3 categories - Good, Needs Improvement and Poor. If any of these 3 metric is not having 'Good' score, the overall results is shown as 'Failed'.
Check the metrics score just below the 'Failed' text, and find out which metric score needs to be improved.

Debjit Sinha
  • 103
  • 1
  • 7
0

When your CWV Assessment fails, you need a systematic approach to diagnose and optimize your web performance. Here's the in-depth tech guide to get you out of the woods.

  1. Analyzing the Problem: Before jumping into solutions, you need to understand what's causing the poor CWV scores. Utilize tools like Chrome's Lighthouse or WebPageTest for an in-depth analysis of your website. These provide specific metrics (like First Contentful Paint, Cumulative Layout Shift, and Largest Contentful Paint) that directly impact CWV.

  2. Optimizing Your Site: Once you've pinpointed the issues, start addressing them systematically. For instance, if your website struggles with render-blocking resources, you can optimize the critical rendering path by inlining critical CSS, deferring non-critical JavaScript, or using async and defer attributes.

  3. Monitoring Real-User Metrics: Lab data is fantastic, but it might not fully represent your users' experience. Real-user monitoring (RUM) is crucial to catch anomalies that lab tests may miss. Here's where a tool like Loado can be a game-changer. It collects real-user data, helping you keep track of the user's actual experience.

  4. Iterating Your Process: Improvement doesn't stop with optimization. Make this a continuous process - keep monitoring, adjusting, and learning from your metrics. Remember, performance is a journey, not a destination!

  5. Educate Yourself: Stay updated with the latest practices and tools. Resources like the Google Web Dev Blog, MDN Web Docs, and forums like this are a goldmine of knowledge.

Remember, the goal of CWV isn't just to meet some arbitrary Google standard, but to create a delightful user experience. As you navigate this journey, we're right here to help! Feel free to reach out with any further questions.

NiLL
  • 13,645
  • 14
  • 46
  • 59