Find the cause of a slow website

A performance score tells you where to look. It does not tell you which plugin to buy. Start with the page and device your customers actually use.

1. Record the baseline

Run the same public URL more than once and note the device strategy, date and main measurements. Keep lab data separate from real-user data.

2. Find the main delay

Identify whether the page is waiting for the server, a large visual element or script execution. Match the fix to that part of the loading sequence.

3. Change one thing safely

Use a staging site or theme copy. Resize an oversized asset, remove a confirmed redundant feature or adjust a documented setting, then repeat the measurement.

4. Check the business task

A faster page is not a successful repair if the menu, form or checkout stops working. Test the relevant customer journey before publishing.

When to ask for help

Stop if the change affects a critical workflow, requires access you do not have or produces a result you cannot explain. Keep the original evidence and a restorable backup. A short, well-defined repair request is easier to review than a series of speculative changes.

Related repair: request a scope review. Choose your platform on the request form; availability and price are confirmed before payment.