9 replies

1. Michael Warren Bluesky 12 min later

   i wonder if core web vitals cares if you’re seeing the not found page? haha

   1. Zach Leatherman Bluesky 41 min later

      😅😅😅

   2. Ben Schwarz Bluesky 10 hr later

      If you’re meaning CWV, collected by Chrome user experience report (CrUX) — nope, if the status is successful and the page is indexable, it’ll measure the error page too.

2. Christopher Kirk-Nielsen Mastodon 16 min later

   @zachleat The lengths some companies will go to game the system…! 🙃

3. Khalid ⚡ Mastodon 45 min later

   @zachleat gotta save that compute for AI

4. Spencer Mastodon 49 min later

   @zachleat task failed successfully?

   1. Zach Leatherman Mastodon 57 min later

      @sphars the error page could be faster, tbh 😅

5. Amelia Bellamy-Royds Mastodon 1 hr later

   @zachleat Are they at least returning an HTTP error code along with that page? (In which case, your Speedlify stats should probably filter it out.)

   1. Zach Leatherman Mastodon 1 hr later

      @AmeliaBR good question! looks like the Axe run (and screenshot) returned a 403 but the Lighthouse request might have succeeded with a 200 (which you can see in the filmstrip).

      https://www.speedlify.dev/site/www-oracle-com/

      I might need to handle this specific case better on my end