Connect Google Page Speed to Power BI

Configure the page URLs to test through Catchr's Google Page Speed source. In Catchr’s Power BI query builder, select page, device and selected performance indicators and preview a short extraction. Import the generated URL through Get data > Web in Power BI Desktop. Check the returned rows before building measures, keeping page, device and test observation time clear in the model.

Catchr exposes the Lighthouse Performance, Accessibility, Best Practices and SEO scores, along with supported timing and diagnostic metrics. Keep the category scores separate: a strong SEO audit score does not mean a page loads quickly, and a fast page does not guarantee that accessibility checks pass.

Google classifies 90–100 as good, 50–89 as needing improvement and below 50 as poor. Treat the score as a diagnostic indicator, not a revenue or ranking forecast. Use the individual speed metrics to identify what needs work.

The tests use different simulated device and network conditions. Compare mobile with mobile and desktop with desktop when checking a change. Keep the device visible in your dashboard instead of averaging both scores into one number.

Test conditions can vary between runs, including network and available computing resources. Investigate a repeated pattern rather than one isolated score. Retest the same URL and device before deciding that a release caused a regression.

No. Lighthouse lab testing simulates a page load, while real-user Core Web Vitals describe visitors' experiences. The measures are related but can disagree. Label lab metrics clearly and do not present a Lighthouse performance score as proof that the site passes the real-user assessment.

The PageSpeed Insights endpoint runs an analysis of the page; it is not an archive of every past test. Catchr's connector does not send a historical test date to that endpoint. To measure a trend, retain results from repeated tests in a stored dataset rather than expecting a date filter to recreate an old page load.

Yes. Put PageSpeed results alongside Search Console clicks and impressions for the same landing pages. Use the comparison to prioritize investigation. A change in traffic alone does not prove that speed caused it, because rankings, demand and page content can change at the same time.