8 Hidden Factors Slowing Your WordPress Site (and How to Fix Them)

A slow WordPress site looks like a checklist problem. Compress a few images, install a caching plugin, done. Most site owners treat it that way, and most are still slow a year later.

Search “why is my WordPress site slow” and the same decade-old advice shows up: switch to JPEG, add a CDN, disable Flash. None of it reflects how Google grades a page in 2026.

The actual problem: Site owners are optimizing against a 2019 checklist, while Google has scored pages on Core Web Vitals, specifically Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS), since 2021.

We’ve covered the basics of trimming unnecessary weight from a WordPress install before. This goes further, into the eight factors that still catch experienced site owners off guard.

What Changed Over the Years

Here’s the shift in one place:

8 Hidden Reasons Your WordPress Site Loads Slow

1. Unoptimized video embeds are the new flash problem

A single YouTube embed loads between 1.3 and 2.6 MB of JavaScript, CSS, and tracking scripts before anyone presses play. Paste a YouTube URL into the block editor and WordPress converts it to an iframe that pulls in YouTube’s entire player stack: ad infrastructure, font files, analytics, all of it, whether or not the visitor ever clicks.

Vimeo is lighter, but not light. And the trend is moving the wrong way.

Median video weight per page grew 28 percent in a single year, from 246 KB to 315 KB.

Source: HTTP Archive’s 2025 Web Almanac

The fix that matters most is the facade pattern: show a static thumbnail and play button first, load the real player only when someone clicks. That single change can cut a video embed’s initial weight from around 2 MB to under 20 KB.

How to fix it

Build the facade pattern yourself with the iframe srcdoc attribute, or use a plugin like lite-youtube-embed. Or skip the extra plugin: FluentPlayer’s free tier has a Load Strategy setting that defers the full player until the visitor interacts, so the facade pattern is built into the player instead of bolted on separately. Here’s the full breakdown of what a video embed actually costs and how to fix it, including which approach fits marketing pages versus course content.

FluentPlayer is free on WordPress.org if you want to see the Load Strategy setting for yourself.

2. Render-blocking scripts are still the biggest silent cost

Render-blocking JavaScript stops the browser from painting the page until it finishes loading. That was true in 2019 and it’s still true now, except today it also shows up in your Interaction to Next Paint score, since every script that blocks the main thread delays how fast the page responds to a click or a tap.

Unminified CSS and JavaScript compound the problem. Extra whitespace and unused code mean more bytes the browser has to download and parse before anything renders.

How to fix it

Move non-critical JavaScript to load with the defer attribute so it waits until the rest of the page renders. Inline anything small enough that a separate request costs more than it saves. For minification, a plugin like Autoptimize handles CSS and JS in one pass, so you’re not hand-editing files.

3. Your CDN might not exist anymore

If a speed guide recommends MaxCDN, close the tab. MaxCDN was folded into StackPath in 2016, and StackPath itself dissolved and liquidated its CDN business in 2024. The product this advice points to hasn’t existed for two years.

A content delivery network still solves the same problem it always did: serving your site’s static assets from a server near the visitor instead of one across the ocean. That part hasn’t changed. The tools have.

How to fix it

Cloudflare’s free tier covers most small to mid-size WordPress sites and takes about ten minutes to connect through your domain registrar. For video specifically, BunnyCDN Stream handles adaptive delivery so a visitor on a slow connection gets a smaller file automatically instead of buffering on the full-resolution version.

4. Images still cost you the most preventable weight

JPEG hasn’t been the best format for web images for a while. WebP compresses smaller than JPEG at equivalent visual quality, and AVIF compresses smaller still. Most current image optimization plugins convert to WebP automatically now, which is why “just use JPEG” stopped being useful advice.

Oversized dimensions are the other half of the problem. An image uploaded at 4000 pixels wide and displayed at 800 pixels forces every visitor to download five times more data than the page actually shows.

How to fix it

Compress every image before upload. Squoosh (free, browser-based) or a plugin like ShortPixel or Imagify will convert to WebP and strip unnecessary metadata in the same step. Set explicit width and height on images so the browser doesn’t shift layout while the file loads, which also protects your Cumulative Layout Shift score.

5. Bloated themes and plugins add up fast

Every theme and plugin loads its own CSS and JavaScript, and WordPress loads most of it on every page by default, regardless of whether that page actually uses the feature. A page builder theme with a dozen unused widget styles ships all of them anyway.

How to fix it

Audit your active plugins against what the site actually uses. Deactivate and delete anything left over from a feature you tried once. For the theme, a lighter, well-coded option (GeneratePress and Astra are common choices for this reason) beats a heavier one with features you’ll never touch.

6. Database overhead nobody checks

Post revisions, spam comments, transients, and orphaned plugin data accumulate in the background for years. None of it shows up in a PageSpeed report directly, but a bloated database slows every query the page has to run, and on a busy site that adds real latency to every load.

How to fix it

Most hosts give you phpMyAdmin access to clean this manually, or you can run it through WP-CLI if you’re comfortable with the command line. A database cleanup plugin works too, and takes less setup if you’d rather not touch raw SQL.

7. Third-party scripts and ad tags block more than ads

Ad networks were never the only offender here. Chat widgets, heatmap trackers, marketing pixels, and embedded social feeds all load their own JavaScript, and each one adds to your Total Blocking Time and drags down INP the same way a render-blocking script does.

How to fix it

Audit what’s actually loading on your highest-traffic pages using your browser’s network tab. Cut anything you installed once and forgot about. For what you keep, load it with defer or async so it doesn’t block the page while it initializes.

8. Caching gaps still undercut everything else

Every fix above gets undone if the page rebuilds itself from scratch on every visit. Caching stores a static version of the page so the server doesn’t have to run PHP and database queries for every single visitor.

How to fix it

WP Rocket handles page caching, browser caching, and basic minification in one plugin if you want a paid, hands-off option. W3 Total Cache is a solid free alternative if you don’t mind more manual configuration. Either way, confirm your cache actually updates when you publish new content. A stale cache serving old pages is a common, quiet failure.

These Problems Keep Changing

These eight factors aren’t a checklist to run once. They’re what’s slowing a WordPress site down after the fixes are in place, and the list keeps changing. Five years ago, video wasn’t on it. In 2026, it’s the biggest factor.

Run your highest-traffic page through PageSpeed Insights and see which of the eight it’s failing. For video across course content or multiple pages, FluentPlayer Pro adds CDN delivery and analytics on top of what the free tier fixes for speed.