QA workflow

Compare page performance around a tracking change

Use repeatable page-load checks to investigate a regression without guessing at its cause.

A practical sequence

From inspection to a documented next action.

01

Choose a baseline

Select representative URLs and record the test conditions. Repeat page loads so a single slow request does not become the conclusion.

02

Inspect synthetic measurements

ODDVX captures page-load timings and available vitals. These are lab observations; interaction metrics can be absent or based on a synthetic interaction.

03

Inspect Google requests

Enable Google tag request capture when needed. Request duration helps investigation but does not isolate a tag’s causal effect on page speed.

04

Compare and investigate

Repeat under comparable conditions after an authorised change. Use browser profiling and field data where needed before attributing the regression.

What the result meansPage-load checks can generate real analytics traffic. Synthetic results are not a field Core Web Vitals assessment.
Start free. Repeat with Premium.Free lets you work on one account, property or saved configuration per run, depending on the tool. Premium adds batches, CSV/Excel exports, report email and multiple Google accounts.

Start free

Use this workflow on one client account.

Start with Free for Windows. Review the scope and findings before expanding the run.