“Is WordPress.com actually fast, or am I just paying for convenience with a slow site?”
This is the question most people ask before they commit to it, and honestly, most answers online are just opinions, not real numbers.
So I decided to do the boring but useful thing. I built a real site on WordPress.com, ran Google PageSpeed Insights on it with no optimization plugins at all, then ran it again after adding one free plugin, and I wrote down every number along the way.
In this post, I’ll share the complete before-and-after results, explain why WordPress.com is fast by default, and show you how it compares to shared and self-hosted hosting.
Heads up — this post contains affiliate links. If you start a site through one of them, I may earn a small commission at no extra cost to you. Every PageSpeed number below is from a real test I ran myself.
TL;DR: On a real WordPress.com site, PageSpeed Insights gave me Desktop 95 / Mobile 65 with no plugins. After basic image cleanup plus the free Jetpack Boost plugin, it climbed to Desktop 99 / Mobile 85, with green Core Web Vitals across the board. The platform handles the page caching and CDN for you on every plan, so you don’t really need a paid caching plugin here. The hosting is genuinely fast, and one free plugin does the rest.
How I Tested It
For this test, I didn’t use a blank demo page. I tested the real homepage of a site I had built on WordPress.com — a local business site with a hero section, image cards, a photo grid and a contact form. A normal, image-heavy page, the kind most people actually publish.
The tool I used is Google PageSpeed Insights, which runs on the same Lighthouse engine Google itself uses.
But before we look at the results, there is one thing you should know about its mobile score.
The mobile test in PageSpeed Insights is deliberately strict. It simulates a mid-range phone on a throttled Slow-4G connection, which is far slower than what most of your visitors are actually on. So the mobile number is more of a worst-case stress test than a reflection of real visitor experience.
Someone visiting on a modern phone over Wi-Fi will see something much closer to the desktop number. Keep that in mind as we go through the scores.
The First Result: No Optimization Plugins
Let’s start with the stock site, with no caching or optimization plugins added. This was just WordPress.com’s own hosting, which already includes a global edge cache and a CDN on every plan.
The result was Desktop 95 and Mobile 65. The desktop score is excellent for putting in zero effort.
The mobile score of 65 looks low, but when I looked closer, the cause wasn’t the hosting at all. It was my page. A large hero photo and a couple of render-blocking web fonts were getting hammered by that Slow-4G simulation.
💡 Observation: On mobile, Largest Contentful Paint was 6.5s (basically the hero image loading slowly), while layout shift and blocking time were already near zero. That pattern — a slow image but stable everything else — points to the page, not the server.
Why WordPress.com Is Fast by Default
Before we optimize anything, let me explain why a stock site already scored 95 on desktop. WordPress.com simply turns on the expensive, hard-to-configure parts of performance for you, the kind of things you would normally pay a developer or a premium host to set up.
- Global edge cache: a static version of your site is served from a network of 28+ data centres across six continents, according to WordPress.com’s own performance documentation. So a visitor in Sydney is served from a nearby location, not from a single server far away.
- Built-in CDN for media: the Jetpack-powered Site Accelerator automatically resizes your images and serves them as WebP from that same network.
- HTTP/3 and modern infrastructure on every plan, including the cheapest one, with nothing to switch on yourself.
The number that really shows this is Time to First Byte.
Time to First Byte (TTFB) measures how long the server takes to start sending back the page after a request. A low TTFB means the server and the network are quick, and it’s the part of speed that a caching plugin on its own cannot really fix for you.
In independent 2026 hosting benchmarks across 29 hosts, WordPress.com posted a global TTFB of around 69ms, which placed it among the three fastest providers tested (Hostingstep). A separate review by WPBeginner recorded an average TTFB of about 288ms with sub-second full page loads in most regions (WPBeginner).
So the server-and-network side is genuinely strong here, and that’s exactly the part WordPress.com already handles for you.
What I Changed (All Free)
To improve the mobile score, I did just two things, and neither of them cost any money.
- Basic image cleanup: I lazy-loaded the below-the-fold images, gave them proper width and height (which keeps layout shift at zero), and served the hero image from the site’s own CDN instead of a third-party link.
- The free Jetpack Boost plugin: I turned on Critical CSS, Defer Non-Essential JavaScript, Concatenate CSS/JS, and the Image CDN (auto-WebP).
One thing worth noting here is that WordPress.com runs the page cache itself, so Boost flagged that option as already handled and greyed it out. So the plugin’s real job in this case was Critical CSS and deferring scripts, which is the page-level work a managed host usually leaves to you.
The Result After the Plugin
Same page, same test, just after those free changes. Here’s the mobile result:
The mobile score climbed from 65 to 85. The mobile LCP nearly halved, going from 6.5s down to 3.7s, and both Total Blocking Time and Layout Shift stayed at zero.
And here is the desktop result, which went up to a near-perfect 99:
That 0.6s desktop LCP is the part I really like. It means the server responded quickly, the cache did its job, and the page painted almost instantly. The only thing keeping mobile away from 100 is that throttled-image simulation, which affects every visual site on every host.
Before and After, Side by Side
Here’s everything in one place so you can see the difference at a glance:
| PageSpeed metric | No plugins | With free plugin |
|---|---|---|
| Desktop Performance | 95 | 99 |
| Mobile Performance | 65 | 85 |
| Mobile LCP | 6.5s | 3.7s |
| Desktop LCP | 0.9s | 0.6s |
| Cumulative Layout Shift | 0 | 0 |
| Total Blocking Time | 20ms | 0ms |
| Accessibility | 92 | 96 |
| Best Practices | 100 | 100 |
How It Compares to Shared and Self-Hosted Hosting
This is really the question behind the question, because “fast” only means something when you compare it to an alternative.
On cheap shared hosting, you usually get none of this for free. The 2026 benchmarks show cached TTFB on budget shared plans drifting up toward 380ms (for example, entry-level Bluehost), compared to WordPress.com’s roughly 69ms global figure (Hostingstep). And on shared hosting, you still have to install and configure a caching plugin and a CDN yourself just to get close.
A well-tuned self-hosted setup can certainly beat WordPress.com. A high-frequency VPS running LiteSpeed has posted a cached TTFB of around 80ms in the same tests. But that’s a setup you have to build and maintain yourself. So the honest comparison looks something like this:
| Setup | Speed out of the box | Work required from you |
|---|---|---|
| WordPress.com | Fast — edge cache + CDN on every plan | Almost none; one free plugin tops it off |
| Cheap shared hosting | Slow to average until configured | Install caching plugin + CDN yourself |
| Managed WP host (Kinsta, etc.) | Fast | Low, but costs more per month |
| Self-hosted VPS + LiteSpeed | Fastest possible | High — you are the sysadmin |
💡 Observation: WordPress.com isn’t the absolute fastest option out there. But it is the fastest option that needs almost no work from you. For most bloggers and small businesses, that’s a very fair trade.
Why Mobile Scores Lower Than Desktop
This is something that confuses a lot of people, so let me explain it simply.
The PageSpeed mobile test throttles your page down to a budget phone on a slow mobile network. On a real, image-rich page, a hero photo will always take a couple of seconds to arrive over that simulated connection. This is why a literal mobile 100 is almost impossible for any visual site, on any host.
The numbers that actually reflect the hosting — Layout Shift at 0, Total Blocking Time at 0, and a desktop LCP of 0.6s — are basically perfect. That’s the platform being fast. A mobile score of 85 is a strong, real-world result for a content page, and it sits well inside Google’s “good” Core Web Vitals range.
If I had to give one rule, it would be this: aim for green Core Web Vitals, not a perfect score. Green vitals are what Google uses for ranking and what your real visitors actually feel.
Do You Need a Caching Plugin on WordPress.com?
For page caching, the honest answer is no. WordPress.com runs that at the platform level on every plan, which is exactly why Jetpack Boost greyed the option out for me. Installing a heavy caching plugin like WP Rocket on top of it would be mostly redundant here anyway.
What a free plugin does still add is the page-level work the host doesn’t touch, like Critical CSS, deferring JavaScript, and combining files. That’s exactly what gave me the jump from 65 to 85 on mobile. On a self-hosted site, you would normally reach for a premium caching plugin like WP Rocket to get all of that in one place, but on WordPress.com, the free Jetpack Boost already covers it.
How to Make Your WordPress.com Site Faster
If your own WordPress.com site is scoring lower than you’d like, here’s the order I would work in, starting with the changes that give the biggest wins:
- Fix your hero image first. It’s almost always the LCP element. Compress it, size it correctly for where it appears, and don’t lazy-load the one image that sits above the fold.
- Give every image a width and height. This is the easiest way to keep Cumulative Layout Shift at zero.
- Install Jetpack Boost (free) and turn on Critical CSS, Defer JS, and the Image CDN. Just remember to regenerate Critical CSS whenever you change your theme.
- Drop unused web fonts. Render-blocking fonts were half of my mobile problem. Stick to one or two weights.
- Keep your homepage light. A wall of sliders, embeds and third-party scripts will slow down any host. A leaner page scores higher everywhere.
None of this costs money, and the first three points alone got me most of the way there.
A Few Things to Keep in Mind
There are a few things the screenshots won’t tell you, so let me be upfront about them:
• A mobile 100 isn’t realistic for an image-rich page on PageSpeed’s throttled test, on any host. Aim for green Core Web Vitals instead of a perfect score.
• Critical CSS needs regenerating after you change your design or theme, otherwise it can go stale and hurt your score.
• The page cache is WordPress.com’s, not the plugin’s, so the free plugin mainly adds Critical CSS and JS deferral on top.
• Plugins are available on the cheaper plans now, so you can install Jetpack Boost yourself; the built-in page caching applies on every plan regardless.
• Your numbers will vary depending on your theme, your images and how heavy your homepage is. A lighter page always scores higher.
So, Is WordPress.com Fast Enough?
Yes, comfortably. You get a global CDN, edge caching and HTTP/3 on every plan without touching a single setting, which is why desktop scored 95 before I did anything. Add one free plugin, and mobile follows.
It won’t out-benchmark a hand-tuned LiteSpeed VPS, but it doesn’t really need to. For a blog or a small business site, the speed is well past “good enough” and firmly into “genuinely fast,” and you get all of it without any maintenance.
My take: the kind of speed you’d normally hire someone to tune is mostly handled for you here. So you can spend your time on lighter images and good content, while the host takes care of the hard part.
FAQ
Is WordPress.com fast?
Yes. In my test a stock site scored 95 on desktop PageSpeed with no plugins, thanks to the built-in global CDN and edge cache on every plan. After a free optimization plugin it reached 99 desktop and 85 mobile. Independent 2026 benchmarks also put its global TTFB at around 69ms, among the fastest hosts tested.
Why is my mobile PageSpeed score lower than desktop?
PageSpeed’s mobile test simulates a mid-range phone on a throttled Slow-4G connection, so image-heavy pages always score lower on mobile than on desktop. Real visitors on modern phones and Wi-Fi experience speeds much closer to the desktop score.
Do I need a caching plugin on WordPress.com?
Not for page caching, since WordPress.com runs that for you on every plan, so a plugin like WP Rocket is largely redundant. A free plugin like Jetpack Boost still helps by adding Critical CSS and deferring JavaScript, which lifted my mobile score from 65 to 85.
What is Jetpack Boost?
Jetpack Boost is a free WordPress performance plugin from Automattic. It generates Critical CSS, defers non-essential JavaScript, combines CSS/JS, and serves images from a CDN as WebP, which is the page-level tuning a managed host usually leaves to you.
Is WordPress.com faster than self-hosted WordPress?
It is faster than most cheap shared hosting out of the box, where TTFB can drift toward 380ms. A well-tuned self-hosted VPS with LiteSpeed can beat it (around 80ms cached TTFB), but that requires setup and maintenance that WordPress.com handles for you.
Can I get a 100 mobile PageSpeed score?
On a page with real images, almost never, because PageSpeed throttles mobile very hard. Aim for green Core Web Vitals (good LCP, zero layout shift, low blocking time) rather than a perfect 100, which matters more for real users and SEO.
How do I test my own site speed?
Run your homepage through Google PageSpeed Insights (pagespeed.web.dev), check both the Mobile and Desktop tabs, and focus on the Core Web Vitals — Largest Contentful Paint, Cumulative Layout Shift and Interaction to Next Paint.
Summing Up!
To sum up, WordPress.com is fast where it really counts. With no plugins, it already scored 95 on desktop, and with one free plugin plus a little image cleanup, it reached 99 desktop and 85 mobile, with green Core Web Vitals across the board. The independent benchmarks back up that sub-100ms server speed too.
If you want a fast site without turning into a performance engineer, this is a genuinely good setup. You can start a site on WordPress.com here.
If you want to read more from my WordPress.com testing, here’s how I moved a live site to managed hosting, how I built a local business site with online booking, which plugins actually work on the cheaper plans, and if you’re just starting out, my WordPress tutorial for beginners.
So what does your homepage score on PageSpeed right now, and is mobile dragging you down? I would love to hear your numbers in the comments.
Happy blogging, folks!
