Measured as a first visit, three times over
Every number in the audit comes from a true first visit with nothing cached. Each layout is run three times, on mobile and on desktop. A warm cache makes a page look far quicker than a new visitor finds it, so warm runs are left out.
What the agent fixes, with a way back
The agent converts images, minifies files, and sets up caching, compression, headers and edge rules. Each changed file gets its own rollback note. Files are renamed rather than deleted, so any change can be undone within minutes.
What a person fixes
Rewriting templates, building critical CSS and deciding what happens to third-party scripts all need judgment, so an engineer does them. They are quoted once the audit has shown which of them are worth doing, as a fixed price in the written proposal.
Scope is counted in layouts
Pages that share one design and the same assets count as a single layout. A shop with 2,000 products usually comes to four layouts. The agent’s crawl does the counting, and the proposal states the figure.
| Kind of site | How the scope is set |
|---|---|
| Pages built from shared templates | By the number of layouts the crawl finds |
| Hand-coded sites where each page is unique | The whole site as one job, at a fixed price in the written proposal |
Monitoring after the fixes
- A fresh audit every week.
- An alert when a new script or plugin makes a page heavier.
- Safe fixes applied again where they have been undone.
- A written report each month, checked by a person.
Why no speed score is guaranteed
We do not promise a particular speed score, and a promise like that deserves caution from anyone who makes it. You get real measurements from before and after, and a clear statement at the start of what is within reach.
Which platforms the agent can change is listed in platform coverage; the service is on the Performance Agent page.