First Contentful Paint (FCP)
See when the first text, image, or other content appears during the lab check. A slow FCP narrows the investigation to the page's early loading path.
Website PageSpeed Monitoring
Run recurring lab checks for selected public URLs. Review loading milestones, server response, main-thread blocking, layout stability, a clear verdict, and result freshness without treating synthetic data as real-user experience.
TL;DR
Too Long; Didn't Read
Show summary Hide summary
TL;DR
Too Long; Didn't Read
What Is PageSpeed Monitoring?
Screpy PageSpeed Monitoring runs recurring synthetic lab checks for selected public URLs. It reports loading, server-response, main-thread, and layout-stability measurements with a current verdict and last-check time. The results help teams choose what to investigate next without presenting lab data as real-user field data or promising a ranking outcome.
Choose monitored pages
- Screpy PageSpeed Monitoring checks selected public URLs rather than every crawlable page automatically.
- Screpy includes the project homepage in the initial monitored set and lets members add other public URLs within the current plan allowance.
- Screpy makes an active URL eligible for another scheduled check after its latest result is at least one day old.
Read the loading timeline
- Screpy reports First Contentful Paint, Largest Contentful Paint, and Speed Index for the selected URL.
- Screpy keeps every PageSpeed result attached to the exact URL and last-check time used for the decision.
- Screpy shows a Good, Needs Improvement, or Poor lab verdict for rapid URL triage.
Narrow the investigation
- Screpy reports Time to First Byte to support server-response and delivery investigation.
- Screpy reports Total Blocking Time as a lab responsiveness diagnostic rather than the real-user Interaction to Next Paint metric.
- Screpy reports Cumulative Layout Shift to keep visual-stability context beside the loading measurements.
Interpret the result safely
- Screpy PageSpeed Monitoring presents synthetic measurements and does not label them as real-user field data.
- Screpy displays the current result and freshness without promising alerts or a multi-point historical trend chart.
- Screpy metrics narrow the next investigation but do not prove a root cause, automatic fix, ranking gain, or conversion result.
Read the PageSpeed timeline metric by metric.
Use six loading, responsiveness, and stability measurements together with a lab verdict, exact URL, and check time. Each signal answers a different performance question.
Largest Contentful Paint (LCP)
Measure when the largest visible content element finishes rendering in the test. Use the result to review the main image, text block, delivery path, or template.
Speed Index
Summarize how quickly visible content appears throughout the lab run instead of judging the experience from a single rendering milestone.
Time to First Byte (TTFB)
Review the initial server-response delay observed by the check. A weak result gives you a reason to inspect redirects, caching, hosting, or backend work.
Total Blocking Time (TBT)
Measure lab-observed main-thread blocking. TBT helps diagnose responsiveness problems, but it is not the real-user Interaction to Next Paint metric.
Cumulative Layout Shift (CLS)
Check unexpected visual movement during the test. Use a weak result to inspect image dimensions, embeds, fonts, and content that appears late.
Lab performance verdict
Use the Good, Needs Improvement, or Poor verdict to triage monitored URLs. The verdict summarizes a synthetic check, not Google's field-data assessment.
URL and check freshness
Keep the result tied to its exact public URL and last-check time so you do not make a current decision from an old or unrelated measurement.
Run recurring lab checks on selected URLs.
Choose public URLs that represent important journeys or templates. Screpy records the current lab measurements, verdict, and last-check time for each active monitored page.
- Monitor the homepage and selected public URLs
- Use the current plan allowance for URL coverage
- Confirm result freshness before acting
Read more than one PageSpeed score.
Use FCP, LCP, Speed Index, TTFB, TBT, and CLS together to identify which part of the controlled loading sequence needs a closer technical investigation.
- Review rendering and visual-progress milestones
- Inspect server-response and main-thread signals
- Keep layout stability in the same result
Measure the same page after a focused change.
Record the current result, use the weakest metric to form one hypothesis, change one likely cause, and check the same URL again instead of mixing multiple pages and fixes.
- Keep the URL and measurement scope consistent
- Change one meaningful cause at a time
- Use a later check to validate the direction
Turn one slow result into a controlled performance check.
Reduce guesswork by keeping the URL, measurement scope, and next change specific. PageSpeed Monitoring supplies the lab evidence; the investigation still belongs to your team.
- 01
Choose a representative public URL
Start with a page tied to revenue, campaigns, organic discovery, or a shared template instead of adding every available URL without a decision purpose.
- 02
Read the current result and its date
Confirm the exact URL, last-check time, verdict, and weakest metric before treating the measurement as evidence for today's page.
- 03
Form one focused hypothesis
Use FCP, LCP, TTFB, TBT, Speed Index, or CLS to decide whether to inspect early rendering, main content, server response, scripts, visual progress, or layout movement.
- 04
Change one cause and measure again
Keep the same URL and test scope, record the original result, make one meaningful change, and use a later check to see whether the evidence moved in the expected direction.
Monitor pages that represent a real business decision.
A smaller, intentional URL set is easier to interpret than a list with no priority. Cover important journeys and templates before low-value edge pages.
Revenue and signup pages
Monitor checkout entry points, pricing pages, lead forms, and signup routes where a slow experience can interrupt a high-value visit.
Campaign landing pages
Keep paid, email, launch, and seasonal landing pages in the monitored set while they are actively receiving traffic.
Organic entry pages
Choose representative articles, category pages, and product pages that bring search visitors into the site.
Shared templates
Monitor one representative URL from each important template so a layout or script change can be investigated with a focused lab result.
Know what the monitoring result does not prove.
Use Screpy as a recurring lab measurement workflow. Keep field data, root-cause diagnosis, historical reporting, alerts, and business outcomes separate unless another source verifies them.
Lab data is not field data
Screpy reports synthetic measurements from a controlled check. Do not present them as the experience recorded from your real visitors.
Freshness is not a trend chart
Use the current result and last-check time to judge relevance. The PageSpeed view does not promise historical charts or performance alerts.
A metric is not the root cause
A weak FCP, LCP, TTFB, TBT, Speed Index, or CLS result identifies where to investigate; it does not prove the implementation change required.
PageSpeed is not a ranking guarantee
Faster pages can support visitors and page experience, but a lab verdict alone cannot guarantee rankings, traffic, engagement, or conversions.
Use the performance workflow that matches the question.
Monitor selected URLs for current lab results, learn how those signals relate to Core Web Vitals, or audit the wider website when a single metric cannot explain a repeated problem.
Run recurring lab checks for selected public URLs and review their current metrics, verdict, and check freshness.
Separate lab diagnostics from field data and understand how LCP, CLS, TBT, and real-user INP should be interpreted.
Crawl the wider site to investigate repeated technical, asset, rendering, and template patterns around an affected page.
Screpy documentation
Learn how to monitor page performance
Use the performance monitoring guide to select useful URLs, read current lab metrics with their check time, separate synthetic results from field data, and plan a focused retest.
Related SEO guides
Learn the concepts behind this workflow and apply them with practical SEO guidance.
Page Speed
Page Speed Monitoring at 2025
Explore page speed monitoring in 2025, including key metrics, loading behavior, common slowdowns, SEO impact, UX signals, and performance tracking.
Read article SEO
SERP Monitoring: What is It and Why It Matters
Learn what SERP monitoring is, why it matters, and how tracking competitors, keyword rankings, and search result changes improves SEO strategy.
Read article SEO
The Best Web Site Analysis Tool: Take The Full Control!
Learn what a website analysis tool should measure, from bounce rate and conversions to traffic, rankings, sales, page issues, and optimization tasks.
Read article Google
Google PageSpeed Insights Metrics and How to Use Them
Learn what Google PageSpeed Insights measures, including FCP, TTI, Speed Index, LCP, lab data, field data, and page performance signals.
Read articlePageSpeed Monitoring FAQ
Understand metric coverage, lab versus field data, daily scheduling, URL selection, result freshness, investigation limits, and what a faster result can and cannot prove.
What does Screpy PageSpeed Monitoring measure?
Screpy runs lab-based checks for selected public URLs and shows FCP, LCP, TTFB, TBT, Speed Index, CLS, a performance verdict, the exact URL, and the last-check time.
Is Screpy PageSpeed Monitoring lab data or field data?
It is synthetic lab data collected under a controlled test. Field data describes how real visitors experienced a page, so the two sources should be interpreted separately.
How often does Screpy check a monitored URL?
An active URL becomes eligible for another scheduled check after its latest result is at least one day old. Exact processing time can vary, so use the displayed last-check time to judge freshness.
Which PageSpeed metrics does Screpy show?
The monitoring view includes First Contentful Paint, Largest Contentful Paint, Time to First Byte, Total Blocking Time, Speed Index, and Cumulative Layout Shift, together with a lab performance verdict.
Which URLs should I monitor first?
Start with the homepage, revenue and signup pages, active campaign landing pages, important organic entry pages, and one representative URL from each shared template. The current plan determines how many URLs can be monitored.
Does PageSpeed Monitoring identify the exact cause of a slow result?
No. A weak metric narrows the investigation, but it does not prove the root cause. Review the affected URL, template, assets, scripts, delivery path, and wider website audit before choosing a fix.
Does PageSpeed Monitoring include alerts or historical trend charts?
The current PageSpeed view presents the latest result and check freshness for each selected URL. Do not rely on this page for an alerting promise or a multi-point historical performance chart.
Will a better PageSpeed result guarantee higher rankings or more conversions?
No. Page speed can support visitor experience and page quality, but rankings and conversions depend on many factors. Treat the lab result as one decision input, not a guaranteed outcome.