Core Web Vitals
Monitor lab-based Core Web Vitals checks for important Screpy project URLs.
Core Web Vitals monitors lab-based checks for important project URLs. Use it to identify pages that need investigation, then confirm the cause with the page, template, and delivery setup—not by treating a single score as the whole user experience or as field data from every visitor.
Add and manage monitored pages
The initial project setup includes the homepage. Select Add Page to monitor another public URL, enter its full address, then wait for the next check to populate its result. The header shows the number of URLs used against the allowance on the current plan.
The report shows a verdict per page and values for FCP, LCP, CLS, TTFB, and TBT. The summary also includes Speed Index. Sort or review the table to find an important URL with a failed result before opening the page and its delivery path.
Deleting a monitored URL removes its history
Removing a URL from Core Web Vitals also removes its existing analysis history. Export or record the data you need before confirming the deletion.
Read the metric with its URL and date
Start with the affected page and the time of the measurement. A homepage result does not automatically describe every template on the site, and a temporary deployment, third-party script, or cache state can influence a single run. Look for a repeated pattern before committing to a broad performance change.
Use the available data to separate likely causes. Slow loading often points to render-blocking work, large assets, server response, or unnecessary client code. Poor responsiveness can be caused by long browser tasks or heavy interaction code. Visual instability is often related to images, embeds, fonts, or content that changes layout after the initial render.
Turn a metric into a testable fix
Choose one hypothesis, make the smallest relevant change, and measure again. For example, optimize the image that dominates a page, reserve space for an embed, or delay a non-essential script. Keep the before and after result with the page URL and deploy date so you can tell whether the change helped.
Common questions
Why is a metric missing?
Screpy needs a checkable public page result. Confirm that the URL is public, reachable, and included in the project’s available Core Web Vitals allowance. A check that has not run yet also has no result to display.
Should I optimize only the lowest score?
Prioritize pages that matter to visitors and business goals. A repeatable template issue on important landing pages is usually a better first project than an isolated low-priority page.
See the Screpy features overview for how performance, availability, and crawl monitoring fit together.
Read how Screpy measures performance data before comparing results. Google's Core Web Vitals documentation explains the industry definitions of loading, responsiveness, and visual stability.