A website can look beautiful and carry all the right information, yet still fail if it takes too long to load. Think of the last time you opened a website on your phone and waited several seconds for anything useful to appear. You probably closed it and moved on. Your potential customers do exactly the same.
For a small business, a slow website is more than a technical inconvenience. It affects whether visitors trust the brand, complete an enquiry form, browse products or make a purchase. In Nigeria this matters even more, because most visitors arrive on mobile phones, often on inconsistent connections and with data they pay for.
WordPress can power anything from a simple business website to a full online store, but installing it does not make a site fast. Hosting, themes, plugins, images, scripts and configuration all affect performance. The good news is that most speed problems can be found and fixed with a structured approach.
In short, to speed up a WordPress website, measure it first, then work through the biggest problems in order: reliable hosting, properly sized and compressed images, correctly configured caching, fewer unnecessary plugins and scripts, and up-to-date software. Test that the site still works after every change, and measure again.
1. Start by measuring your website’s speed
Before changing anything, find out how the website performs today. It is easy to install several optimisation plugins and assume the site is faster, but without testing before and after, there is no way to know whether the changes helped.
Google PageSpeed Insights is a good starting point. Enter the address of a page and review both the mobile and desktop reports. Do not test only the homepage, because service pages, product pages, blog posts and contact pages can load very differently.
PageSpeed Insights gives two kinds of information. Lab data comes from a controlled test and is useful for diagnosing a specific page. Field data, when available, reflects real visitors’ experiences over the previous 28 days. A new or low-traffic website may not have enough visitors for field data yet, and that does not mean anything is broken.
Lighthouse in Chrome, GTmetrix and the Core Web Vitals report in Google Search Console are also useful. Compare the same page under similar conditions each time. A single score is a snapshot, not the full story.
2. Understand Google’s Core Web Vitals
Core Web Vitals are the measures Google uses to judge three parts of a real visitor’s experience: how quickly the page loads, how quickly it responds and how stable it stays while loading. Google treats a page as “good” when at least 75% of visits meet each target.
| Metric | What it measures | Good target | Common cause of problems |
|---|---|---|---|
| Largest Contentful Paint (LCP) | How quickly the main visible content loads | 2.5 seconds or less | Large banner image, slow server |
| Interaction to Next Paint (INP) | How quickly the page responds to taps and clicks | 200 milliseconds or less | Heavy JavaScript |
| Cumulative Layout Shift (CLS) | How much the layout jumps while loading | 0.1 or less | Images or adverts without reserved space, late-loading fonts |
If the main banner or heading takes too long to appear, visitors feel the page is still loading, so LCP suffers. Optimising the largest visible image, improving server response and removing files that block the page from displaying all help. A page can also appear quickly but feel sluggish when someone taps the menu or submits a form. That is usually too much JavaScript, and it shows up in INP. And if you have ever tried to tap a button just as the page shifted and moved it, you have experienced the problem CLS measures. Setting image dimensions and reserving space for embeds prevents it.
Core Web Vitals are part of how Google assesses page experience, but they do not guarantee higher rankings. Useful, relevant content still matters most. Treat a good score as one part of building a website that serves visitors well.
3. Choose reliable hosting
No amount of optimisation can fully make up for weak hosting. The hosting server is where WordPress runs, the database is processed and files are sent to visitors. If it is slow or overloaded, visitors wait before the page even begins to appear.
When choosing hosting for a Nigerian business, consider the type of website, expected traffic, support quality, server resources, backups and security. A local audience does not mean the server must be in Nigeria. What matters is measured response time, network quality and the provider’s reliability.
A reputable shared hosting plan may be enough for a small brochure website. A busy online store or a site with demanding plugins may need managed WordPress hosting or a virtual private server (VPS). Do not choose a plan on “unlimited” claims alone; check the processing power, memory, storage type and usage limits. A content delivery network (CDN), which serves images, stylesheets and scripts from locations closer to visitors, can help, but it does not replace a healthy main server.
4. Optimise images before uploading them
Images are often the largest files on a business website. A photo straight from a phone can be several megabytes, even when it is shown in a small space on the page.
Resize every image to the size it will actually be displayed at. There is no need to upload a 4,000-pixel-wide photo when the design only needs 900 pixels. Compress images while keeping the quality acceptable, and use modern formats such as WebP or AVIF where possible; WordPress and many image tools can produce these for you. Give images descriptive file names and useful alternative text, which helps accessibility and search. Set each image’s width and height so the browser can reserve its space, and lazy-load images further down the page so they only load when needed. The one exception is the main banner image at the top of the page: lazy-loading it slows down LCP.
A real estate website is a good example. Uploading every property photo at full camera resolution makes listing pages needlessly heavy. A consistent resizing and compression routine keeps galleries attractive without making every visitor download oversized files.
5. Use caching correctly
WordPress builds pages on demand. Each visit can mean running code, querying the database and assembling the page. Caching saves a ready-made copy so the server does not rebuild everything for every visitor.
A page-caching plugin can make a noticeable difference. Depending on your host, options include LiteSpeed Cache (on LiteSpeed servers), WP Super Cache and W3 Total Cache. Some hosts provide caching at server level, which should be used instead of, or carefully coordinated with, a plugin.
Caching is not a matter of switching on every setting. Shopping carts, checkout pages, account pages and other personalised content usually need to be excluded. After setting up a cache, test forms, login, search, cart and checkout, and clear the cache after design or content changes if visitors still see the old version. Browser caching and a CDN add further layers, and all of them should be set up to work together rather than compete.
6. Review your theme and plugins
Themes and plugins are what make WordPress so flexible, but each one can add code, scripts, stylesheets, database queries or outside requests.
Start by reviewing what is installed. Remove plugins you no longer use, replace tools that overlap, and avoid installing a plugin for something the theme or a small piece of well-written code can handle. Judge plugins by their actual impact rather than their number: one badly built plugin can slow a site more than several light ones.
The same applies to themes and page builders. An impressive-looking theme may load sliders, animations and icon libraries the business does not need on every page. Choose a theme that delivers the design without the extra weight, and keep page-builder layouts purposeful. Before removing or replacing anything on a live website, take a backup and test on a copy of the site first, sometimes called a staging site, because a plugin may be running a critical form, payment or security feature.
7. Reduce unnecessary JavaScript and CSS
JavaScript and CSS control how a website behaves and looks. The problem is not that these files exist, but that too many large files, or files loaded where they are not needed, delay the page and its response to visitors.
Useful techniques include minifying files (removing unnecessary characters from the code), removing unused CSS, and deferring or delaying scripts that are not needed straight away. Be careful with aggressive settings, though. Combining or delaying scripts can break menus, sliders, page-builder sections, analytics, chat tools and forms. Change one setting at a time, clear the cache and test the key pages on desktop and mobile.
Outside services deserve a review too. Live chat, tracking pixels, embedded maps, social feeds and advertising scripts all add weight. Keep only those that serve a clear business purpose.
8. Keep WordPress, PHP and the database healthy
Outdated software creates security and compatibility problems, and newer versions often run faster. Keep WordPress, themes and plugins updated, and use a version of PHP (the programming language WordPress runs on) that both WordPress and your host support. Always back up first and test updates, especially on sites with custom code or an online store.
Over time the database collects old post revisions, spam comments and expired temporary data. Clean-up tools can help, but they are not a magic speed button. Take a backup, understand what is being removed, and never run an aggressive clean-up on a live store without testing. For larger, busier sites, object caching at server level can reduce repeated database work; it is usually set up with your host or a developer.
9. Make mobile performance a priority
A website is not fast just because it loads quickly on a developer’s laptop on office Wi-Fi. Most Nigerian customers browse on phones, with very different connections, devices and data budgets.
Test the mobile version of your key pages. Check whether the banner image is too large, whether pop-ups cover the content, whether text is readable and whether buttons are easy to tap. Serve smaller images to small screens rather than desktop-sized files. Test under realistic mobile conditions rather than assuming every visitor has a fast connection. A lighter page is more dependable for visitors, and it costs them less data.
10. A step-by-step speed optimisation routine
When I work on a slow WordPress website, I go in stages. It makes it clear which change helped and reduces the risk of breaking something while trying to fix everything at once.
I start by recording a baseline, testing the important pages on mobile and desktop and saving the reports. Next I check the hosting: server resources, PHP version, response time and whether server-level caching is available. Then I deal with the largest files, resizing and compressing images, reviewing fonts and removing oversized media such as video backgrounds. After that I set up page and browser caching, making sure plugin and server caching work together. Then I review the theme, plugins and outside scripts, removing anything unused. Before calling the work done, I test everything the business depends on: navigation, forms, search, login, cart and checkout. Finally, I run the same tests again, compare the results and keep watching the real-visitor data as it builds up.
Common mistakes to avoid
The most common mistake is chasing a perfect score. A high lab score is not the goal in itself; real visitor experience on the pages that matter to the business is. Another is installing several optimisation plugins at once, which can conflict with each other. Choose one solution that suits your host and configure it carefully.
Lazy-loading every image is another trap, because it delays the main banner and makes LCP worse. Ignoring mobile gives a false picture, since desktop results rarely reflect what customers experience on their phones. And making changes without a backup puts enquiries, orders and customer data at risk. Speed work should never cost the business a working website.
Conclusion: a faster website is a better experience for your customers
Speed optimisation is not a one-off job, and it is not just about a green score. A WordPress website changes as pages, images, plugins and features are added, and each change can affect performance. That is why speed checks belong in regular website maintenance.
Start with a proper test, fix the biggest problems in a sensible order and confirm the site still works as expected. Better hosting, optimised images, correct caching and fewer unnecessary scripts often make a meaningful difference on their own.
For a small business, a fast website helps visitors find information, explore services and take action without waiting. That is the real purpose of performance work: not to impress a testing tool, but to make the website work better for the people using it.
At Evaluate Media, regular speed and performance checks are part of how we build and manage our clients’ websites.
Frequently asked questions
1. Why is my WordPress website so slow?
The usual causes are weak hosting, oversized images, too many or poorly built plugins, a heavy theme, excessive scripts and missing caching. Run a speed test first so you fix the biggest problems instead of guessing.
2. How can I speed up my WordPress website without a developer?
Resize and compress your images, remove plugins you no longer use, set up a reputable caching plugin, keep WordPress updated and review your hosting plan. Back up the website before making changes, and test forms and checkout afterwards.
3. Which WordPress plugin is best for speed?
There is no single best plugin for every site. LiteSpeed Cache is a strong option on LiteSpeed hosting, while WP Super Cache and other established plugins suit other set-ups. Check what your host already provides, and avoid running two plugins that do the same job.
4. What is a good PageSpeed Insights score?
A score of 90 to 100 is rated good, but it is a lab measurement and varies between tests. Real-visitor Core Web Vitals matter more where that data is available. Never remove important features just to chase a perfect score.
5. Do Core Web Vitals affect Google rankings?
They are part of how Google assesses page experience, but they are only one factor. A good score does not guarantee top rankings, and useful, relevant content remains the most important thing.
6. Will a CDN make my WordPress website faster in Nigeria?
It can speed up the delivery of images, stylesheets and scripts by serving them from a nearby location. How much it helps depends on the CDN’s coverage, where your visitors are and how healthy your main server is. A CDN will not fix slow hosting or database problems.
Sources
Google Search Central, Understanding Core Web Vitals; Google Search Console Help, Core Web Vitals report; Google for Developers, About PageSpeed Insights; WordPress Developer Resources, Optimization; WordPress Developer Resources, Cache; Make WordPress Hosting, Performance handbook.
