Website Design
Website speed optimization starts with finding the real bottleneck, and on most small business sites it is one of five things: oversized images, cheap hosting, plugin bloat, missing caching, or third party scripts. Some of those you can fix yourself this afternoon. Others are buried in your theme and will eat every weekend you throw at them. This diagnostic walks the causes in the order we actually find them on client sites, labels each fix DIY or hire it out, and gives you a 20 minute triage to run before you spend a dollar.
What Actually Makes a Website Slow?
Five causes account for nearly every slow small business website: images uploaded at full camera resolution, budget shared hosting, too many plugins or a heavy page builder, no caching or CDN, and third party scripts like chat widgets and tracking pixels. Fixing the top one or two usually recovers most of the lost speed.
Here they are, ranked by how often we find them when auditing client sites at Dorian Media Group. On the last 20 or so WordPress sites we have taken over, the first two covered the majority of the problem:
| 1 | Oversized images. The most common offender by a wide margin. A phone photo is 4,000 pixels wide and 3 to 8 MB; your page displays it at 800 pixels. One client’s homepage was loading 41 MB of images. After converting to WebP and resizing, the page went from 9 seconds to under 3. If you check nothing else, check this. |
| 2 | Cheap shared hosting. The $4 to $8 per month plans put hundreds of sites on one server. Your first byte can take over a second to arrive before the page even starts loading. We moved one client from a bargain shared plan to managed hosting and time to first byte fell from about 1.4 seconds to roughly 300 milliseconds with zero other changes. |
| 3 | Plugin and page builder bloat. Every active plugin can add scripts and styles to every page. Sites running 30 plus plugins on top of a heavy builder routinely ship 2 to 4 MB of code before any content appears. The symptom: your site feels sluggish even on fast wifi, and your PageSpeed score sits in the 20s or 30s. |
| 4 | No caching or CDN. Without caching, WordPress rebuilds every page from the database for every visitor. A caching plugin plus a CDN serves prebuilt copies from servers near the visitor. This one is cheap, fast to set up, and often cuts load time by a third or more. |
| 5 | Third party scripts. Chat widgets, heat maps, five tracking pixels, a review carousel, a booking embed. Each one phones home before your page settles. We audited a site carrying 14 third party scripts; the owner could name a business reason for 6 of them. Cutting the rest took half a second off every page. |
The Fixes, Ranked: DIY or Hire It Out
Most website speed optimization fixes split cleanly: image compression, caching, and script cleanup are DIY territory, while hosting migrations and theme surgery are worth paying for. The table below is the honest version of that split, including the effort each fix really takes.
| Fix | DIY or hire | Effort | Typical payoff |
| Compress and resize images (WebP) | DIY | An afternoon | Often the single biggest gain |
| Install caching plugin | DIY | Under an hour | A third off load times |
| Remove unused plugins and scripts | DIY | An evening, carefully | Half a second or more |
| Add a CDN | Either | An hour, some DNS nerves | Faster everywhere, not just near your server |
| Migrate to better hosting | Hire it out | Risky solo, routine for a pro | Second or more off first byte |
| Theme or page builder surgery | Hire it out | Days, breaks things if rushed | Fixes what no plugin can |
Speed Fixes That Backfire
Three common speed fixes make sites slower or break them, and we clean up after all three regularly. Knowing them saves you a weekend and possibly a rebuild.
First, stacking speed plugins. Two caching plugins plus an optimizer do not add up; they fight. We inherited a site last quarter running exactly that combination, and its cache hit rate was near zero because each plugin kept purging the other’s work. Install one tool, remove the overlapping ones the same day. Second, lazy loading everything, including the hero image at the top of the page. Lazy loading below the fold helps; lazy loading the first thing visitors look at delays your Largest Contentful Paint on purpose, which is the exact number you are trying to shrink. Third, aggressive minify and combine settings switched on blind. Those checkboxes break sliders, forms, and checkout flows in ways that only show up on some browsers. Turn them on one at a time and click through your site after each, or let whoever maintains the site do it with a staging copy.
The pattern behind all three: speed tools promise one click results, and one click is how sites break quietly. Change one thing, measure, then change the next.
A 20 Minute Triage You Can Run Today
You can diagnose your own site in about 20 minutes with free tools, no login required. Run this checklist in order and write the numbers down; they become your baseline for judging any fix, and they are the first thing we ask for on a discovery call.
| ✓ | Run your homepage through PageSpeed Insights and note the mobile Largest Contentful Paint number, not just the score |
| ✓ | If LCP is above 2.5 seconds, open the report’s image section; oversized images will be listed by name |
| ✓ | Check time to first byte in the same report; over 800 milliseconds points at hosting, not your content |
| ✓ | Count your active plugins; over 25 on a small business site usually means several are dead weight |
| ✓ | List every widget and pixel on the site, then cross out the ones nobody has looked at in six months |
Ran the triage and the numbers are ugly?
Our website care plans include the full speed diagnosis and the fixes: image pipelines, caching, hosting moves, and the theme level work that free plugins cannot touch. You get the before and after numbers in writing.
When Is It Time to Hire Help for Website Speed?
Hire help when the DIY fixes are done and mobile LCP still sits above 2.5 seconds, when the diagnosis points at hosting or your theme, or when the site earns enough that every slow week costs real revenue. Those three situations share a trait: the remaining work has consequences if it goes wrong.
A hosting migration done badly takes your site down. Theme surgery done badly breaks layouts in places you will not notice for weeks. This is the same reason we tell clients the opposite about images and caching: those are safe to try, so try them first. Budget wise, most one time speed projects land between $300 and $1,500 depending on how deep the theme problems go, and ongoing care plans bundle speed monitoring with updates and backups; our breakdown of website maintenance costs covers what businesses actually pay. One more signal it is time: if your site is slow because it was built slow, a speed project becomes a partial rebuild, and it is worth reading our website redesign cost guide before paying anyone to patch it. We had a restoration contractor come to us for a speed fix this spring; the diagnosis showed a page builder loading 3 MB of unused code on every page, and patching around it would have cost more over a year than rebuilding the templates did once. Sometimes the honest quote is the bigger one.
What Does a Good Website Speed Score Actually Mean?
A good score means your site passes Google’s three Core Web Vitals thresholds with real visitor data: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. Google documents these thresholds at web.dev, and they matter more than the 0 to 100 score most owners obsess over.
The score is a lab estimate. The vitals are measured on actual visitors. We have seen sites score 60 in the lab and pass every vital in the field, and the reverse. Chase the vitals, use the score as a to do list, and if you want the full explanation of each metric, our Core Web Vitals guide goes threshold by threshold. As of the field data we see across client sites, mobile is where sites fail; a site that passes on desktop and fails on mobile fails, because Google indexes the mobile experience.
Frequently Asked Questions
How do I optimize my website for speed?
Start with images: resize them to display size and convert to WebP. Add a caching plugin, remove plugins you no longer use, and cut third party widgets nobody reads. That sequence fixes the majority of slow small business sites. If mobile load time is still over 2.5 seconds after that, the problem is your hosting or theme.
Is there a free way to test my website speed?
Yes. Google’s PageSpeed Insights is free, needs no account, and shows both lab results and real visitor data when your site has enough traffic. GTmetrix and Pingdom are free alternatives worth a second opinion. Test the mobile result, not desktop, and test your money pages, not just the homepage.
What is a good website speed score?
Aim to pass the Core Web Vitals rather than hit a specific score: content visible under 2.5 seconds, responses to taps under 200 milliseconds, no layout jumping. A PageSpeed score above 90 is nice, but we would rather ship a 75 that passes the vitals than a 95 on a page nobody can use.
How much does website speed optimization cost?
DIY fixes cost almost nothing: caching plugins and image tools are free or under $100 a year. Professional one time projects usually run $300 to $1,500 depending on whether the work stops at images and caching or goes into hosting and theme code. Ongoing care plans bundle speed with updates, backups, and monitoring.
Does website speed affect SEO?
Yes, twice. Core Web Vitals are a Google ranking signal directly. And speed changes visitor behavior: slow pages get abandoned before they load, which wastes the ranking you already have. In our client work, speed fixes rarely cause overnight ranking jumps, but they reliably improve the conversion rate of the traffic already arriving.
Dorian Media Group
Get Your Site Under 2.5 Seconds
We diagnose exactly what is slowing your site down, fix what is worth fixing, and show you the before and after numbers. No guesswork, no plugin roulette. Book a call and bring your PageSpeed report if you have run one.
In this article

Social Media Channels