How do measurements reach your report?
Install the Request Metrics browser agent, code that runs in a visitor’s browser, with the token for the intended website. The vendor documents a snippet, package and script-tag options. The browser agent collects performance information from visits. A separate Lighthouse test runs a controlled page load.
On a test page, confirm the intended destination and collection options before the agent runs. Review the URLs and optional data fields it could send. Use fictional inputs or inspect existing approved reports when you cannot confirm isolation.
What can a lab result leave unanswered?
A Lighthouse result shows one set of conditions and can point to a heavy file or slow load. A real-user report shows measurements from the visits the agent could observe. A browser that blocks the agent or a small number of visits can leave gaps in that report.
How long can you compare results?
The plan table lists 24 hours of retention on Free, 30 days on Essentials and 90 days on Professional. Free lists one website, 1,000 monthly page views and Core Web Vitals monitoring. The plan comparison lists the separate Real User Monitoring and Lighthouse Performance Testing features from Essentials onward. Paid plans have larger traffic allowances. The provider counts monitored page views and allocates traffic capacity over time.
Save useful filtered reports as CSV while they are available. The billing docs say cancellation closes the account and purges data, so keep the reports and their date ranges before canceling.
What should you check if the field report is empty?
Draw a fictional page with a lab report and no real-user measurements. Run no browser agent or external test.
- Check the pathWrite where the browser agent should load and which test website should receive data.
- Keep the results separateMark lab results as a test and field coverage as unknown. Do not treat a missing report as a fast visit.