Your prompt
Improve my Largest Contentful Paint: find the largest element on my homepage and top pages, compress and resize it, preload it, and make sure page caching is on.
What this prompt does
This prompt targets Largest Contentful Paint, the time it takes for the biggest visible element, usually a hero image or large heading, to appear. Your AI assistant is asked to find that element on your homepage and top pages, compress and resize it, preload it, and make sure page caching is on.
LCP is one of Google’s Core Web Vitals, and a slow one often comes from an oversized image or one that the browser discovers late. Preloading tells the browser to fetch it early.
The result varies by theme and host, so treat the outcome as an experiment to measure.
Remember that the largest element can differ between mobile and desktop. Ask the assistant to check both, because a fix on one screen size does not always carry over to the other.
Before you run it
- Measure first, with PageSpeed Insights or a similar tool, so you have a baseline.
- Take a backup, because the assistant replaces image files and may edit theme or plugin settings.
- Keep the original large image in case the compressed one looks poor.
- Know whether your theme or a performance plugin already handles preloading.
Do not lazy-load the main hero image. Lazy loading suits images below the fold, and on the largest visible element it tends to make LCP worse. Tell the assistant this explicitly.
What to check afterwards
- Re-run the same test and compare the LCP value for each page.
- The hero image looks sharp at its displayed size.
- The page source shows a preload for that image, and only for that image.
- A logged-out visit is served from the page cache.
- The layout has not shifted and nothing else slowed down.
Ways to adapt it
- Choose pages: Do this for my product pages and my top three blog posts.
- Choose the image format: Convert the hero image to WebP and keep the original.
- Report more: Show me the LCP element for every page you checked.
If it goes wrong
- LCP is still slow. The element may be text or a slow server, so ask the assistant to identify it and check server response time.
- Preloading the wrong image wastes bandwidth. Remove it and preload only the true LCP image.
- Cached pages look stale. Purge the cache after changes.
Core Web Vitals for WordPress explains all three metrics, and using PageSpeed Insights shows how to measure.