Core Web Vitals and Why WordPress and Astro Sit So Far Apart
Core Web Vitals performance is a set of field-based user experience metrics from Google that capture how quickly content appears, how visually stable it is during loading, and how responsive a page feels to real visitors on real devices and connections. In HTTP Archive’s Core Web Vitals Technology Report, WordPress and Astro end up near opposite ends of the spectrum: WordPress has roughly 49% of sites scoring good Core Web Vitals, while Astro reaches about 67%. Both platforms can output fast pages, but the report shows that the typical implementation patterns around each ecosystem differ. WordPress sites often ship more features, plugins, and scripts by default, whereas Astro projects tend to be lighter and more focused. The key lesson is not that one platform is always fast or slow, but that their architectural defaults push developers toward very different performance profiles.
Architecture and Page Weight: Why Astro Starts Lighter
Astro’s architecture centers on pre-rendering pages and sending mostly static HTML, with the option to hydrate interactive islands only where needed. That design makes low page weight the default: the HTTP Archive dataset shows Astro with a median transfer size of about 1.65 MB, the lightest of the platforms compared. This aligns with Astro’s solid Core Web Vitals performance, where about 67% of sites achieve good scores. WordPress, in contrast, is a dynamic PHP-based CMS that often layers themes, page builders, and multiple plugins on top of each other. That stack tends to ship more JavaScript and CSS by default, giving WordPress a median page weight of around 2.76 MB, near the heaviest in the report. Page weight alone does not decide Core Web Vitals performance, but starting lighter gives Astro developers more room before they hit user-perceived limits.
Beyond Page Weight: Execution, JavaScript, and Real-World Metrics
The report shows that Core Web Vitals performance is shaped as much by how code runs as by how much code is sent. Lighthouse favors lower JavaScript payloads, fewer render-blocking resources, and efficient images; Astro tops that chart with a score of 68, while WordPress sits at 44. Yet examples like Shopify, which combines heavy pages with high Core Web Vitals success, prove that execution patterns matter. Stable layouts, predictable rendering, and tuned CDN delivery can offset larger payloads in real-world CrUX measurements. For WordPress vs Astro, this means that Astro’s minimal JavaScript and static-first rendering align closely with what both Lighthouse and field data reward. WordPress sites, however, must work harder to tame plugin scripts, optimize theme assets, and control layout shifts to reach similar Core Web Vitals performance, even if the total page weight is not dramatically higher.
Platform-Specific Strategies: Choosing and Tuning for Core Web Vitals
WordPress and Astro demand different web performance optimization strategies because their architectures and ecosystems shape bottlenecks in different places. With WordPress, most Core Web Vitals wins come from practical hygiene: trimming plugins, auditing third-party scripts, optimizing images, and choosing themes that avoid layout shifts. Caching and CDN setups are essential to keep dynamic rendering from slowing down real users. Astro, on the other hand, rewards discipline around interactivity. Its static-first design means that complexity only grows when developers add islands and client-side frameworks; keeping those islands small and focused helps maintain strong Core Web Vitals performance as sites grow. The platform comparison data makes one point clear: there is no one-size-fits-all recipe. Developers should pick the platform that matches their feature needs, then apply performance tactics that fit how that specific platform builds and ships pages.