What does one test measure?
+
Google PageSpeed Insights on mobile and on desktop: four Lighthouse scores (Performance, Accessibility, Best Practices, SEO), lab metrics (FCP, LCP, TBT, CLS, Speed Index), opportunities and diagnostics, and field data from the Chrome UX Report when it exists. PerfBee also loads the page in its own browser for a request waterfall, page weight by type and by domain, and a filmstrip.
How does PerfBee decide a page got slower?
+
Each run is compared with that page's own average over the last 15 days by default. It counts as a drop when the score falls by your point threshold or more (10 by default, on mobile and desktop), or when mobile LCP or mobile CLS gets worse by the percentage you set.
Why one page per template?
+
Pages built from the same template usually slow down together. A monitor holds up to 10 pages, so PerfBee suggests your homepage plus one page per template from your latest crawl.
Does it measure INP?
+
Yes, from field data. INP comes from real Chrome users in the Chrome UX Report, when the page or site has enough traffic. A lab run cannot measure it.
What's the difference between lab and field data?
+
Lab data is one controlled load of the page on every run, and it explains why with opportunities. Field data is the 75th percentile from real Chrome users over 28 days, for the URL or the whole site, and it needs enough traffic.
Does PerfBee change my code?
+
No. AI fix suggestions (Business and up) give your team steps and code to review. PerfBee writes the fix; a person applies it. PerfBee never edits your site.
How do I start?
+
Sign up for free and run a test from the dashboard, or set up a monitor. To test one page without an account, use the free page test.