The Five Real Causes, in Order
Let’s clear the air first: WordPress is not slow. This site runs on WordPress, on ordinary shared hosting, and scores 100/100 on Google’s PageSpeed test on mobile, the hard one. No exotic infrastructure, no tricks. WordPress setups are slow, and they’re slow in remarkably predictable ways.
If your site takes four, six, eight seconds to appear, the cause is almost certainly on this list. In fix-this-first order:
1. Page weight: you’re shipping too much
The most common cause is the simplest: the page is huge. A 6 MB photo dropped straight from a phone into the hero. Five font families. A video that autoplays. Sliders. The browser can’t paint what it hasn’t downloaded, and on mobile connections, megabytes are seconds.
The fixes are unglamorous: images resized to the size they display at, compressed, served as WebP; fonts trimmed to the two or three weights actually used; the slider replaced with one strong image (sliders hurt conversions anyway, that’s a separate article’s worth of data). Weight is also the fix with the best effort-to-result ratio: it’s often possible to remove half a page’s bytes in an afternoon without changing how it looks.
2. Plugin bloat: forty little taxes on every visit
Every active plugin can add its own CSS and JavaScript to every page, run its own database queries, hook into every request. One plugin is nothing. Thirty-five plugins, the realistic average we find on sites that come to us, is a tax collected on every single page view. Worse, many load their assets everywhere: the contact-form plugin’s scripts on pages with no form, the shop scripts on the blog.
The fix is an audit, not a purge for its own sake: what does each plugin do, is it still needed, does a lighter alternative exist, and can its assets be restricted to the pages that use them? A recent rebuild took a client site from 23 plugins to 15, and load time from 4.2 s to 1.1 s.
3. No caching: WordPress rebuilds every page for every visitor
By default, WordPress assembles every page from scratch on every visit: PHP runs, the database answers a dozen queries, the HTML is generated. For the ten-thousandth identical view of the same homepage. Page caching stores the finished HTML and serves it instantly to the next visitor. It’s the single biggest server-side speedup available, it’s often a free plugin, and a shocking number of slow sites simply don’t have it turned on (or have it installed but misconfigured, which can be worse than nothing).
If your site is on cheap shared hosting, this is doubly important: caching is how a $10/month server behaves like a $100/month one.
4. Hosting that was never going to be fast
Sometimes the server is genuinely the bottleneck: ancient PHP versions (each major PHP release is meaningfully faster than the last), overloaded shared machines, no server-level caching, databases on spinning disks somewhere far from your visitors. The tell: even a stripped-down page with caching takes over a second to start responding (that’s TTFB — time to first byte).
Honest advice: don’t start here, even though every hosting company’s marketing says to. Weight, plugins, and caching usually deliver more than a hosting upgrade, and a bloated site moved to premium hosting is a bloated site with better scenery. Fix the site first; then judge the hosting on the clean result.
5. Theme and page-builder overhead
Heavyweight multipurpose themes and page builders generate deeply nested markup, load framework CSS/JS for features you don’t use, and add render-blocking assets, a structural tax on every page. This is the hardest cause to fix, because the theme is the site. Realistic paths: aggressive optimization within the builder, or when the business case supports it, a rebuild on a lean custom theme. This site is a custom theme for exactly that reason. Vortano custom theme weighs less than 300 KB, roughly a tenth of what Astra ships, and about 1–2% of a typical page-builder theme.
What mostly doesn’t help (despite the hype)
- “Optimization” plugins stacked on a heavy site — minifying 4 MB of assets produces 3.7 MB of assets. Removal beats compression.
- CDNs as a first move — a CDN distributes your site globally; it doesn’t make a heavy site light. Great later, not first.
- Obsessing over a 100 score — Google’s own guidance is thresholds, not perfection: pass Core Web Vitals and spend the remaining energy on content. The difference between 92 and 100 is bragging rights (we enjoy them, but honestly: bragging rights). The difference between 45 and 85 is customers.
Why speed is a business number, not a vanity number
Google uses page experience in ranking, but the bigger effect is human: slow pages lose visitors before they load, and every additional second measurably increases the percentage who give up. For a site whose job is generating inquiries or sales, speed is conversion-rate infrastructure. That’s also why speed isn’t a one-time project — sites regain weight as content, plugins and updates accumulate, which is why performance monitoring is part of every care plan we run.
Find out which of the five is yours
Run your site through PageSpeed Insights — free, no signup — and look at the opportunities list, not just the score. Or let us do the reading for you: the free Health Check covers performance as one of its seven scored areas, names your specific causes in plain English, and tells you what fixing them would take.