A page speed report that explains why each page is slow
A speed score on its own doesn't tell you what to change. Paste this to-do and your todo.is agent loads each page on mobile and desktop, looks at what the browser actually downloads, and writes a plain report naming the heaviest images, scripts and fonts, with the likely gain from each fix.
The prompt
- Make a page speed report for [PAGE LINKS]. Load each page on a mobile and a desktop screen size, 3 times each, and report the median. Measure: time until the main content shows, total page weight, number of requests, largest images and their sizes, render-blocking scripts and styles, third-party scripts (chat widgets, trackers, embeds), web fonts, and layout shifts while loading. Where you can, include the Core Web Vitals (LCP, CLS, INP) from Google's public PageSpeed tools. For each page list the top 5 fixes with the estimated saving in KB or seconds. My site runs on [PLATFORM]. Deliver a PDF report and send a short summary to [WHERE TO SEND IT].
What to change
- [PAGE LINKS]: Up to 10 pages, e.g. homepage, a product page and a blog post.
- [PLATFORM]: e.g. "Shopify", "WordPress with Elementor" or "Webflow". Fixes are tailored to it.
- [WHERE TO SEND IT]: e.g. "my email", "Slack" or "here".
Example result
- Page speed report · Halden Outdoor shop (example)
- Measured Oct 8 · median of 3 loads per device
- Overview
- • Homepage (mobile): main content after 4.9 s · 6.2 MB · 142 requests
- • Homepage (desktop): 2.3 s · 6.0 MB · 138 requests
- • Product page (mobile): 3.6 s · 3.1 MB · 97 requests
- • Blog post (mobile): 2.1 s · 1.4 MB · 54 requests
- The homepage on mobile is the problem. LCP is in the "poor" range (over 4 s).
- Homepage: top 5 fixes
- • 1. Hero image is a 3.8 MB PNG at 4000 px wide. Serve WebP at 1600 px for desktop and 800 px for mobile. Saving: about 3.4 MB, roughly 2 s on mobile.
- • 2. Instagram feed embed loads 31 requests and 900 KB before you scroll. Load it only when it comes into view. Saving: about 0.8 s.
- • 3. Two chat widgets (an old one was never removed). Remove one. Saving: about 400 KB.
- • 4. Four font weights of the same font. Keep regular and bold, use font-display: swap. Saving: about 180 KB and less blank text.
- • 5. Layout shift (CLS 0.21) when the announcement bar loads. Reserve its height in CSS.
- Product page: top fixes
- • Gallery loads all 12 photos at full size. Lazy-load images after the first.
- • A reviews app adds 400 KB of script. Check its settings for a lighter mode.
- On Shopify
- • Use the image_url filter with a width to get resized images
- • Check Apps: removed apps can leave scripts in the theme
- What good looks like
- LCP under 2.5 s, CLS under 0.1 and INP under 200 ms on mobile.
- Re-run this report after changes to see the difference.
How to do it with todo.is
- Copy the prompt and paste in the pages that matter most to you.
- Paste it into todo.is on the Today screen, or send it to your agent on Telegram.
- Your agent loads each page several times, measures it and builds the PDF.
- Fix the top item on the slowest page first, then say "run the same report again" to compare.
Tips for a better result
- Measure mobile first. Most visitors are on phones and mobile is where slow pages hurt.
- Images are the most common cause. Resize to the size shown on screen and use WebP or AVIF.
- Every chat widget, tracker and embed costs time. Remove the ones nobody uses.
- Make it monthly: "run this report on the 1st of every month and tell me if any page got slower".
page speed report: FAQ
- What is a good page load time? Aim for the main content to show in under 2.5 seconds on mobile. That is Google's "good" threshold for Largest Contentful Paint.
- What are Core Web Vitals? Three measures Google uses for page experience: LCP (loading), CLS (visual stability) and INP (responsiveness to clicks and taps).
- Why is my site slow on mobile but fine on desktop? Phones have slower processors and often slower networks, so large images and heavy scripts hurt more. Mobile-sized images usually help most.
- Can it make the changes on my site? No. It finds the causes and writes the fixes. For images, you can attach them and your agent will resize and compress them for you.
JavaScript is required to use the todo.is app.