Core Web Vitals report that explains the fix, not just the score
Search Console says your pages have "poor" Core Web Vitals, but the report doesn't say what to change. This prompt has your todo.is agent test your key templates with Google PageSpeed Insights, read your Search Console export, find the element behind each slow LCP, layout shift or sluggish interaction, and write a fix list in plain language for you and your developer.
The prompt
- Make a Core Web Vitals report for [YOUR SITE]. Test these pages on mobile and desktop with Google PageSpeed Insights: [KEY PAGES]. For each, record field data (real users) where available and lab data, for LCP, INP and CLS, plus the LCP element, the elements that shift, and the heaviest scripts, images and fonts. If I attach [SEARCH CONSOLE CWV EXPORT], use it to see which URL groups fail. My site runs on [PLATFORM]. Explain each problem in one plain sentence, then give the fix with platform-specific steps, ranked by impact and effort. Deliver a Word report for my developer with screenshots and a one-page summary for me, then re-test the same pages every [RECHECK SCHEDULE] and message me if any metric gets worse.
What to change
- [YOUR SITE]: e.g. "wildfernflorist.com".
- [KEY PAGES]: One URL per template: homepage, a product or service page, a category page, a blog post.
- [SEARCH CONSOLE CWV EXPORT]: Optional: export from Search Console > Core Web Vitals. Write "none" if you don't have it.
- [PLATFORM]: e.g. "Shopify", "WordPress with Elementor", "Squarespace", "Next.js".
- [RECHECK SCHEDULE]: e.g. "Monday morning" or "1st of each month". Write "never" for a one-off report.
Example result
- Core Web Vitals report: wildfernflorist.com (Shopify)
- Tested on mobile with PageSpeed Insights. Field data is from real Chrome users over the last 28 days.
- Summary
- • LCP (loading): fails on homepage, collection and product pages. The main image appears too late.
- • INP (responsiveness): needs improvement on product pages. The delivery date picker blocks the page when tapped.
- • CLS (visual stability): fails on all pages. The announcement bar and review stars push content down.
- Fixes, most impact first
- • 1. Hero image (homepage): the LCP element is a 2.8 MB banner loaded by a slideshow app. Use one static image, export it at the size it displays, and let the theme serve WebP. Do not lazy-load the first image.
- • 2. Product images: the first product photo is lazy-loaded. Turn off lazy loading for the first image only.
- • 3. Announcement bar shift: the bar is injected by an app after the page loads. Use the theme's built-in announcement bar, which reserves its space.
- • 4. Review stars shift: reserve a fixed height for the star rating block.
- • 5. Delivery date picker (INP): a large calendar script runs on every tap. Ask the app developer for a lighter version, or load it only when the shopper opens the picker.
- • 6. Unused apps: 4 apps still load scripts though they are disabled. Remove them fully.
- • 7. Fonts: 3 font weights load. Keep 2 and preload the main one.
- Targets
- • LCP: 2.5 seconds or less
- • INP: 200 milliseconds or less
- • CLS: 0.1 or less
- (measured at the 75th percentile of visits)
- Next check
- Re-test every Monday. Field data takes up to 28 days to fully reflect fixes.
How to do it with todo.is
- Pick one URL for each page template and fill in the prompt with your platform.
- Attach your Search Console Core Web Vitals export if you have one, and paste the to-do into todo.is.
- Your agent runs PageSpeed tests in its browser, finds the causes and writes the report with fixes.
- Send the Word file to your developer. The weekly re-test messages you only if a metric gets worse.
Tips for a better result
- Test templates, not every page. Fixing the product template fixes every product page at once.
- Field data from real users is what Google uses. Lab scores help you debug but can differ.
- Apps and third-party scripts are the most common cause on Shopify and WordPress. Remove what you don't use.
- Core Web Vitals are one ranking signal among many. Fix them for your visitors first; better content still matters more.
Core Web Vitals report: FAQ
- What are Core Web Vitals? Three Google metrics for page experience: Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability).
- Why do my PageSpeed scores change every time? Lab tests vary with network and server load. Look at field data and trends over several tests rather than one score.
- How long until Search Console shows my fixes? Search Console uses a rolling 28-day window of real-user data, so improvements show up gradually over about four weeks.
- Do Core Web Vitals affect rankings? They are part of Google's page experience signals. They rarely beat relevance, but they can matter between similar pages and they affect conversions.
JavaScript is required to use the todo.is app.