Astro vs WordPress Speed Test: Real Numbers From Real Sites
Everyone says WordPress is slow. But how slow? We rebuilt one of our client’s WordPress sites in Astro and ran the numbers side by side. Same content, same images, same hosting tier.
The results weren’t close.
The Test Setup
WordPress site:
- Theme: Flavor theme (ThemeForest, $59)
- Plugins: 34 active (Yoast SEO, WooCommerce, Contact Form 7, Elementor, WP Rocket, etc.)
- Hosting: Shared hosting on Bluehost (standard business plan)
- PHP 8.1, MySQL 8.0
Astro site:
- Framework: Astro 6 with Tailwind CSS
- Plugins: Zero
- Hosting: Vultr VPS (2 vCPU, 4 GB RAM, CloudPanel + nginx)
- Static HTML output
Both sites served over HTTPS with valid SSL certificates. Both were tested from the same location using Google Lighthouse, WebPageTest, and GTmetrix.
The Numbers
| Metric | WordPress | Astro | Difference |
|---|---|---|---|
| First Contentful Paint | 2.1s | 0.3s | 7x faster |
| Largest Contentful Paint | 3.8s | 0.4s | 9.5x faster |
| Total Blocking Time | 890ms | 0ms | 890ms saved |
| Cumulative Layout Shift | 0.18 | 0.00 | Zero shift |
| Lighthouse Performance | 52 | 99 | +47 points |
| Page Weight | 3.2 MB | 142 KB | 22x smaller |
| HTTP Requests | 87 | 8 | 79 fewer |
| Time to Interactive | 4.7s | 0.4s | 11.7x faster |
The WordPress site made 87 HTTP requests on the homepage alone. CSS files from Elementor, JavaScript from 6 different plugins, Google Fonts loaded three separate ways, analytics scripts, chat widgets, cookie consent popups. Every one of those requests adds latency.
The Astro site made 8 requests. HTML, one CSS file, one font file, a favicon, and four optimized images. That’s it.
Why WordPress Is Structurally Slow
It’s not that WordPress developers are bad. It’s that WordPress’s architecture makes speed almost impossible:
PHP renders every page on every request. Even with caching plugins, WordPress generates HTML by querying a MySQL database, running it through PHP template logic, and assembling the page. Astro generates HTML once at build time and serves static files.
Plugins inject code everywhere. Each plugin adds its own CSS and JavaScript to every page, whether that page needs it or not. Yoast adds SEO schema scripts to every page. Elementor adds its rendering engine to every page. Contact Form 7 loads its JavaScript on every page — even pages without forms.
Theme bloat is the norm. Most WordPress themes ship with code for every possible layout, widget, and feature. Your site uses maybe 15% of the CSS in your theme. The other 85% still downloads on every page load.
What This Means for Your Business
Google uses Core Web Vitals as a ranking signal. A site with a 3.8-second LCP is penalized. A site with 0.4-second LCP gets a boost.
But the bigger impact is conversion rates. Amazon found that every 100ms of latency costs 1% in sales. Your 3.4-second disadvantage is costing you real money.
A visitor who lands on a 3.8-second WordPress site has a 53% chance of bouncing before the page renders. A visitor who lands on a 0.4-second Astro site sees your content instantly.
The Migration Process
Rebuilding from WordPress to Astro typically takes 2-4 weeks depending on the site’s complexity. We:
- Audit your existing content and page structure
- Rebuild every page in Astro with proper semantic HTML
- Implement full SEO structure (schema, meta, sitemaps)
- Set up managed hosting on a dedicated VPS
- Launch and verify with Lighthouse + Search Console
The WordPress version of this client’s site scored 52 on Lighthouse. The Astro version scored 99. Same content. Same business. Completely different results.
Get a free site audit and see exactly where your WordPress site is losing speed and rankings.