What this tool tests
We hit your site with the same test Google uses to decide rankings. The Google PageSpeed Insights API runs a full audit of your page on a simulated mobile device (Moto G Power on a 4G connection). Mobile, because that's where Google looks first.
You get three numbers: a Performance score (0 to 100), Largest Contentful Paint (how fast your main content appears), and a pass/fail on Core Web Vitals. These are the same metrics Google uses in its page experience ranking signal.
Citation-ready answer
WordPress speed answers to inspect before a rebuild call
What is a WordPress speed test?
A WordPress speed test compares mobile lab performance, available field data, Core Web Vitals, and WordPress-specific bottlenecks such as plugins, themes, images, and server response time.
When it breaks
It becomes misleading when one lab score is treated as the full truth without checking CrUX field data, Lighthouse opportunities, cache state, third-party scripts, and the tested URL template.
Inspect first
Inspect PageSpeed field data first when available, then Lighthouse LCP, INP proxy signals, CLS, render-blocking files, JavaScript execution, image weight, and TTFB.
Which Core Web Vitals matter?
The Core Web Vitals are Largest Contentful Paint for loading speed, Interaction to Next Paint for responsiveness, and Cumulative Layout Shift for visual stability.
When it breaks
WordPress pages fail when the LCP element is delayed by server response, render-blocking CSS, heavy JavaScript, unoptimized hero images, ads, or consent and tracking scripts.
Inspect first
Start with the LCP element, main-thread work, third-party cost, layout shifts above the fold, and whether the failing URL is a template pattern or a one-off page.
When does speed become a rebuild signal?
Speed becomes a rebuild signal when repeated cleanup cannot remove structural plugin, page-builder, theme, hosting, and rendering costs from priority landing pages.
When it breaks
It is easy to over-prescribe a rebuild if you have not first measured plugin load, image weight, TTFB, unused scripts, caching behavior, and the current conversion value of the page.
Inspect first
Pair the external PageSpeed result with a plugin-bloat score, crawl priority, GSC landing-page demand, and a fix-versus-rebuild estimate.
| Diagnostic step | Question to answer | Action when it fails |
|---|
| Field data | Is CrUX data available for the URL or origin? | Use field data as the user-experience baseline where it exists. |
| Lighthouse lab run | Which element controls LCP and which resources block render? | Prioritize the LCP element, CSS, image, and JavaScript path. |
| WordPress stack | Which plugins, theme assets, and third parties load on the page? | Remove or defer non-critical assets before pricing a rebuild. |
| Template priority | Does the slow URL drive search demand or leads? | Fix high-value templates first, then retest after cache and traffic settle. |
Methodology and limits
This tool requests a mobile PageSpeed Insights test for one public URL. PageSpeed Insights returns Lighthouse lab data and, when Google has enough real-user data, Chrome UX Report field data. Use field data first when it exists. Use the lab result to find the bottlenecks you can reproduce and fix.
Lab result
A controlled Lighthouse run for the tested URL. It is useful for LCP, render blocking, image weight, JavaScript cost, and repeatable debugging.
Field data
A 28-day real-user view from CrUX when enough traffic exists. Some URLs only show origin data, and new or low-traffic URLs may show no field data.
WordPress signals
Heuristics from the page response, resource patterns, and common plugin/page-builder footprints. It does not inspect your WordPress admin.
Known limits
One run can move. API quota, third-party tags, caching state, consent banners, and server timing can change the score between tests.
Why WordPress sites score low
Plugins. Every WordPress plugin injects its own CSS and JavaScript files into every page load, whether that page needs them or not. A site with 20 plugins can generate 60 to 80 HTTP requests before a visitor sees any content. That's not a theory. It's what we see on every site we test.
Page builders. Elementor, Divi, and WPBakery ship 400KB+ of JavaScript that the browser has to download, parse, and execute before it can render your page. That's the rendering engine loading before your content. On mobile, patients, customers, or leads see a blank screen for 3 to 5 seconds. Most leave after 3.
Uncompressed images. The average WordPress site loads hero images at 1 to 3MB. No WebP conversion, no responsive sizing, no lazy loading. One image can double your total page weight.
Shared hosting. Most WordPress sites run on shared servers where the server response time alone is 800ms to 1.5 seconds. That's before any CSS, JavaScript, or images start loading. You can't cache your way out of a slow server.
Plugin bloat scorecard
The speed test gives you the external mobile PageSpeed result. Pair it with a quick internal plugin score so you know whether to optimize WordPress first or price a rebuild seriously.
0 to 3 points
Cleanup path
Remove unused plugins, clean tracking scripts, optimize images, and retest.
4 to 6 points
Audit path
Profile plugin PHP cost, frontend assets, DOM size, and Core Web Vitals together.
7 to 8 points
Rebuild threshold
Treat repeated optimization as suspect and map SEO parity before rebuilding.
Score the stack with the plugin-bloat scorecard, then read the plugin-bloat guide for the measurement workflow before and after removing obvious offenders.
What the scores mean
0 to 49Your site is actively losing visitors. Google is factoring this into your rankings. Every day at this score costs you traffic you never see.
50 to 89Functional, but competitors with faster sites rank higher for the same keywords. You're leaving positions on the table.
90 to 100Top tier. Google isn't penalizing you for speed. Your ranking factors are content, backlinks, and relevance, not infrastructure.
What to do if your score is bad
Most WordPress sites we test score between 25 and 45 on mobile. You're not alone, and it's fixable.
If you want the full picture, every issue, what it's costing you, and exactly how to fix it, that's what the $490 audit is for. It includes a complete speed analysis, redirect risk map, and a rebuild-or-fix recommendation based on your specific site. 72-hour delivery.
Common questions
What is a good PageSpeed score for WordPress?
Anything above 90 on mobile. But most WordPress sites we see score 25 to 45. If you're above 60, you're ahead of the majority.
Why is my WordPress site so slow?
Usually plugins. The average WordPress site loads 30 to 80 plugin files before showing any content. Page builders like Elementor add another 400KB+ of JavaScript on top.
Does site speed actually affect Google rankings?
Yes. Google confirmed Core Web Vitals as a ranking factor in 2021. We've seen sites jump 10 to 15 positions from speed improvements alone.
Can I fix my speed without rebuilding my whole site?
Sometimes. Removing unused plugins, compressing images, and adding caching can help. But if your site runs Elementor or a heavy theme, there's a ceiling to what you can fix without changing the foundation. The audit tells you which path makes sense for your site.