Why does my page score lower here than in my dev tools?

PSI runs on a throttled mobile device profile to simulate real users. Your dev tools usually run on your desktop hardware — much faster.

Is this lab data or field data?

Lab data (Lighthouse run on demand). For field data, see the Core Web Vitals Checker.

Why did one URL fail with a quota error?

PageSpeed Insights API has a daily quota. Spread large runs across days or use a Google API key for higher quotas (paid LemWatch plans).

Can I run desktop instead of mobile?

Bulk mode runs mobile by default (the strategy Google uses for indexing). For desktop, use the single-URL Page Speed Test.

How long does a 25-URL run take?

Usually 90 to 120 seconds. Three URLs are measured at a time so each page gets a clean, uncontended test, and slow or heavy pages can push a full batch slightly past two minutes. Leave the tab open until the run finishes.

Why does the same URL get slightly different scores each run?

Lighthouse runs are subject to variance (CPU contention in the lab environment). Run twice and take the better score for trend tracking.

Free Tool

Updated 6 June 2026

Bulk PageSpeed Checker

Run PageSpeed (Lighthouse) on up to 25 URLs in one go. Performance score, LCP, CLS, and TBT per URL — exportable.

By Deepak Shukla — Founder & CEO, Pearl Lemon

Paste your URLs — one per line, up to 25

0 URLs ready

What This Tool Checks

Lighthouse Performance score (0–100) per URL
Largest Contentful Paint (LCP)
Cumulative Layout Shift (CLS)
Total Blocking Time (TBT)
Per-URL performance summary

Why This Matters

Core Web Vitals are a real ranking factor and every page is graded individually. Without bulk visibility you only optimise what you remember to check.

How to Fix Issues

1.Sort the CSV by score ascending — the slowest pages are the biggest SEO opportunity
2.For pages with high LCP, audit hero images first (compress, preload, use modern formats)
3.For pages with high CLS, audit images and embeds without dimension attributes
4.For pages with high TBT, audit third-party scripts — analytics, chat, A/B testing

Lighthouse is the gold standard for page-speed audits — but running it per URL is slow. Bulk PageSpeed checks let you score a whole site map in one paste so you can prioritise optimisation by impact, not by gut feel.

What this tool does

Paste up to 25 URLs. We trigger a Lighthouse run against each (via Google's PageSpeed Insights API), extract the Performance score and core metrics, and return them in a sortable table. Export to CSV and you have a prioritised optimisation backlog.

How to read the results

Score is the Lighthouse Performance score 0–100. LCP under 2.5s is good, 2.5–4s needs work, over 4s is poor. CLS under 0.1 is good, 0.1–0.25 needs work, over 0.25 is poor. TBT under 200ms is good, 200–600ms needs work, over 600ms is poor.

Methodology

We call Google's public PageSpeed Insights API for each URL with strategy=mobile by default. PSI runs a full Lighthouse audit in a controlled environment and returns metrics from the lab run. We extract: Performance score, LCP, CLS, TBT, and FCP. We do NOT mix in CrUX field data in bulk mode for consistency — lab metrics are reproducible across runs, field data is not. Each URL takes 10–25 seconds; the bulk runner caps parallelism at 3 to avoid PSI rate limits.

Frequently Asked Questions

Monitor this continuously with LemWatch

A one-off bulk pagespeed checker shows you today. LemWatch re-runs the same checks around the clock and alerts you the moment something breaks — free for up to 10 sites, no card needed.