How Fast Is a WordPress.com Site? I Tested It Before and After (2026)
I ran Google PageSpeed tests on a WordPress.com site before and after free optimisation. The actual scores, Core Web Vitals, and if you need a caching plugin.
A stock WordPress.com site scored Desktop 95 / Mobile 65 in Google PageSpeed with no optimisation. After two free changes, cleaning up the hero image and installing the free Jetpack Boost plugin, it hit Desktop 99 / Mobile 85, with mobile LCP cut from 6.5s to 3.7s and green Core Web Vitals throughout. WordPress.com is fast by default because it handles edge caching, a global CDN, WebP images and HTTP/3 for you. You do not need a heavy caching plugin; you just need lean images and one free plugin.
On this page
- TL;DR
- How I tested it
- The first result: no optimisation plugins
- Why WordPress.com is fast by default
- What I changed (all free)
- The result after the plugin
- Before and after, side by side
- How it compares to shared and self-hosted
- Why mobile scores lower than desktop
- Do you need a caching plugin on WordPress.com?
- How to make your WordPress.com site faster
- A few things to keep in mind
- So, is WordPress.com fast enough?
- Final take
- Common questions
"Is WordPress.com actually fast?" is one of those questions everyone answers and nobody tests.
So I tested it. Real site, real Google PageSpeed Insights, before and after.
The short version: stock, it scored Desktop 95 / Mobile 65. After two free changes, Desktop 99 / Mobile 85, with green Core Web Vitals across the board.
Here are the actual numbers, the screenshots, and exactly what moved them.
How I tested it
I tested a real WordPress.com site (a local-business homepage, hero section, image cards, a photo grid, a contact form), not a stripped-back demo. The tool: Google PageSpeed Insights, which runs Lighthouse.
One thing to know up front: PageSpeed's mobile test throttles to a mid-tier phone on a Slow 4G connection. That is far harsher than most real visits, so mobile scores always look lower than what your visitors actually feel.
The first result: no optimisation plugins
Stock site, zero performance plugins. Desktop 95, Mobile 65.
The mobile weakness was not the host. It was the page, a large hero photo and render-blocking fonts. The desktop 95, with no tuning at all, already told the real story about the server.
Why WordPress.com is fast by default
Before I changed anything, the platform was doing the heavy lifting. Every WordPress.com site gets, on every plan:
- A global edge cache and CDN across 28+ data centres on six continents.
- Automatic image optimisation, resizing and WebP delivery, no plugin.
- HTTP/3 on modern infrastructure (Automattic enabled it across all its services in December 2023).
This is the stuff you would normally hire someone to configure. Here it is just on.
What I changed (all free)
Two changes, zero cost.
1. Fixed the images. Lazy-loaded below-the-fold images, added proper width/height attributes, and made sure the hero was served from the site CDN.
2. Installed Jetpack Boost (free). I enabled Critical CSS, defer JavaScript, concatenate CSS/JS, and the Image CDN.
The result after the plugin
Mobile climbed 65 → 85, and mobile LCP nearly halved, 6.5s → 3.7s. On desktop it went to a near-perfect 99, with a 0.6s LCP.
Before and after, side by side
| Metric | Before | After |
|---|---|---|
| Desktop PageSpeed | 95 | 99 |
| Mobile PageSpeed | 65 | 85 |
| Mobile LCP | 6.5s | 3.7s |
| Desktop LCP | 0.9s | 0.6s |
| CLS | 0 | 0 |
| Total Blocking Time | 20ms | 0ms |
| Accessibility | 92 | 96 |
| Best Practices | 100 | 100 |
Two free changes, +20 mobile points and a 43% faster mobile LCP. The host never changed; only the page did.
How it compares to shared and self-hosted
Where does that leave WordPress.com against the alternatives?
| Host type | Typical TTFB | Setup effort |
|---|---|---|
| WordPress.com | ~69ms edge-cached (Hostingstep); ~288ms origin (WPBeginner) | None, handled |
| Budget shared | ~530ms (e.g. entry Bluehost) | Manual caching + CDN |
| Tuned self-hosted VPS | ~80ms cached (LiteSpeed) | High, you're the sysadmin |
One honest caveat: those WordPress.com numbers measure different things, Hostingstep's ~69ms is edge-cached global TTFB, while WPBeginner's ~288ms is average origin TTFB. Not a like-for-like comparison, but both put WordPress.com among the fast group. A tuned VPS can beat it, if you want to run the server yourself.
Why mobile scores lower than desktop
Do not panic at a mobile 85. It is expected.
PageSpeed throttles mobile to a budget phone on a slow network, so an image-rich page will always score lower there than on desktop. What actually matters for SEO is green Core Web Vitals (LCP ≤2.5s, CLS ≤0.1, INP ≤200ms), measured on real visitors, not a perfect 100 in the lab tool.
My site had green vitals at a mobile score of 85. That is the win, not the number.
Do you need a caching plugin on WordPress.com?
No.
WordPress.com applies page caching at the platform level, so a heavy caching plugin like WP Rocket is largely redundant. (On the plugin-capable Business and Commerce plans, just confirm the global edge cache is enabled, it is a toggle there.)
The free Jetpack Boost is different, it does page-level work (Critical CSS, deferring JS) that the cache does not, which is why it still added 20 mobile points.
How to make your WordPress.com site faster
If you want the same result, do these in order.
Fix the hero image
It is almost always your LCP element. Compress it, size it correctly, and let the site CDN serve it. This single fix moves the mobile score most.
Add width and height to every image
This prevents layout shift (CLS). It is a small, boring change that keeps your CLS at 0.
Install Jetpack Boost (free)
Turn on Critical CSS, defer JavaScript, and the Image CDN. Free, and it does the page-level optimisation the platform cache does not.
Drop unused web fonts
Each custom font is a render-blocking request. Use one or two, or lean on system fonts, and the mobile score thanks you.
Keep the homepage lean
Fewer heavy sections, fewer third-party scripts. The host is fast; do not undo it with a bloated page.
A few things to keep in mind
Honest caveats
- A perfect 100 mobile score is unrealistic for an image-rich page, and you do not need it.
- Critical CSS needs regenerating after big design changes.
- The page cache is the platform's, not a plugin's, so do not double up on caching plugins.
- Your host is not the whole story. Theme, images, plugins and third-party scripts affect your score far more than the server does.
So, is WordPress.com fast enough?
Yes, comfortably.
The speed you would normally pay someone to tune, edge caching, a CDN, WebP, HTTP/3, is handled for you. You bring lean images and good content; the host takes care of the hard part.
It is not the single fastest option on earth, a hand-tuned VPS can edge it out. But it is the fastest option that needs almost no effort, and for most sites that is exactly the right trade. It is the same reason I moved a live site to managed hosting in the first place.
Final take
Speed on WordPress.com is not something you fight for. It is mostly the default.
My stock site was already fast on desktop, and two free changes, a lighter hero image and Jetpack Boost, took mobile from a shaky 65 to a solid 85 with green vitals. No caching plugin, no server tuning, no monthly maintenance.
Build a local business site or a blog on a WordPress.com plan, keep your images lean, and the platform quietly handles the part most people find hardest. New to WordPress entirely? Start with the beginner's tutorial and grow from there.
Want a WordPress site that is fast AND ranks?
Green Core Web Vitals are the floor, not the finish line. If you want a WordPress site engineered for speed, SEO and conversions, send us your goals, the first reply comes from Sunny, not a sales team.
See technical SEOCommon questions
Is a WordPress.com site fast?
Yes. In my test, a stock site scored Desktop 95 / Mobile 65, and after two free tweaks it reached Desktop 99 / Mobile 85 with green Core Web Vitals. WordPress.com handles edge caching, a CDN, WebP and HTTP/3 for you, so the hard part of speed is done by default.
Why is my mobile PageSpeed score lower than desktop?
Because PageSpeed Insights throttles the mobile test to a mid-tier phone on a slow 4G connection, which is far harsher than most real visits. An image-heavy page will always score lower on mobile. Watch your green Core Web Vitals more than the raw score.
Do I need a caching plugin on WordPress.com?
No. WordPress.com applies page caching at the platform level, so a heavy caching plugin like WP Rocket is largely redundant (on Business and Commerce plans, just make sure the global edge cache is enabled). The free Jetpack Boost still helps with page-level tweaks like Critical CSS.
What is Jetpack Boost?
A free WordPress plugin that improves page-level performance: Critical CSS, deferring and concatenating JavaScript, concatenating CSS, and an Image CDN. It is what took my test site's mobile score from 65 to 85, on top of the caching WordPress.com already does.
Is WordPress.com faster than self-hosted WordPress?
A well-tuned self-hosted VPS with LiteSpeed can post a lower cached TTFB, but it takes real sysadmin work. WordPress.com gives you most of that speed with zero configuration. For most people, the effort-to-speed trade strongly favours the managed platform.
Can I get a 100 mobile PageSpeed score?
Rarely on a real, image-rich page, and you do not need to. The mobile test is deliberately harsh, and Google ranks on your field Core Web Vitals (which can all be green at a score of 85), not on a perfect 100 in the lab tool.
How do I test my own site speed?
Run your URL through Google PageSpeed Insights. It gives both lab scores and, if your site has enough traffic, real-user Core Web Vitals. Test the mobile tab, fix the biggest LCP element (usually the hero image), then re-test.
SEO Specialist and product builder with 10+ years in search. The notes come from the work, not the theory.