Run a speed test before and after every deploy. Compare Lighthouse scores, Core Web Vitals, and request waterfalls to catch regressions instantly.
The deploy workflow
You wouldn't deploy without running your test suite. Performance should be no different. A quick test before and after catches regressions that synthetic monitors miss until it's too late.
Save the report URL as your "before" snapshot.
Ship the feature, update, or fix to production or staging.
Open both reports side by side. Scores dropped? Waterfall shows new requests? Catch it now.
Going Pro? Automated CI/CD integration runs tests in your pipeline and fails builds when performance budgets are exceeded. Sign up for early access →
What you get
Get a full Lighthouse audit after every deploy. Catch performance regressions before they reach production users.
Verify that LCP, FCP, TBT, CLS, and TTFB haven't regressed. Compare results against your baseline to catch subtle changes.
See if a new dependency, larger bundle, or additional API call slipped into the build. The waterfall makes it obvious.
Every test is stored for 90 days with a permanent URL. Compare before-and-after deploys and share results with your team.
FAQ
Run a DebugUtils test on your current production URL to establish a baseline. Save the report URL. After deploying, run the same test again and compare the two reports side by side. Look for changes in Lighthouse score, Core Web Vitals, and the request waterfall.
DebugUtils Pro includes CI/CD integration that automatically runs Lighthouse tests in your deployment pipeline. You set performance budgets, and the build fails if scores drop below your thresholds. Sign up for Pro early access to get this feature when it launches.
The most common deploy-related regressions are: increased JavaScript bundle size (new dependencies), additional network requests (new API calls or tracking scripts), larger images without compression, removed caching headers, and new render-blocking resources. The DebugUtils waterfall and metrics breakdown make all of these immediately visible.
At minimum, run a test before and after every production deploy. For high-traffic sites, consider daily automated tests with DebugUtils Pro to catch regressions from third-party script changes, CDN issues, or backend degradation that deploys don't cause.
Yes. DebugUtils tests any publicly accessible URL. If your staging site is behind authentication or a VPN, you'll need to temporarily expose it or use a preview URL. Testing staging before promoting to production is the ideal workflow.
How it works
Paste any URL. We handle normalization, redirects, and protocol detection.
Real Chrome browser runs Lighthouse and captures network data, screenshots, and video.
Scores, metrics, waterfall, filmstrip, video, and recommendations — ready in under 2 minutes.
Paste your URL, get a full report in under 2 minutes. No account needed.
Results are shareable via URL and stored for 90 days.