{"id":607,"date":"2025-08-22T06:13:20","date_gmt":"2025-08-22T06:13:20","guid":{"rendered":"https:\/\/ambiguouslyblonde.com\/files\/weston-ruter-web-performance-milestone\/"},"modified":"2025-08-22T06:13:20","modified_gmt":"2025-08-22T06:13:20","slug":"weston-ruter-web-performance-milestone","status":"publish","type":"post","link":"https:\/\/ambiguouslyblonde.com\/files\/weston-ruter-web-performance-milestone\/","title":{"rendered":"Weston Ruter: Web Performance Milestone"},"content":{"rendered":"

A couple months ago, this blog<\/a> reached a web performance milestone which I shared on LinkedIn<\/a>, Bluesky<\/a>, Mastodon<\/a>, Twitter<\/a>:<\/p>\n

\n

For the first time ever, I\u2019ve just seen my blog appear in field metrics from CrUX (Chrome UX Report), albeit in desktop only and for the origin not an individual URL. Baby steps. In any case, Core Web Vitals Assessment: Passed \"\u2705\"<\/p>\n<\/blockquote>\n

Yesterday, I checked PageSpeed Insights<\/a> again, and I was excited to discover that my blog is now also appearing in field metrics for mobile as well! And like desktop, the CWV assessment is also passing for mobile. The eligibility criteria<\/a> for the CrUX dataset includes that \u201cthere must be a large enough number of visitors in order to create a statistically significant dataset.\u201d Granted, my site is still only getting enough traffic for origin-level metrics, and I can\u2019t see field metrics for the homepage URL specifically, but it\u2019s another baby step! (Or maybe a toddler step?)<\/p>\n

I\u2019ve really been trying to double down this summer on tuning every bit of performance possible out of WordPress (on the frontend), using my site as a case study, and I\u2019ve been sharing my findings in posts here. I hope the site traffic is an indication that the community has found my posts helpful. The learnings are also making their way into Performance Lab<\/a> feature plugins as well as in performance improvements on the roadmap for WordPress 6.9<\/a>. I have some more posts that I\u2019m working on. You can subscribe<\/a> to get them in your inbox.<\/p>\n

On August 27th (next Wednesday) at WordCamp US 2025<\/a> here in Portland, Oregon, I\u2019m giving a talk called \u201cThe Site Speed Frontier with Performance Lab and Beyond<\/strong><\/a>\u201d at 11:30am PDT. I hope to see you there, but it will also be livestreamed and recorded. I\u2019ll be blogging an elaborated version of what I have time to share in my talk. (By the way, if you are attending in person, check out My Portland Picks<\/a> post for what I recommend visitors check out!)<\/p>\n

One takeaway I\u2019ll be emphasizing in my talk is that we needn\u2019t settle with sites merely passing<\/em> the Core Web Vitals assessment or achieving a \u201cperfect\u201d 100 performance score in Lighthouse. Why be content with a good 2-second LCP<\/abbr> when it could be half that or even practically zero? Web performance is a journey, and there\u2019s always room for improvement. I can see from my blog\u2019s field metrics, for example, that the TTFB<\/abbr> is hovering around the threshold between \u201cneeds improvement\u201d and \u201cpoor\u201d. In spite of this, the frontend is so tuned that on mobile the LCP-TTFB<\/abbr> in CrUX is 400ms and on desktop it\u2019s only 100ms.<\/p>\n

I personally love optimizing the performance of WordPress sites, but I get it that this isn\u2019t for everyone (nor should it be). By landing our improvements from the Core Performance Team<\/a>, my hope is that WordPress core (and the ecosystem) will have best practices implemented by default so that site owners needn\u2019t worry about performance.<\/p>\n

\n

I had to take some PSI<\/abbr> screenshots to memorialize the milestone:<\/p>\n

Field Data via CrUX<\/h2>\n
\n
\n
\"Core