How to use the Speed Optimizer
A step-by-step guide for customers who already have the Speed Optimizer in one of their seats.

This guide shows you how to run the Speed Optimizer, what to type, and how to read what it sends back. To see what it checks and which plans include it, read the Speed Optimizer page.
Before you start
- The address of the page you want speed-tested. The one mobile PageSpeed test runs on the address you type, so pick your homepage or your busiest page.
- Access to your site images and plugins, or a developer, since speed fixes are made in the site itself.
- The Speed Optimizer picked in one of your seats under My AI agents, then Save selection.
Step by step
- Sign in and open My AI agents in the dashboard menu. Click the Speed Optimizer to put it in one of your seats, then click Save selection.
- Open the Dashboard page. In the chat box, type what you need in plain words and include your website address.
- Wait while the check runs. The answer shows in the chat, and the full report is saved under Audit reports & fixes.
- Make the changes you agree with, then send the same request again to see what is still open.
What to type in the chat
Copy one of these requests and change the details to match your business.
“Run a speed check on yourbusiness.com”
Use this as your main check. The Speed & Performance Audit reads up to 5 pages and runs one mobile PageSpeed test on the address.
“Run a speed test on yourbusiness.com/services/”
Use this to test an inner page, since the test runs on the address you type.
“Why is yourbusiness.com slow on phones? Check it”
Plain wording like this starts the same speed audit.
“Run a technical SEO audit on yourbusiness.com”
Use this when you want speed plus crawl and schema checks. It reads up to 10 pages.
How to read the results
- The chat result shows four PageSpeed scores (Performance, Accessibility, Best Practices, SEO), then the overall score out of 100.
- Each issue names the exact file and number from the test, such as a file that blocks the page from showing or an image with its possible savings.
- For LCP, under 2,500 ms is good, 2,500 to 4,000 ms needs work, and over 4,000 ms is poor. Lower is always better.
What to do next
- Fix the highest issue first, then run the same check on the same address.
- Look at whether the named file or image is gone, since the score itself can move a bit from one test to the next.
- Test your other key pages one at a time by typing each page address.
Tips
- Type the address the way it finally loads, with https and with or without www. A redirect adds time to the test.
- Ideas like a heavy script on every page come from the code of the other pages it reads, not only the tested page.
- On a Next.js site, the agent will not suggest preloading your main stylesheet. The fix there is smaller CSS.
Questions about using it
What if it finds nothing?
When the page passes LCP, FCP, TBT, and CLS, the agent leaves out small savings tips, so the list can be short or empty. That is a good result.
Can I test the desktop version?
No. The test runs on a mobile setting only. To see desktop numbers, run PageSpeed Insights yourself and pick Desktop.
Can I test a page other than my homepage?
Yes. Type that page's full address in your request, and the PageSpeed test runs on that page.
Guides for agents that pair well
Agents work better together. Here are specialists that pair well with the Speed Optimizer:
- Technical SSR Sentinel - Checks your pages for technical SEO problems that stop search engines from finding, crawling, or indexing them.
- UI/UX Enhancer - Checks your pages for things that make it harder for visitors to take the next step, and suggests specific changes.
- Platform Readiness Lead - Checks the technical signals that affect whether search engines and AI tools (ChatGPT, Perplexity, Claude, Gemini) can reach your pages: robots.
Need a different agent? Browse all 25 agent guides or see the full agent catalog.