A WordPress site can look finished and still be slow. Slow pages lose visitors before they read a word, and they make every other piece of SEO work harder. Before I hand a site over, I run through the same five checks. None of them needs a new plugin purchase or a rebuild. They are the basics, done in the right order.
1. Convert the images to WebP
Images are usually the heaviest part of a small business site. A photo saved as a large PNG or JPG can be several times bigger than the same image as WebP, and the visitor sees no difference.
Before a site goes live, I check every image on the home page and the main service pages. Screenshots and photos go out as WebP. On my own portfolio, the Projects page carries twelve project screenshots — all WebP. If an image is only needed at a small size, it should not be uploaded at full camera resolution either. Resize first, then convert.
2. Turn on caching and clear it after every change
A caching plugin serves a saved copy of each page instead of building it from scratch on every visit. On the sites I work on, that is usually LiteSpeed Cache on Hostinger, but the principle is the same with any caching plugin: turn it on, and clear the cache after every change you make.
The second half matters more than people think. I have seen a site where a fix was live in the editor but the visitor still saw the old page, because nobody purged the cache after saving. Check the live page in a private browser window after every change. If the change is not there, purge the cache and check again.
3. Keep the plugin list short
Every plugin adds code that runs on every page load. A small business site rarely needs more than a handful: a caching plugin, an SEO plugin, a security plugin, a backup plugin, and the ones the business actually uses — a booking form, for example.
Before launch, I open the plugin list and ask about each one: does the site use this, or was it installed for a test and forgotten? Deactivated plugins should be removed, not left sitting there. A plugin that is installed but unused is still a file that needs updating and a risk that needs watching.
4. Make the home page load what it needs, and nothing else
The home page is the first page most visitors see, and it is the page most likely to be overloaded: a slider, a video background, three image galleries, and a chat widget, all loading at once.
I check what actually loads on the home page and remove what the visitor does not need in the first few seconds. A video background can usually become a still image with a play button. A slider with five slides can usually become one strong image and a clear heading. If a chat widget or a map is only needed on the contact page, it should not load on the home page.
5. Test the live site on a phone, on mobile data
The last check is the simplest and the one most often skipped: open the live site on a real phone, on mobile data, and use it the way a customer would. Tap the menu, open a service page, find the phone number or the booking button.
If a button is hard to tap, an image takes seconds to appear, or the menu does not open, fix it before launch. A site that feels fast on a laptop on office wifi can feel very different on a phone on a weak connection — and the phone is where most of a small business's customers are.
That is the whole list. Five checks, in order: images, caching, plugins, home page weight, and a real phone test. Do them before launch, and the site starts its life fast. Skip them, and you will be fixing speed problems after the site is already live — which is always slower, for the site and for you.
Author Bio
Muhammad Asad Bukhari is a freelance WordPress developer based in Lahore, Pakistan. He builds WordPress websites for small and service businesses, including salons and spas, sets up AI automation with n8n workflows, and works on SEO for WordPress sites. His portfolio is at https://asadbukhari.site.
Top comments (0)