How to Speed Up a WordPress Website

Run the mobile test in PageSpeed Insights first and save three numbers — Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift — before installing anything. A slow WordPress site is usually a slow first byte, a heavy first image, or scripts that delay the first tap, and each of those has a different fix. A laptop feels faster than the report because the browser has already stored the site.

GTmetrix gives a second lab view of the same URL — useful for seeing which single file is heavy. Stop chasing its grade once the three table lines are already in the good range.

A page cache stores the finished HTML of a page and serves that copy to logged-out visitors, so WordPress skips the PHP-and-database build for most traffic — and you enable one cache plugin, never two. On a LiteSpeed server (WebJi®'s cPanel LiteSpeed plans, for example) that plugin is LiteSpeed Cache; leave WP Rocket, W3 Total Cache and WP Super Cache off so they do not write over the same files.

1. Open LiteSpeed Cache → Cache in wp-admin and set Enable Cache to ON. Save.
2. Purge All from the LiteSpeed menu in the admin bar.
3. Open the homepage in a private window while logged out; menus, fonts and buttons should match the admin view.
4. Re-run the mobile PageSpeed test on the same URL and compare with the report you saved.

WP-Optimize can clean the database, but it is not a second page cache next to LiteSpeed Cache. And if the host panel already caches HTML, do not add another cache plugin on top of it. The admin dashboard usually skips the page cache, so the dashboard is not the test — the logged-out private window is.

The plugin count is not the problem — one slider, a second gallery and three analytics tags can cost more than ten quiet plugins, and Interaction to Next Paint measures exactly that pre-tap wait. Deactivate a plugin you no longer use, purge, and reload the private window; if nothing breaks, delete it, because an inactive plugin is still files on the account.

External fonts, ad tags and a second chat widget all add work before the page can answer a tap. Keep one chat and one analytics tag, remove the duplicates, then retest on a phone — desktop Wi-Fi hides the delay. A light theme skips demo templates the homepage never shows; switching themes is a design change, so do it on a copy and repeat the private-window check.

Do this last: the page cache already skips most database work for logged-out visitors, so database cleanup and object caching only pay off on carts, searches and logged-in screens. Delete old revisions, spam comments and expired transients with one cleaner, cap how many revisions WordPress keeps, then purge. Do not run two database cleaners.

A Redis object cache needs a Redis server on the account; it does little for a brochure page that is already cached. Treat it as on only when the plugin reports Connected, then load the cart and one logged-in screen. If mobile Largest Contentful Paint is still over 2.5 seconds after the server, the cache and the images, stop adding plugins — WordPress speed optimization is quoted by email before any work starts.