A slow homepage, a slow product search and a slow checkout may have different causes. Before buying new hosting or another optimisation plugin, identify the page, action and conditions that make the website feel slow. That gives your developer something concrete to investigate.
Describe where the delay occurs
Test a few representative pages and devices. Record whether the problem affects everyone, logged-in users only or a particular location or connection.
Check the visitor experience alongside measurement tools. A page may load its initial text quickly while a form takes a long time to submit. That delay still matters.
Avoid treating one test score as a complete diagnosis. Repeat comparable tests and note the conditions. Changing several things between measurements makes the result difficult to interpret.
Inspect images and other media
Large images can increase what visitors need to download. Confirm that the image dimensions and file size suit how it is displayed.
Use suitable formats and responsive image handling where supported. Preserve enough quality for product details and do not remove useful visual information simply to reduce a file size.
A large background video may need reconsideration if it delays the information people came to find. Decide whether it serves a real purpose on that page.
Follow one slow action
Suppose catalog pages open quickly, but searching by product code takes noticeably longer. Record the code used, whether the visitor was logged in, the device and whether the delay repeats. Compare another search and a normal category page. This does not identify the cause by itself, but it narrows the investigation to a useful path. Making the homepage banner smaller may still be worthwhile, yet it will not necessarily address a slow search query. Change one suspected factor and compare the same task again.
Check the amount of work the page performs
Themes, builders and plugins can add scripts or database work. The number of installed plugins alone is not a reliable measure of performance: what they do matters.
Identify slow requests and functions before disabling components. A live store should not lose checkout or product rules during an experiment.
Use a suitable copy for investigation when changes could disrupt important work. Preserve a backup and a record of what was changed.
Review hosting and server response
Ask whether the server has adequate resources for the actual workload. Scheduled jobs, uploads and traffic spikes can affect the experience.
Before moving hosting, understand whether the limitation is resources, configuration or application behaviour. A more expensive server may not fix inefficient code or a slow external request.
Review logs with a developer where necessary. They can help distinguish an application error from a network or provider issue.
Use caching with care
Caching can reduce repeated work, but different pages need different treatment. Personalised account information and transactional behaviour must remain correct.
The WordPress optimisation guidance describes performance considerations including caching and server configuration. The suitable setup depends on the website.
Check the result after any caching change. A faster page that displays stale prices or another user’s information is not an improvement.
Investigate external scripts
Chat widgets, analytics, embedded videos and other services can add loading work. Keep the ones that serve a clear purpose and check how they are loaded.
For a hypothetical business site, removing an unused external widget may be more sensible than replacing the theme. The investigation should lead to a specific change with a measurable result.
Auspian’s WordPress services can include performance investigation and changes within an agreed scope.
First checks to record
- Affected pages and actions.
- Device, connection and login state.
- Media dimensions and file sizes.
- Slow network requests or server responses.
- Recent software or content changes.
- External scripts and background jobs.
- Results before and after a controlled change.
Frequently asked questions
Will a caching plugin fix every slow site?
No. It may help some workloads, but the underlying cause must be investigated.
Should we change hosting immediately?
Only after checking whether the hosting is actually the limitation and what improvement the proposed move provides.
Does a high test score guarantee enquiries?
No. Performance is one part of usability. Content, navigation, relevance and the enquiry process also matter.
Ask Auspian to review the slow path. Include an example page or action and the conditions in which the delay appears.
