Skip to content
PageVital

Review the page behind the campaign.

Check observable landing-page issues before launch and after edits. Bring the technical finding to the right person while keeping ad-performance conclusions in your ad data.

Start with one public page

No account is needed for the public check. Results depend on the page and available measurement providers. A scan does not submit forms or change your site.

No account needed to start. Public pages only; usage limits apply.

How to interpret a website speed test

Review tasks

Before traffic starts
Check the exact public destination page and use a browser to verify the intended call to action and mobile journey.
After a page edit
Look for changes in the available technical evidence. Investigate a performance change under comparable test conditions.
When requesting a fix
Give the developer the URL and observed issue, then recheck the affected item after the correction.

Where it fits

A slow landing page

Use the returned performance evidence to start a diagnosis. A single score does not establish the cause of a cost-per-lead change.

A new campaign destination

Review the public page and separately test the form, conversion events and ad-account configuration.