Run a Page Speed analysis on a connected site

Manage GPL ships with a per-site Page Speed tab that runs Lighthouse via Google's PageSpeed Insights API and renders the result inside your dashboard — performance, accessibility, best practices, SEO, plus Core Web Vitals and the top opportunities. This article walks through running an analysis and reading what comes back.

Where to find it

Open any connected site, then click Page Speed in the per-site sidebar (between Uptime and Whitelabel).

Run an analysis

1. Click the Run analysis button in the top-right of the page.
2. The page flips into an "Analyzing your site…" state. Lighthouse typically takes 30–60 seconds to render the page, run its audits, and return a result. The page polls automatically — you don't need to refresh.
3. When the result lands, you'll see a 4-tile score grid, a Core Web Vitals strip, and a list of the top opportunities Lighthouse flagged.

If something goes wrong (the site is behind a login, returned a 5xx, or Google's crawler is blocked) you'll see a red Analysis failed card with the exact error from Google instead of scores.

The 24-hour throttle

Each site can run one Page Speed analysis every 24 hours. Once you run one, the button switches to "Available {time}" and stays disabled until 24 hours have passed since the last run.

This applies whether the run succeeded or failed. A failed attempt counts the same as a successful one — without that rule, a broken site would let you loop the API endlessly. If a run gets stuck (worker crashed mid-job, etc.), it's automatically released after 5 minutes.

Reading the four category scores

Each score is 0–100. Lighthouse colors them green (≥90), amber (50–89), or red (<50) — same convention as pagespeed.web.dev:

• Performance — how fast the page loads and becomes interactive. The score most people obsess over, and the one Google uses as a ranking signal.
• Accessibility — automated checks for things like color contrast, missing alt text, ARIA labels. A high score doesn't guarantee accessibility (manual review is still needed) but a low score reliably means there are issues.
• Best Practices — modern web hygiene: HTTPS, no console errors, no deprecated APIs, image aspect ratios, etc.
• SEO — basic SEO hygiene: meta description present, title tag, viewport meta, mobile-friendly tap targets, robots.txt valid. Doesn't measure ranking — just the technical fundamentals.

Core Web Vitals

Below the score grid, the Core Web Vitals strip surfaces the lab measurements that matter most for user experience:

• LCP (Largest Contentful Paint) — when the main content of the page becomes visible. Good < 2.5s, poor > 4s.
• INP* (Interaction to Next Paint, approximated by Total Blocking Time in lab runs) — how responsive the page feels to clicks/taps. Good < 200ms, poor > 600ms.
• CLS (Cumulative Layout Shift) — how much the page jumps around as it loads. Good < 0.1, poor > 0.25.
• FCP (First Contentful Paint) — when the first text or image appears. Good < 1.8s.
• TTFB (Time to First Byte) — how long the server took to respond. Good < 0.8s.

Each tile is colored green / amber / red against those thresholds.

Top opportunities

Below the metrics, Lighthouse lists the audits with the largest estimated time savings — typically things like "Reduce unused CSS," "Eliminate render-blocking resources," "Serve images in modern formats." These are sorted by potential savings (highest first) and capped at the top 5 to keep the page focused on the wins worth chasing.

Plan requirement

Page Speed analysis is included on the Developer and Agency plans. Free plans see a blurred preview of the page so you can tell what's there, but the run button is disabled and the data is mock — upgrade to enable it on your sites.