Updated October 9, 2026.
If your WordPress website feels slow, start by finding out where the time goes. Buying a new hosting plan or installing another optimization plugin before measuring can add cost without fixing the main problem.
This guide helps an owner work with the person maintaining an existing site. The same measure, change and retest process applies to general web builds; the WordPress-specific steps concern plugins, caching and the database. For a broader view of speed and inquiry quality, see our website optimization guide.
1. Establish a useful baseline
Choose pages that represent the site: the homepage, a main service page, a content-heavy page and the contact path. For a store, include a product page and the buying journey.
Record the date, URL, device conditions, observed delay and test result. Run comparable tests more than once. PageSpeed Insights combines lab diagnostics with real-user data when enough samples are available. Missing field data does not mean the page passed or failed.
Describe the symptom in plain language:
- The server takes a long time to start returning the page.
- The main image appears late.
- Content shifts while loading.
- The menu or form responds slowly.
- A booking or payment service is the part that stalls.
Those observations help the maintainer choose the next investigation. A single score does not identify which tool to buy.
2. Protect the working site before changing it
Have a current backup of files and the database, a tested way to restore it, and a staging copy for changes that could affect functionality. WordPress’s hardening guidance includes maintaining software and recoverable backups.
Record the active theme, plugins, hosting features and outside services. Identify which tool currently handles caching, image processing and script optimization. Two products can overlap without improving the result.
Make one planned change at a time so you can compare results and reverse it if necessary. On a store or membership site, agree how new orders, accounts and submissions will be preserved if rollback is needed. Restoring an old database without reconciliation can discard newer records.
3. Review images and outside scripts
Start with the actual files the browser downloads. An image displayed at a modest size may still be delivered as a very large file. Check dimensions, compression and whether the page sends a suitable version to the device.
Use lazy loading for images that are not initially needed. Do not automatically lazy-load the prominent image visible when the page opens: web.dev’s image loading guidance explains that delaying initially visible images can harm performance. Our image-format guide covers format choices and practical image preparation.
Next, list chat widgets, maps, videos, analytics and booking tools. Ask whether each is needed on every page and whether there is a lighter presentation. Retest the associated customer task after changes; delaying a script is not a useful improvement if it breaks the form or checkout.
4. Coordinate caching with the host
Caching reuses previously generated responses or assets. WordPress’s optimization handbook describes page caching and other performance factors. The right configuration depends on the site’s content and hosting.
Before adding a plugin, ask the host or maintainer:
- Is page caching already enabled at the server or another layer?
- Which pages, cookies and logged-in sessions must bypass shared caches?
- How are updates published and old copies invalidated?
- Which optimization features overlap with the current plugin setup?
For WooCommerce, follow the official caching exclusions: cart, checkout and account pages need special handling. Do not apply a blanket cache-everything rule to personalized or transactional responses.
Test with separate browser sessions and appropriate test accounts. Confirm that carts, login state and private information stay separate, and that updated content appears correctly. Cache configuration is part of correctness, not just speed.
A CDN can help deliver eligible assets, but product features, billing and cache behavior vary. Review the provider’s current documentation with the maintainer. DNS changes are not a routine speed shortcut; preserve mail and verification records and plan the cutover if a change is actually needed.
5. Investigate plugins and server work
If the server response remains slow, have the maintainer review resource limits, application logs and slow database activity. Compare what happens with and without caching. Upgrade hosting when the evidence points to a capacity or configuration issue, rather than using price as a proxy for quality.
Check for unnecessary features and outdated software. Test plugin removal on staging, including any forms, layouts or scheduled tasks it supplies. Use supported software versions compatible with the site’s components, and plan important updates with recovery in mind.
Avoid database cleanup by guesswork. A revision may be useful recovery history, and unfamiliar metadata may belong to a live feature. Before deleting anything, identify its owner and purpose, back it up, review the proposed deletion and test the effect. Database tuning should address a demonstrated issue rather than serve as a universal monthly cleanup ritual.
6. Verify customer tasks and record the result
Repeat the baseline tests under comparable conditions, then test what the site is for:
- Navigation and readable layouts on mobile and desktop.
- Contact form validation, submission and delivery.
- Search, booking, login or checkout where applicable.
- Fresh content after an edit, with caches refreshed appropriately.
- Keyboard access and visible focus through the main task.
Keep a short change log: issue, adjustment, before-and-after evidence, functional checks and rollback instructions. Report the measured improvement for the tested pages and conditions. Do not turn one result into a guarantee of rankings, sales or a fixed improvement on every page.
When to consider a broader build
If repeated fixes cannot meet the site’s requirements at a reasonable cost, compare a focused repair with a broader replacement. Use our refresh-versus-redesign guide to frame that decision. A working WordPress site does not need to move platforms solely because another tool is available.
Our website development services use Astro for new builds. For an existing WordPress site, confirm which performance tasks your hosting agreement covers and arrange any additional work with an appropriate maintainer.