LightAudit Score – Lighthouse and PageSpeed Insights in one local console LightAudit Score, a free local console from LightAudit, runs Lighthouse v13 on a user's own machine to audit localhost, staging, VPN, and intranet sites that hosted tools cannot reach, offering median-of-N runs, calibration to hardware, integrated PageSpeed Insights and CrUX field data, and an AI that explains low scores with prioritized fixes. The tool supports batch crawling, desktop and mobile paired audits, and requires a free Google API key for PSI, with a free tier of 25,000 requests per day. Lighthouse and PageSpeed Insights. One local console. Free. LightAudit Score runs Lighthouse on your machine , so it audits localhost, staging and VPN sites that hosted tools can't reach. Whole sites in one batch, median-of-N runs for numbers you can defend, Google's real-user field data next to your lab scores, and an AI that explains why a score is low and how to fix it. Your Chrome, your keys, your AI. $0. 2.1 s 140 ms 0.06 Calibrate Audit the pages Google can't see. PageSpeed Insights needs a public URL. LightAudit runs the same Lighthouse v13 engine on your own machine, so localhost:3000 , a staging box behind a VPN, and the intranet app nobody can link to all get audited exactly the same way. Localhost, staging, VPN, intranet If your Chrome can open it, LightAudit can audit it. No tunnels, no temporary public URLs, no "we'll check it after deploy". Whole sites in one batch Paste a list of URLs, or crawl a site: sitemap plus a robots-aware, same-origin crawl with depth, max-page and exclude-path controls. Preview the discovered pages, then audit them all. Live, per-URL progress Every page streams queued → running → done with score rings and Core Web Vitals LCP, CLS, TBT, FCP, SI, TTI as they land. Open the full Lighthouse HTML report from any card. Desktop + mobile, paired Audit both form factors in one run and read them side by side, instead of running everything twice and reconciling by hand. Numbers you can defend in a code review. Lighthouse Performance swings about ±5 points on identical runs, because Total Blocking Time is CPU-sensitive and worth roughly 30% of the score. One run is an anecdote. LightAudit is built around making the number trustworthy. Median of N, isolated Chrome, one job per process Each URL is audited N times default 3 and Lighthouse's own computeMedianRun picks the representative run. Every run launches a fresh headless Chrome with a cold profile, and every job runs in its own forked Node process so concurrent audits can't poison each other's timings. Calibrate to your hardware Lighthouse's default 4× CPU throttle only lands on "mid-tier mobile" from a high-end desktop. A fast Mac under-throttles and reads optimistically. Calibrate reads your host's benchmarkIndex and picks the multiplier that targets mid-tier mobile from your machine. Match DevTools preset One click sets mobile, simulated throttling, single run, concurrency 1 and Lighthouse's own 4×, so a local number is directly comparable to the Chrome DevTools Lighthouse panel on the same machine. Drift warnings and an environment badge Every result shows the host power, throttling method and multiplier it ran under, and flags when the machine , not the page, moved the score: host-power drift, CPU contention, or concurrency contention. Accuracy mode serialises Performance runs automatically. Lab and field, in the same table. Lab scores tell you what the page does in a controlled run. Field data tells you what real Chrome users experienced. You normally get them from two different tools with two different histories. Here they share one. PageSpeed Insights, built in The same paste-or-crawl input, audited by Google's hosted Lighthouse instead of your Chrome. Runs carry a cyan PSI badge in History so you never confuse the two. Real-user Core Web Vitals from CrUX LCP, INP and CLS at the 75th percentile, per URL and per origin, with good / needs-improvement / poor distribution bars beside the lab scores. Your own free Google key PSI needs an API key now keyless calls are capped at zero . LightAudit walks you through creating one; the free tier is 25,000 requests a day, per user. The key is read server-side from your .env and never sent to the browser. Ask why. Get prioritised, cited fixes. A score tells you something is wrong. Click it and the AI reads the actual audit data, explains what's dragging the category down, and returns concrete fixes with steps, a priority, and, when a research server is connected, citations to sources it actually opened. Analyses are stored with the run, so reopening a report costs nothing. Researching · fetched web.dev/lcp Diagnosis. LCP is 2.9 s because the hero image is a 1.4 MB PNG served at native resolution and discovered late by the preload scanner. TBT 380 ms comes almost entirely from a single 640 kB analytics bundle that executes on the main thread before hydration. Serve the hero as responsive AVIF and preload it HighCuts the LCP resource by ~85% and lets the browser discover it before CSS resolves. - Export the hero at 640 / 1280 / 1920 widths as AVIF with a WebP fallback. - Use