A slow site rarely has one neat cause. Start with the pages customers actually use, such as a service page, enquiry form or booking journey, and test those on a phone as well as a desktop.
Begin with what the visitor experiences
Start by checking whether someone can read the page, tap a link and send an enquiry without waiting or losing their place. Google calls its measures of loading speed, response time and page movement Core Web Vitals. They can help investigate what you notice.
Five checks worth making
1. Check image dimensions and file sizes
Large image files can make a page slow to load. Ask whoever looks after the site to resize them for the screen and delay loading images further down the page until they are needed.
2. Review the plugin list
Plugins add features to WordPress, such as forms or booking tools. Ask your developer to check for unused plugins or ones doing the same job. Take a full backup and test changes on a separate copy of the site before removing anything.
3. Ask how pages are stored and delivered
Caching stores a ready-made version of a page so the server does less work for each visit. Ask your hosting provider whether it is set up appropriately. Sites with visitors in several countries may also benefit from a network that delivers files from a server closer to each visitor.
4. Check background tasks and stored data
WordPress stores page revisions and temporary data, and runs tasks such as backups in the background. Ask your developer to check whether these are slowing the site down. Changes to stored data need a backup and careful testing.
5. Compare the hosting with the site
A simple business website and a busy online shop have different hosting needs. Ask whether the server has enough capacity, how quickly it responds and what support is available before deciding to move.
A useful 15-minute check
Choose the service page that matters most to your business. Open it on your phone using mobile data, then try to find a price or useful example and reach the enquiry form. Write down where you wait, where the page jumps and anything that is difficult to tap. Repeat the same journey on a desktop.
For example, if the heading appears quickly but the main photograph takes several seconds, inspect that image before changing the whole website. If every page pauses before anything appears, ask your provider to check the server response. These are starting points for investigation, not a diagnosis from one visit.
Keep a record before changing anything
Save the page URL, device, date and test result. Make one change on a test copy, then repeat the same journey under similar conditions. Check the enquiry form and navigation as well as the speed score. A faster page is only useful if the important tasks still work.
WordPress explains how to back up a site before making changes. If you need someone to manage the work, see our WordPress care plans.
Need help with your website?
Tell us what needs attention and what you need the website to do. Andy will suggest a practical next step.