How to speed up a slow WordPress site

Test the homepage and one slow internal page with a page-speed tool and your browser’s developer tools. Record the mobile result, the server response time, the largest image, and any unusually large CSS or JavaScript files. Do not judge the site only from an already-cached browser tab.

Also check Tools > Site Health. It can flag outdated PHP, loopback failures, missing updates and other configuration problems that affect performance.

Page caching is normally the biggest improvement for a site that serves mostly public content. It saves rendered HTML so WordPress does not rebuild the page from PHP and the database for every visitor. Your host may provide server-level caching; otherwise use one caching plugin.

Do not run two page-caching systems at the same time. After enabling caching, clear every existing cache and test logged-out pages, menus, forms and mobile layouts. WordPress has no page cache by default, and cached changes may not appear until the relevant cache is cleared.

Resize images to the dimensions they are actually displayed at, compress them, and use a suitable modern format where your workflow supports it. Large images increase transfer time even when the rest of the page is well cached. Avoid uploading a full-size camera image when a much smaller version is sufficient.

Minify CSS and JavaScript only after making a backup. Combining or delaying files can break menus, sliders, forms or page builders, so enable one optimisation setting at a time and check the front end after each change.

Deactivate and delete plugins you do not use, replace an unnecessarily heavy theme, and remove widgets, tracking scripts and external embeds that add no value. Test plugins selectively if the slowdown started after an update or installation. WordPress’s performance guidance specifically recommends disabling unnecessary plugins and checking their effect individually.

Keep WordPress, the theme and plugins updated, but take a backup first. If an update causes a Friday-night failure, rename the plugins folder through your host’s file manager or FTP to disable all plugins temporarily, then restore and reactivate them one at a time.

If the server response remains slow with page caching enabled, the bottleneck may be hosting, PHP, database queries or traffic rather than the browser assets. Ask the host whether PHP OPcache, persistent object caching and suitable resource limits are available. A CDN can reduce the distance and server work involved in delivering static files.

Do not treat increasing the WordPress memory limit as a complete speed fix. It can hide the underlying problem. For persistent slowness, inspect slow logs or use a profiling service to find slow database queries, PHP functions and external requests.

For one ordinary WordPress site, WP Fastest Cache Premium is a practical shortcut because it puts page caching, browser caching, compression, minification, cache preloading, mobile caching and CDN support in one plugin. Upload the plugin ZIP through Plugins > Add New > Upload Plugin, activate it, then enable page caching first.

Clear the cache and test the homepage, a post, search, forms, login, mobile views and any shop pages. Add minification, compression, preloading and CDN settings one at a time. Exclude cart, checkout, account and other personalised pages from full-page caching where needed. If a layout breaks, turn off the last setting, clear all caches and retest rather than enabling another cache plugin.