Your prompt
Find the five slowest pages on my site, explain why each is slow, and fix the biggest issue on each.
What this prompt does
This prompt asks your AI assistant to find the five slowest pages on your site, explain what slows down each one, and fix the biggest single issue on each page. It is narrower than a whole-site speed project, which makes it easier to check.
Pages are often slow for different reasons: an oversized image on one, a heavy embed or script on another. Looking page by page shows where the problem actually is.
Treat the five pages as a sample rather than the whole story. If the same kind of issue turns up on all of them, you have learned something about the site, and you can fix that cause everywhere afterwards.
Before you run it
- Make a backup, or use a staging site.
- Check what data your assistant can use to decide what is slow. If it has no measurement tool, ask it to say how it chose the pages.
- Tell it about pages you do not want touched.
- Be ready for possible fixes such as resizing images, removing a plugin’s script from one page, or turning off an embed.
- Decide whether you want to approve each fix first. A change to a plugin setting can affect the whole site, not just one page.
What to check afterwards
- Ask for a table: page, cause, fix made, and measurement before and after.
- Open each of the five pages and confirm it still looks right.
- Click through forms, sliders and videos on those pages.
- Test on mobile.
- Check that a fix on one page did not change other pages, especially if a plugin setting was changed globally.
Ways to adapt it
- Change the number: “Find the ten slowest pages but only fix the top three.”
- Ask for advice first: “List the cause for each page and wait for my approval before changing anything.”
- Focus on one kind of page: “Only look at my blog posts.”
- Set a limit on how invasive fixes can be: “Only change content on the page itself. Do not change plugin settings.”
If it goes wrong
- The same cause shows up on every page. That points to a sitewide problem, such as hosting or a plugin, so ask the assistant to look there next.
- A fix removed something you wanted. Ask for it to be restored and for a lighter alternative.
- Results look no better. Clear caches and test again, as cached and uncached results differ.
Read our Core Web Vitals guide to understand the causes it finds, and the slow admin guide if the dashboard is slow too.