What should you measure before you change WordPress?
A slow WordPress site is usually a slow first byte, a heavy first image, or scripts that delay the first tap. Open PageSpeed Insights, run the mobile test, and save Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift before you install anything. A laptop feels faster because the browser already stored the site.
| Check | Good line | Change this if it fails |
|---|---|---|
| Largest Contentful Paint | 2.5 seconds or less | The hero image, then the server response |
| Interaction to Next Paint | 200 milliseconds or less | Extra scripts and a heavy plugin |
| Cumulative Layout Shift | 0.1 or less | Missing width and height, or a late font |
| Server response | Not a Core Web Vital | If HTML is late, fix PHP and the page cache before images |
GTmetrix is a second lab view of the same URL. Use it to see which file is heavy. Do not chase its grade once the three lines in the table are already in the good range.
Making a site in WordPress, making one that looks like another site, or making a B2B catalogue is a different job. Finish that first. This checklist starts only after the homepage is already online.
How do you cut time to first byte?
Time to first byte is the wait before any HTML arrives. If that wait is long, an image plugin will not fix it. On WordPress hosting at WebJi® the server is LiteSpeed. In the panel, select the newest PHP release the theme and plugins support, then load the homepage and one form.
If the site goes white, switch the previous PHP release back on and read the error log before you add a plugin. Do not leave the site on a PHP release that no longer gets security fixes.
It worked when a second mobile test shows a shorter server response and the form still submits. If the response is still the slow part, email the URL and the test time to support@webji.services. The office phone is not the support queue.
How do you turn on one page cache?
WordPress builds each visit from PHP and the database. A page cache stores the finished HTML and serves that copy to logged-out visitors. Use one plugin. On LiteSpeed, 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.
- In wp-admin open LiteSpeed Cache, then Cache, and set Enable Cache to ON. Save.
- In the admin bar, open the LiteSpeed menu and choose Purge All.
- Open the homepage in a private window while logged out. Menus, fonts, and buttons should match the admin view.
- Run the mobile PageSpeed test on that same URL again. Compare it with the report you saved.
WP-Optimize can clean the database. It is not a second page cache next to LiteSpeed Cache. If the host panel already caches HTML, do not add another cache plugin on top of it.
It worked when a logged-out private window is quicker and the layout matches. The admin often skips the page cache, so the dashboard is not the test.
How do you shrink images without delaying the hero?
The largest image on the first screen is often the Largest Contentful Paint element. Export it near the width of the column, as WebP, and upload that file. Do not upload the camera original and expect CSS to shrink the download. The browser still fetches the big file.
Lazy-load images below the fold. Leave the hero eager, with width and height set, so the layout does not jump. A WebP conversion covers the library already in the media folder.
It worked when that hero file is smaller in the waterfall, or it is no longer the Largest Contentful Paint element. Purge the page cache before you retest, or you will score the old image.
Which plugins and scripts should you remove?
The count of plugins is not the problem. One slider, a second gallery, and three analytics tags can cost more than ten quiet plugins. Deactivate a plugin you do not use, purge, and reload the private window. If nothing breaks, delete it. An inactive plugin is still files on the account.
External fonts, ad tags, and a second chat widget add work before the page can answer a tap. That wait is what Interaction to Next Paint measures. 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 of the site and repeat the private-window check. Customizing the theme, or duplicating the whole site, is not a speed step.
When does a CDN help visitors in India?
A CDN keeps images, CSS, and JavaScript closer to the reader. If the site and its readers are both in India, and the server is already in India, the HTML first byte may barely move. The change shows up on heavy files, and for readers outside India.
Turn a CDN on only after the page cache works. If Cloudflare or QUIC.cloud sits in front, purge that copy when you purge LiteSpeed, or the edge keeps the old CSS. There is no fixed percent to expect. The second mobile test is the result that counts.
Full-page caching at the CDN can also store HTML. Exclude the cart, checkout, and account URLs so one shopper does not see another person's page.
When should you clean the database or add Redis?
Do this last. The page cache already skips most database work for logged-out visitors. Delete old revisions, spam comments, and expired transients with one cleaner, then purge. Cap how many revisions WordPress keeps. Do not run two database cleaners.
A Redis object cache helps carts, searches, and logged-in screens that skip the page cache. It needs a Redis server on the account, and it does little for a brochure page that is already cached. Treat it as on only when the plugin says 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 at support@webji.services before any work starts. Send the URL and the PageSpeed link. Do not call the office number for that ticket.
Frequently Asked Questions
How can I speed up my WordPress site?
Measure the mobile URL in PageSpeed Insights. Move PHP to a supported release, enable LiteSpeed Cache only, shrink images to WebP, and remove plugins you do not use. Retest in a private window. Add a CDN or Redis only after those steps.
Which is better, WP-Optimize or LiteSpeed Cache?
On a LiteSpeed server, LiteSpeed Cache is the page cache. WP-Optimize can clean the database. It is not a second page cache. Use one page-cache plugin. Two caches fighting over the same HTML can serve a stale or broken page.
Why is my WordPress site slow on a phone?
The phone test uses a slower network and the real Largest Contentful Paint image. A desktop score hides that image, extra fonts, and scripts that delay the first tap. Fix the mobile report, then retest on a phone.
Will a CDN speed up WordPress for visitors in India?
It can speed images and scripts, and it helps readers outside India. If the server is already near the reader, the HTML first byte may not change. Purge the CDN when you purge the page cache, and judge it with a second test rather than a fixed percent.
How do I know the WordPress speed fix worked?
The private window matches the live layout, the form or cart still works, and the mobile PageSpeed report shows a shorter Largest Contentful Paint or a shorter server response than the test you saved. A higher score with a broken menu is a fail.
What if the site is still slow after cache and images?
Email the URL and the PageSpeed link to support@webji.services. Speed work is quoted before it starts. Do not stack more cache plugins, and do not call the office number for a performance ticket.