WordPress feels slow. What should you measure first?
A performance score alone does not explain why a customer gives up. Start with the business journey: opening a service page, viewing a product or sending an enquiry. Slowness may affect the initial visit, an interaction or only periods when several people use the website.
Compare representative pages and conditions
Record three typical pages and the main action on each. Compare mobile with desktop and anonymous visits with administration. Repeat measurements under similar conditions and save the date. A logged-in session may use a different caching path from a visitor. Note whether slowness is constant or coincides with imports, backups or campaigns.
Find where time is being spent
WordPress performance guidance covers hosting, caching and content. For your website, separate the wait for a server response from the work the browser performs afterwards. If the initial response is slow, shrinking an image may miss the main cause. If the response arrives quickly but the page remains unresponsive, investigate scripts, styles and integrations.
- Compare the homepage with a simple internal page.
- Identify the main image and its transferred size.
- List chat, map, video and marketing integrations.
- Observe search, filter and form response times.
Change one variable at a time
Test on a copy and keep a baseline measurement. If you suspect an integration, temporarily disable it there and repeat the same journey. Avoid stacking several overlapping optimisation tools: identifying which one changed behaviour becomes difficult. For shops, check that caching and optimisation do not mix carts, sessions or personal content.
Prioritise actual usage
An oversized main image on a busy page may deserve attention before a footer detail. Record each fix, the observed difference and functional checks. Afterwards, compare real visitor data over time when available. The intended outcome is a website that is easier to use. A score guides investigation; it does not replace the customer's experience.
Frequently asked questions
Do I need different hosting?
First separate server limits from application problems. Moving slow queries or heavy integrations to another provider may simply move the problem.
How many plugins are too many?
The count alone does not measure impact. Consider the work each plugin performs, where it runs and how it interacts with the others.
Reference documentation
A note from ArqWeb
This guide organises checks and decisions for a common situation. Implementation depends on the website, access and systems involved. We can assess your situation if you need help applying these steps.
Let's look at your situation.
Tell us what you need and what you have already. We will reply with next steps and a proposal suited to the work.
Discuss my requirements