WordPress Speed Optimization Checklist: Fix the Slow Parts of Your Small Business Website

📅 2026-11-09T05:32:04.365Z
👁️ 52 katselukertaa
🔓 Julkinen


# WordPress Speed Optimization Checklist: Fix the Slow Parts of Your Small Business Website

A slow WordPress site costs you enquiries. Visitors leave before the page finishes loading, and Google treats speed as part of the page experience its ranking systems use. The good news is that most slow WordPress sites are slow for a handful of fixable reasons: weak hosting, oversized images, a heavy theme, too many plugins and no caching. Measure first, fix the biggest problem the measurement reports, then re-test. Work in that order and you will usually get most of the gain without touching code.

For the full step-by-step version of this checklist, [AI SEO Lift Portland](https://aiseolift.com/wordpress-speed-optimization-checklist/) walks through each item with the detail you need to act on it.

## 1. Measure before you change anything

Run your home page, your most important service page and a blog post through PageSpeed Insights on mobile, and save the numbers. The tool reports two kinds of data: field data from real Chrome users over the past 28 days, and lab data from a simulated Lighthouse test. Lab data is useful for debugging because you can change something and test again in a minute; field data tells you whether real visitors are actually having a good experience. The three Core Web Vitals to watch are Largest Contentful Paint (loading, 2.5 seconds or less), Interaction to Next Paint (responsiveness, 200 milliseconds or less) and Cumulative Layout Shift (visual stability, 0.1 or less). A page passes when all three meet their targets at the 75th percentile of page loads. Treat a score of 90 or above as good, but remember Google itself says good scores do not guarantee top rankings — speed is a user-experience and conversion issue first, and a ranking factor second.

## 2. Hosting is the foundation

If your server takes a long time to respond, every other optimisation is working uphill. Warning signs include slow response on otherwise simple pages, slowness that gets worse at busy times, and an admin dashboard that crawls. Bargain shared hosting packs many sites onto one server; for a business that depends on its website for leads, a managed WordPress plan or a small VPS is usually a sensible step up. Check that your host runs a currently supported PHP version, prefer a data centre on the US West Coast if your customers are in Oregon, and use your host's server-level caching if it offers one — do not stack a second full-page cache plugin on top without checking compatibility. Moving hosts is a real project, so handle it carefully.

## 3. Slim down the theme and builder

The theme is the biggest single decision for front-end speed. Multipurpose themes that ship with dozens of demos, sliders and bundled plugins load a lot of CSS and JavaScript on every page, whether you use those features or not. Prefer a lightweight theme and add only the features you need. If you use Elementor or a similar builder, avoid deeply nested sections, stacked animations and decorative sliders — each adds markup and script. Do not load a font family in six weights when you use two, and host fonts locally where you can. If the theme itself is the root problem, a rebuild is often cheaper than endless patching.

## 4. Fix your images first

Images are usually the largest files on a page and the most common reason for a slow Largest Contentful Paint. Resize photos before upload — a 4,000-pixel-wide photo from a phone does not belong in an 800-pixel slot. Use modern formats such as WebP, which WordPress can generate on upload. Set explicit width and height attributes so the browser can reserve space and prevent layout shift. Lazy-load images below the fold only, never the hero image — lazy-loading the hero is a frequent mistake that makes the page feel slower. Give the main hero image fetch priority instead. And replace autoplaying hero video with a well-compressed still image; it usually does the job for a fraction of the cost.

## 5. Use one caching layer

Without caching, WordPress builds each page from scratch by querying the database and running PHP. A page cache stores the finished HTML and serves it directly, which cuts server response time sharply. Use one page-caching layer — either your host's or a single plugin — because two competing caches cause confusing bugs. Enable browser caching so returning visitors do not re-download unchanged files. A content delivery network helps if you have visitors outside your region or heavy static files; for a purely local Oregon audience it is a nice-to-have rather than a requirement. Exclude pages that must stay dynamic: cart, checkout, account pages and anything personalised.

## 6. Test minify and defer settings carefully

Caching plugins offer options to minify CSS and JavaScript, combine files, delay scripts until user interaction and remove unused CSS. These can help, and they can also break your site — aggressive settings are a common cause of menus that stop opening, sliders that vanish, layouts that shift and contact forms that quietly stop submitting. Change one setting at a time, and after each change check the home page, a service page, the mobile menu and your contact form. Submit a real test enquiry and confirm it arrives. Delaying JavaScript is the setting most likely to cause trouble with chat widgets, analytics, reCAPTCHA and forms, so exclude the scripts your lead capture depends on. If a setting barely moves the score, turn it back off. Fewer risky settings is better than a slightly higher lab score.

## 7. Audit plugins and third-party scripts

The number of plugins matters less than what each one does. List every active plugin and write one line on why it exists; anything you cannot justify is a candidate for removal. Deactivate and delete unused plugins and themes rather than leaving them installed. Look for plugins that load assets sitewide when they are only needed on one page, and watch for heavy background jobs such as related-posts widgets and broken-link checkers that run constantly. Audit third-party scripts the same way: chat widgets, review carousels, social feeds, tracking pixels and embedded maps each add requests and JavaScript you do not control. Keep what earns its place, load maps and videos only when a visitor clicks, and remove anything nobody looks at.

## 8. Tidy the database and keep things updated

Over time WordPress accumulates post revisions, spam comments, expired transient data and leftovers from deleted plugins. On a small brochure site this rarely causes dramatic slowness, but it adds up on older sites. Back up before any cleanup, limit stored post revisions, and clear spam and trashed comments. Be cautious with one-click database optimisation plugins — use them on a backup-protected site and avoid deleting data you do not understand. Keep WordPress core, themes and plugins updated; maintenance is part of performance.

## A sensible order of work

Start with a PageSpeed Insights baseline, then fix images and the hero image priority — often the biggest single gain. Turn on one caching layer, remove unneeded plugins and scripts, and only then consider hosting or theme changes, which fix root causes. Test minify and delay settings carefully, and re-measure afterwards. Give field data time: because it reflects a 28-day window, improvements may take weeks to show in the real-user numbers even when the lab score changes immediately. Not sure what is slowing your site down? Request a free SEO audit and a specialist will point out the biggest speed and technical issues for your site.