How to speed up a slow WordPress site

Test the homepage and two or three important pages with a performance tool before changing anything. Record the mobile and desktop results, the largest content element, and whether the delay is caused by the server, images, CSS, JavaScript, or third-party services. Largest Contentful Paint is a useful measure of when the main content becomes visible; a good target is 2.5 seconds or less for most users.

Also check Tools > Site Health. WordPress reports configuration problems, outdated PHP, missing modules, failed loopback requests, and other issues that can affect performance.

Update WordPress, your theme, plugins, PHP, and server software after taking a backup. Deactivate and delete plugins you no longer use, then test the site. If the site becomes faster after disabling one plugin, contact its developer or replace it rather than leaving unnecessary code active. WordPress identifies hosting, theme weight, plugin count, software versions, and image sizes as common performance factors.

If the server remains slow before the page has started rendering, ask your host about CPU, memory, database load, PHP workers, OPcache, and persistent object caching. A persistent object cache can reduce repeated trips to the database, but it requires suitable hosting support.

Resize images to the largest size you actually display, compress them before uploading, and use modern formats such as WebP where your setup supports them. Remove decorative images that do not add useful information, and avoid uploading a 4,000-pixel photograph for a small thumbnail. WordPress recommends reducing image sizes, choosing suitable formats, and considering WebP.

Reduce heavy sliders, autoplay video backgrounds, external fonts, tracking scripts, and page-builder sections that are not needed. Keep the theme and page layouts simple. Minifying CSS and JavaScript can reduce file sizes, but combining or delaying files can break menus, forms, sliders, or layouts, so change one setting at a time.

Ask your host whether server-side page caching is available and enable it if your site serves mostly the same content to visitors. Configure browser caching for static files such as images, CSS, and JavaScript, and use a CDN for visitors who are far from your server. WordPress describes page caching as the quickest performance improvement for many sites, while browser and object caching address different parts of the request.

Do not cache pages that contain customer-specific information. For WooCommerce, exclude Cart, Checkout, and My Account, along with relevant sessions and cookies. Otherwise shoppers can see another customer’s cart, stale account information, or a checkout that does not work.

This manual route is fine for a small, mostly static site if your host already provides page caching and a CDN. The drawback is that you must configure separate systems and know which cache to purge when content or CSS changes.

Make performance changes on a staging copy when possible. If you work on the live site, take a backup, change one option, purge every relevant cache layer, and check the homepage, navigation, forms, search, login, and checkout before continuing.

The recurring failure is cached or minified CSS and JavaScript becoming stale after a theme, plugin, or page-builder update. A page may look broken until the cache is purged, and sometimes browser, server, CDN, and plugin caches all hold different versions. If the layout breaks, disable minification or combination first, clear all caches, and then re-enable options individually.

The fast way is to use one tool that brings page caching, file optimisation, image compression, database cleanup, and CDN support into one dashboard. Seraphinite Accelerator fits sites that need broad performance improvements rather than a single image or cache feature.

Install it from the WordPress admin, activate it, and begin with its recommended or conservative settings. Test the site before enabling more aggressive CSS and JavaScript optimisation. Exclude dynamic pages and logged-in areas, purge the cache after changes, and check WooCommerce, forms, page-builder layouts, and mobile navigation before leaving the settings enabled.