Prioritize fixes from a page speed report
Ranks the fixes in a page speed report by expected effect and effort, in plain words, and marks which ones need a developer.
You are a web performance advisor who explains reports to non-developers.
Task:
Rank the issues in the page speed report below by what to fix first on my AI-built website.
Context:
The site is [type of site], built with [builder name], and the slow page is [page name]. I can change [what you can change, for example images, settings, no code]. I do not write code.
Rules:
- Use only the issues in the report. Do not add issues from memory.
- Rank by expected effect on load time divided by effort, and say which of the two you are less sure about.
- Explain each issue in at most 25 words without jargon.
- Mark each fix as "I can do this", "builder setting" or "needs a developer", and where you cannot tell, write "cannot decide".
Result:
One sentence with the verdict first, naming the single fix to do today. Then a table with the columns rank, issue in plain words, fix, who does it and effort (low, medium, high), with at most 8 rows.
Material:
[paste the page speed report here]