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
Google's Core Web Vitals can help describe loading, responsiveness and visual stability, but the practical test is simpler: can someone read the page, move through it and submit an enquiry without waiting or losing their place?
Five checks worth making
1. Check image dimensions and file sizes
Large source images are a common source of unnecessary page weight. Resize them for the space they occupy, use an appropriate file format and lazy-load images that begin below the visible page.
2. Review the plugin list
WordPress sites often keep plugins that are no longer used or duplicate another feature. Remove only after checking what each plugin does, taking a backup and testing the change away from the live site.
3. Check caching and delivery
Page caching can reduce repeated server work. A Content Delivery Network may also help when visitors are spread across different regions, although it does not fix a slow theme or poor hosting configuration.
4. Inspect scheduled and database work
Old revisions, expired transient data and busy scheduled tasks can add overhead. Database work should be backed up and reviewed carefully rather than run as a blind cleanup.
5. Compare the hosting with the site
A small brochure site and a busy e-commerce site have different needs. Look at server response time, PHP resources, caching and support before deciding that a move is necessary.
Our WordPress care plans can cover routine maintenance and performance review. Tell us about your site if you would like help deciding where to start.
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.
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.