"The website is slow" is one of the most common things a Cincinnati business owner says to us, and it is almost always followed by "I don't know why." The good news is that WordPress sites are slow for a short list of reasons. It is very rarely mysterious, and it is very rarely all five at once.
What follows is the list, roughly in order of how often it turns out to be the culprit, with how to check each one yourself. Do this before you buy an optimization package — you may find your problem is a twelve-dollar hosting decision rather than anything that needs a developer.
First, measure it properly
Your site does not feel slow to you, because your browser has cached it and you are probably on good wifi. Open Google's PageSpeed Insights, put your homepage in, and look at the mobile score, not desktop. Then look at one interior page too — service pages are often much heavier than the homepage because nobody optimized them.
The number that matters most is Largest Contentful Paint: how long until the main thing on the screen appears. Under 2.5 seconds is fine. Four seconds and up is where people start leaving, and Google has been folding these measurements into rankings for years now.
1. Images nobody compressed
This is the single most common cause, and it is usually the easiest to fix. Someone uploaded a photo straight off a phone or a camera — four thousand pixels wide, several megabytes — and WordPress displayed it in a box six hundred pixels wide. The visitor downloads the whole thing anyway.
How to check: right-click an image on your site, open it in a new tab, and look at its dimensions. If your hero photo is 4,032 pixels wide, that is your problem. A properly sized, modern-format image for that slot is usually under 200KB. We have seen homepages drop three full seconds from image work alone.
2. A page builder doing far too much
Page builders make WordPress editable by non-developers, which is genuinely valuable. The cost is that most of them load a large bundle of CSS and JavaScript on every page, whether the page uses those features or not. A simple contact page ends up carrying the code for sliders, tabs, popups, and animations it does not contain.
You cannot really fix this without either changing how the site is built or accepting the overhead. What you can do is stop stacking — a builder plus a heavy multipurpose theme plus a separate animation plugin is three layers doing overlapping work, and dropping one usually helps.
3. Plugin sprawl
Every plugin is entitled to add its own stylesheet and its own script to your pages. Twenty-five plugins means a lot of separate requests, and the ones that hurt most are the ones running on every page for a feature used on one — a contact form library loading site-wide for the single form on /contact, for instance.
How to check: go to your plugins list and count. Then, more usefully, ask of each one: what does this do, and when did we last rely on it? In most audits we run, a third of the installed plugins are doing nothing anyone can name. Deactivating those is free speed, and it also shrinks your security exposure — the two problems are closely related.
4. Hosting that is too cheap to work
A budget shared hosting plan puts your site on a server with hundreds of others. When one of them gets a traffic spike, or runs a badly written query, your site slows down and there is nothing you can do about it from your side. This is the cause people find hardest to accept, because the hosting bill looks like the one thing that is under control.
How to check: look at your server response time in PageSpeed Insights. If the server is taking more than about half a second to send anything at all, the problem is upstream of everything on your site. No amount of image compression fixes a slow server.
This is worth stressing because it is where money gets wasted. We have watched a business pay for a full speed optimization project on a site whose actual constraint was a four-dollar hosting plan. The optimization worked; the site was still slow.
5. Caching that is missing, or doubled
Caching means the server saves a finished copy of each page instead of rebuilding it for every visitor. Without it, WordPress reassembles the entire page from the database on every single request. With it, most visitors get a file.
The failure we see is not usually missing caching — it is two caching plugins installed at different times by different people, quietly fighting. Symptoms are odd: changes that do not appear, logged-in users seeing the wrong thing, pages that are fast sometimes and slow other times. If you have more than one caching plugin active, that is worth untangling before anything else.
What this is actually worth
It is easy to treat speed as a technical vanity metric. It is not. A visitor who waits five seconds on a phone for a contractor's site has usually already gone back to the results page and called the next name down — and you never see that in any report, because they never arrived. Speed is one of the few site changes where the benefit shows up in both rankings and conversions at the same time.
The order to work in: hosting first if the server response is bad, images second, plugin cleanup third, then caching, then the builder question — which is really a rebuild question. Doing it in the other order is how people spend a lot and gain a little.
When speed work stops being worth it
Sometimes the answer is that the site cannot get meaningfully faster without being rebuilt. A ten-year-old theme carrying a decade of plugin decisions has a floor, and you can spend real money getting near it and still land somewhere mediocre. At that point the honest comparison is what you would spend chasing the last second versus what a replacement costs once. Our guide to when a redesign is justified works through that decision, and the Cincinnati website cost guide has real numbers.
If you would rather not work through all this yourself, that is what a WordPress audit is for. We will tell you which of the five applies to your site, roughly what each is costing you in load time, and whether the fix is worth doing — including when the answer is that your site is fine and someone is trying to sell you something.