PageSpeed Monitoring Features
Lighthouse Scores
Track performance, accessibility, best practices, and SEO scores (0-100). Monitor trends over time.
Core Web Vitals
Monitor LCP (Largest Contentful Paint), FID (First Input Delay), CLS (Cumulative Layout Shift)—all Google ranking factors.
Timing Metrics
Track FCP, TTI, Speed Index, and TBT. Identify bottlenecks and optimization opportunities.
Resource Analysis
Monitor page size, request count, and DOM size. Detect bloat before it impacts users.
Mobile vs Desktop
Test performance on both mobile and desktop devices. Different thresholds for each.
SEO Impact Tracking
Core Web Vitals affect Google rankings. Monitor your scores and catch regressions early.
How PageSpeed Monitoring Works
Add Your Page URL
Enter the page to analyze (homepage, landing pages, product pages—any URL).
Choose Device Type
Select Mobile or Desktop (or both). Configure network throttling to simulate real conditions.
Track Performance
Daily Lighthouse runs give you performance trends. Get alerts when scores drop below thresholds.
Who Uses PageSpeed Monitoring?
SEO Teams
Core Web Vitals affect rankings. Track scores and ensure Google sees your site as fast.
Frontend Developers
Catch performance regressions after deployments. Monitor impact of new features on load times.
E-commerce
Every 100ms matters. Slow pages = lost conversions. Track checkout and product page performance.
Marketing Teams
Ensure landing pages load fast. Better LCP = better ad Quality Scores = lower CPC.
PageSpeed Monitoring FAQ
What are Core Web Vitals?
LCP (load time), FID (interactivity), CLS (visual stability)—Google's official user experience metrics. They directly impact search rankings since 2021.
How often are Lighthouse tests run?
Daily by default. Pro and Business plans can run more frequent tests. Tests take ~30-60 seconds per page.
Do you use real Chrome or simulated?
We use headless Chrome with Lighthouse CLI—same as running Lighthouse locally. Real browser, real metrics.
Can I test pages behind authentication?
Yes! Use custom headers, Bearer tokens, or Basic Auth to access protected pages. Same auth options as HTTP monitoring.
What's the difference between mobile and desktop testing?
Mobile uses: slower CPU (4x throttle), smaller viewport (375x667), simulated slow 3G network. Desktop: no throttling, larger viewport.
Why do scores vary between runs?
Performance depends on many factors: server load, network conditions, ads loading. We track trends over time—short-term variance is normal.
Can I monitor non-public pages?
Yes, as long as our monitoring agents can reach them. Staging environments, password-protected pages, etc.