Identify what you notice when your website loads
Each speed problem has a different cause, so knowing which one you have keeps you from wasting time changing things that don't help. Open your website on your phone and write down which of these situations happens to you. After you measure in step 2, go to the matching step:
- The screen takes a long time to show content: the cause may be your hosting (the company that stores your website and delivers it to whoever visits it) or your cache (a ready-made copy of your website that is delivered to each visitor without building it from scratch). Go to steps 3 and 4.
- The text appears, but the main photo takes a while: it may be its file size or its dimensions. Go to step 5.
- The content jumps around while it loads: space may not be reserved for images, ads, or fonts. Go to steps 5 and 6.
- The website shows up, but buttons and menus respond late: it may be the code of a chat, a widget (an extra block, like a calendar or a map), or another external tool. Go to step 6.
- The website works differently when you log in or buy something: the cache may be storing content it shouldn't. Go to step 4.
If more than one happens to you, deal first with the one that most affects the person who wants to contact you.
Measure the pages that help your customer move forward
Without a starting measurement, you won't know whether a change helped, did nothing, or made something worse. That's why you should first measure the pages your customer goes through: a service page, your contact page, and your booking or purchase page, if you have one.
To measure them, go to PageSpeed Insights (pagespeed.web.dev), a free Google tool. Paste the page address and write down the date, the address, and whether the test was on mobile or desktop; the tool shows them separately.
PageSpeed Insights gives you two kinds of data. The first is a lab test, a simulation the tool runs at that moment. The second is real-user data, which Google calculates from visits over the last 28 days and which only appears if your page has enough of them. If it doesn't appear, that doesn't mean your page is fast or slow; it means that information isn't available yet. In that case, run several lab tests under the same conditions and write down the difference between them.
Keep in mind that the lab test is useful for investigating, but it doesn't show what each visitor experiences, nor does it prove that you'll get more contacts.
Then, check these four things:
- Main load: when the large content the visitor needs to see appears, like the headline or the main photo.
- Response: whether the menu and buttons respond when you tap them.
- Stability: whether images or fonts move the content around while it loads.
- Contact: whether you can fill out the form and the request reaches you.
Check your hosting before you think about moving your website
If your server (the computer at your hosting company that delivers your website) is slow to respond, no other improvement, like lighter images, will remove all the waiting. That's why, before paying for a more expensive plan or moving to another hosting company, write to yours and ask:
- What resources your plan includes.
- Which PHP version (the language WordPress runs on) is compatible with your site.
- What limits your plan has.
- What caching it already offers.
They may mention technologies with names like NVMe or LiteSpeed. They can help, but the name alone doesn't prove your website needs them, so ask them to explain which of the problems you measured in step 2 they would solve.
If you finally decide to move your website to another company, do it with a backup (a complete copy of your website that you can restore) and with a plan for your form, for your email (if it uses your website's address, like yourname@yourbusiness.com), and for rolling back if something fails. We recommend not moving just to get a higher score.
Use a cache that works with your WordPress features
A cache that doesn't fit your site can cause serious problems. If your website has a shopping cart, forms, or customer accounts, a poorly configured cache can show one person another person's data, or stop the cart or the form from working. That's why caching only helps when it respects those features.
When it works well, the cache stores a ready-made copy of your public pages and delivers it to each visitor; according to the official WordPress guide, this reduces the work your server has to do. To take advantage of it, first check whether your hosting already offers caching and which plugin it recommends for your setup. If you need one, search for the word "cache" in the WordPress plugin directory and choose one that is compatible with your hosting.
After you turn it on, do this:
- Write down who controls the cache (your hosting or the plugin) and how to clear it.
- If your site has a cart, checkout, customer accounts, or personalized content, exclude them from the cache so no one sees another person's data.
- When you change a page, open it without logging in and check that the new version shows.
- Test the forms and the confirmations as a visitor, not only with your administrator session.
Prepare your images without delaying the main image
The main image is usually the first large thing the visitor expects to see when they open your website, and Google uses it to measure how long it takes for the main content to appear. If that image takes a while, the person feels the whole page is slow; that's why it's worth preparing it well and not delaying it.
A photo uploaded at a huge size forces the visitor's phone to download more information than it needs. To avoid that, do this before uploading your images:
- Upload each photo at a size that fits the space it takes up in your design.
- Use lighter formats, like WebP or AVIF, as long as the image keeps good quality. If it's a product or a before-and-after, check that it doesn't end up blurry, because your customer needs it to decide.
- Reserve the width and height of each image so the content doesn't jump around while it loads.
- Also check videos, sliders (images that change on their own), and large backgrounds.
There's also lazy loading, which makes an image download only when the visitor scrolls down to it. Use it on images lower down the page, but not on the main image, because it would delay it.
Reduce CSS and JavaScript without breaking your contact form
CSS and JavaScript are the files that give your website its design and its features, like menus, buttons, and the contact form. The more code each page loads, the more work the visitor's phone has to do, so it's best for each page to load only what that person needs at that moment.
First, check which styles, forms, chats, and analytics tags load on each page. Analytics tags are snippets of code that measure how many people visit your website and what they do on it, like the ones from Google Analytics. Removing spaces and unnecessary parts from a file makes it smaller. It doesn't stop a script (a snippet of code that performs a function on your website, like a chat) from running on a page that doesn't need it.
Be careful: delaying or removing code can break the features that depend on it, and if the form breaks, you lose that contact even if the page loads faster. That's why you should make these changes first on a staging copy (a copy of your website where you can test without affecting the one your customers see) and then check the menu and the form. If the menu doesn't open or the form doesn't send, that change didn't work, even if the speed looks better. Also, don't remove the analytics tags or the cookie notice (the message that asks the visitor for permission to store data about their browsing) just to improve a test.
Fonts are also part of what your website loads. Many themes load them from an external service, like Google Fonts, every time someone opens the page. Hosting them on your own website can change the load time, but it's not an automatic fix: it depends on how many fonts and styles you use and how much they weigh. That's why you should measure before and after, as in step 2.
Review your theme and plugins by what they do
According to the official WordPress guide, the number of plugins and their performance have a big influence on your site's speed, and deactivating and deleting the ones you don't need is an important way to improve it. The same goes for the theme, which is the base design of your website. That's why it's worth knowing what each one does.
To find out, make a list of what your site uses and what each thing is for. Then, look for three cases:
- Plugins you no longer use.
- Two plugins that do the same thing.
- Plugins that load their files on pages where they aren't needed.
To see which one weighs the most, deactivate the plugins one at a time on a staging copy and measure the page after each one, as in step 2. Before uninstalling any of them, check which content, orders, fields, or connections to other services depend on it.
A lightweight theme can help, but changing your theme or page builder (the editor you use to build your pages) can also change the design and features. That's why you should test the alternatives on the staging copy before changing anything on the live website.
Clean up the database with a backup
Before cleaning up the database, make a backup (the complete copy from step 3). It lets you roll back if, while deleting something, you lose an order, a user, or a form submission that you actually needed.
The database is where WordPress stores your text, orders, users, and plugin data. Over time it fills up with revisions (earlier versions of your pages) and drafts, and cleaning it can help, as long as that's what's slowing your website down. If it isn't, an aggressive cleanup only adds risk without removing the wait.
Also, not all old data is unnecessary. That's why you should review what you're going to delete and ask whoever manages your website before deleting orders, users, form submissions, bookings, or any information you need to keep. We recommend not doing a mass cleanup on the live website if you don't know what each part of the database stores or how to recover it.
Consider a CDN if your problem is how files reach the visitor
A CDN helps when your website's files take a long time to reach the visitor, for example, if your server is far from your customers or struggles to deliver so many files at once. It's a network of servers in different locations that stores copies of certain files from your website and delivers them from the server closest to the visitor. According to the official WordPress guide, it also takes a lot of work off your own server and performs better when used together with a caching plugin.
Before adding one, check where your visitors are and which files weigh the most. Cloudflare is a well-known option, but its rules have to fit your site. Check that pages that change for each person, like the cart or the account, aren't delivered as if they were public files, and that your updates reach the visitor.
When you turn it on, you may have to change your DNS: the settings for your domain (your website's address) that tell the internet where your website and your email are. Write down those changes and then check that your site and your email still work.
Keep in mind that a CDN doesn't fix a huge image or a script that blocks the buttons.
Check the improvement and the whole journey
A better speed score doesn't help if your customer can't contact you. That's why, besides measuring again, you need to confirm that the whole journey still works.
Repeat the tests from step 2 under the same conditions and compare them with your starting measurement. Then, open your website, use the menu, and send the form. If something stopped working, write down what it was and how you fixed it. Keep in mind that real-user data is calculated from visits over the last few weeks, so it takes time to reflect your changes.
Next, watch whether visitors reach your service page and ask for help. For that, you can use Google Search Console (search.google.com/search-console), a free Google tool that shows how many times your page appeared in search results (impressions) and how many people clicked on it. If you don't have it, ask whoever manages your website to connect it. Impressions and clicks show how visible you are; requests from real customers show how your business is doing. None of these measures, on its own, proves that a change was the reason you rank higher on Google or sell more.
To decide what's next, keep this information on hand:
- Your before-and-after measurement, with its conditions.
- The lab results, real-user results, impressions and clicks, and contacts, each one separately.
- A log of the changes you made and how to undo them.
With that, decide your next task based on what you measured, not on a list of plugins someone recommends to you.