How to speed up a slow WordPress site

Run the homepage and at least one important internal page through a performance checker on both mobile and desktop. Record the page URL, load time, largest contentful paint, total page size and the biggest recommendations. Test an uncached page and a repeat visit where possible.

Check whether the delay is server response time, image loading, JavaScript work or a specific page. A good largest contentful paint target is 2.5 seconds or less for at least 75% of visits.

Create a restorable backup before changing caching, database data or optimisation settings. Then update WordPress, the active theme and plugins, removing plugins you no longer use. WordPress recommends regular housekeeping, including deleting unwanted plugins and images and keeping the database maintained.

Do not update everything directly on a busy shop if you can avoid it. Use staging first, or update during a quiet period and check the homepage, forms, login, search and checkout immediately afterwards.

Temporarily test the site with a default theme and only essential plugins active. If the site becomes faster, restore the other plugins and theme changes one at a time until the delay returns. Clear all page, server and CDN caches after each meaningful change, or you may mistake an old cached result for a fix.

Use a query or performance monitor to identify slow database queries, excessive PHP work and external requests. If the dashboard is slow too, ask the host about CPU, memory, PHP worker limits and slow-query logs. Support threads repeatedly point to plugin conflicts, resource exhaustion and optimisation features that break JavaScript or AJAX.

Enable page caching through your host or use one caching plugin, not several competing page-cache systems. Page caching serves saved HTML instead of making WordPress rebuild every page request, while browser and object caching can reduce repeated work and database trips.

Start with page cache and browser cache. Then test minification, file combination, deferred scripts and delayed scripts one setting at a time. Purge the cache after changes and check menus, forms, sliders, logged-in pages, search, cart and checkout. Aggressive JavaScript optimisation is a common Friday-afternoon failure: the page may look fast while its buttons or AJAX requests stop working.

Resize images to the largest display size you actually need, compress them, and use modern formats such as WebP or AVIF where your setup supports them. Do not lazy-load the main image visible at the top of the page; it is often the largest content element and needs to start loading promptly. Compress below-the-fold images and avoid uploading huge originals for small thumbnails.

Remove unused fonts, tracking scripts, animation libraries, page-builder widgets and third-party embeds. Do not combine or delay every script blindly. Verify the page on a phone after each change, because a desktop report can improve while the mobile menu or layout breaks.

Remove expired transients, old revisions, spam and trashed content only after confirming you have a backup. Database overhead can accumulate over time, and persistent object caching can reduce repeated trips to the database when the host provides a suitable cache server.

If the site is still slow with a clean plugin test and sensible caching, the bottleneck may be hosting, PHP workers, an overloaded database or an external service. Ask the host to inspect resource limits and slow requests rather than simply restarting PHP. A restart can hide the problem temporarily without fixing the cause.

For a broad first pass, use Firebox Pro to handle caching, image optimisation, database cleanup and mobile tuning from one performance settings area. Apply one group of changes at a time, purge the cache, and retest the same pages used for your baseline.

Keep a backup and test dynamic features after enabling optimisation. Firebox Pro can be a practical choice when you want an all-in-one workflow rather than configuring separate tools, but it does not remove the need to investigate a slow host, a faulty plugin or an expensive third-party request.