How can you compare the same page in a lab report and field report?

Give the page the same label in both reports. A synthetic check runs a browser against a URL or scripted journey. Real user monitoring needs the browser snippet on pages you control and the site domain allowed in settings. Choose a sample rate, the share of visits you want to measure.

Check the session-cookie and collection settings before sending visitor data. A test browser also needs permission and access to the chosen page. If you cannot confirm disposable data and connections for a protected path, inspect an approved report instead.

Why do extra locations or browsers increase test usage?

SpeedCurve counts a synthetic check as one browser page load with performance recorded. Testing the same page from several locations or browsers increases the number of checks. Real-user page views have a separate quota based on collected visits. The pricing page lists a starting price of US$90 per month.

How much old data can you revisit?

SpeedCurve documents 13 months of synthetic data access. Its field retention guide distinguishes archived real-user data from the portion you can access on your plan. Smaller plans get three months of generic real-user access according to the support guide. Check the window you can access before deciding how far back to compare.

Charts can be downloaded as CSV. Keep the date range, page label and conditions beside each export so a teammate can read the comparison later.

What could make two charts disagree?

Draw a lab report and a real-user chart for a fictional pricing page. Use paper only.

Write what each measured
Give both the same page label. Record the fixed lab device and the device group and date range of the field sample.
Check the sample
Show the lab improving and the field sample remaining small. Keep the real-user result uncertain until enough comparable visits arrive.