Recommended Free Tools
Use Cypress to drive a repeatable user journey, then run Lighthouse against the page state you want to assess. Cypress automates application behavior; Lighthouse audits page performance. Cypress test-suite runtime is not a substitute for Lighthouse metrics, and a Lighthouse lab result is not the same as real-user field performance.
Decide what performance question you are answering
Before choosing a tool or wiring up CI, identify what you need to measure. These are related but distinct questions:
As an Amazon Associate I earn from qualifying purchases.
- Is the Cypress suite slow? Measure and optimize test execution. Cypress’s performance guidance concerns the speed and diagnosis of Cypress tests, not Lighthouse measurement of the application.
- How does a page perform after a user journey? Use Cypress to reach the relevant page or state, then audit that state with Lighthouse.
- How are real users experiencing the site? Use field data where available, such as the CrUX data shown by PageSpeed Insights, and distinguish it from Lighthouse lab results.
Lighthouse is an open-source automated web-page auditing tool. Chrome documents running it in DevTools, from the command line, or as a Node module, as well as using Lighthouse CI to help prevent regressions: Lighthouse overview.
Free tools Windows power users keep installed
One-click scans. No signup required.
Build a repeatable Cypress journey and Lighthouse baseline
- Choose the page and state. Decide which URL and application state matter. If the performance question concerns a state reached after login, navigation, or an interaction, make that journey explicit in the Cypress test.
- Automate the journey. Cypress launches and controls a browser in an isolated profile, which supports repeatable browser-based application journeys and CI use. See the Cypress browser documentation.
- Run an initial Lighthouse audit. Record a baseline before changing the application. Chrome’s guidance recommends using an audit to identify likely improvements: Lighthouse overview.
- Record the conditions. Keep the URL and state, browser and device profile, navigation mode, storage and cache treatment, network and CPU throttling, and tool versions consistent between runs. Decide these deliberately rather than allowing settings to drift.
- Make one change and repeat. Use the audit findings and DevTools Performance panel to investigate, change one thing at a time, and compare under the same conditions. A single before-and-after comparison is easier to interpret when the environment has not changed.
For an audit immediately after a Cypress-driven journey, use a compatible Lighthouse integration only after checking its current package documentation, Cypress and browser requirements, configuration, and threshold behavior. Chrome documents Lighthouse as a Node module or CLI and documents Lighthouse CI, but a universal, current Cypress-plugin installation recipe is not established here. Cypress community plugins are community-owned, not automatically official integrations; the Cypress plugin directory distinguishes community work.
#1 Best Overall
Choose metrics and interpret results carefully
Do not use a single Lighthouse score as the whole result. Inspect the underlying metric values and relevant audit details, then assess whether the findings relate to the user experience you are trying to improve. Lighthouse aggregates metric scores, and results can vary with test conditions. Chrome’s historical Lighthouse 3.0 announcement put the principle plainly: “There’s no single load performance metric that captures all use cases across the web, so Lighthouse provides many different ones, so that you can build a holistic picture of your performance.” The statement is from a 3.0 announcement, not a current scoring specification: Lighthouse 3.0 announcement.
Audit details may include request count and transfer size, DOM size, and third-party code impact. Treat these as investigative clues, not automatic proof of a user-visible problem or a guaranteed way to change the overall score. Audit names and placement can change between versions; Chrome notes that Lighthouse 13 reorganized the DOM-size and third-party audits: Lighthouse performance audits.
Rank #2
Separate lab results from field performance
A Lighthouse audit is a lab measurement under its chosen conditions. It does not by itself establish how all visitors experience the site. PageSpeed Insights can show Lighthouse lab results alongside Chrome User Experience Report (CrUX) field data when such data is available. Label and interpret the two kinds of evidence separately: lab results are controlled estimates, while CrUX reflects field experience from real Chrome users. See About PageSpeed Insights.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Set regression checks without overreacting to noise
Thresholds are useful only when they reflect repeatable baselines and the product’s actual performance needs. Establish a baseline across stable runs, then investigate surprising results under controlled conditions before making a failed score block a build. A fluctuating Lighthouse result can reflect test conditions rather than a code regression. Lighthouse CI is one documented option for performance regression prevention; its use does not remove the need to choose sensible conditions and thresholds: Lighthouse overview.
Common problems and fixes
- The Cypress run is slow, but Lighthouse looks fine. These tools measure different things. Investigate Cypress test execution using Cypress’s performance guidance; do not interpret suite runtime as page performance. Cypress test performance.
- The score changes between runs. Recheck browser and tool versions, device profile, navigation mode, storage/cache treatment, throttling, and the exact page state. Repeat under the same conditions before treating the difference as a regression.
- A suggested Cypress-Lighthouse plugin does not work. Check its current maintenance status, supported Cypress and browser versions, configuration requirements, and how it implements thresholds. A community listing does not mean the integration is official: Cypress plugin directory.
- A Lighthouse audit name or location differs from a guide. Guides may describe older Lighthouse versions. Check the current documentation; Lighthouse 13 reorganized some audits, including DOM-size and third-party findings: Lighthouse performance audits.
- Lab results improve, but field experience does not. Compare the same relevant page and time context in PageSpeed Insights, and check whether CrUX field data is available. Lab and field results describe different evidence: About PageSpeed Insights.
Or skip the browser setup
If the job is to capture a clean screenshot rather than audit performance, ScreenshotNeo provides a website screenshot API and MCP server. A single GET request returns an image or PDF; it is not a replacement for Cypress journeys or Lighthouse performance audits.
cURL example (see the ScreenshotNeo documentation for options):
Rank #4
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts cookie/consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; those steps can be disabled. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, with response headers identifying the page verdict and billing status. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.
Sign up for 1,000 free screenshots a month, with no card required.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently Asked Questions
Can Lighthouse tell me whether a Cypress test suite is too slow?
No. Cypress suite runtime and Lighthouse page-performance metrics answer different questions; use Cypress performance guidance for slow tests.
Best Value
- Used Book in Good Condition
Does a Lighthouse score represent real-user performance?
Not by itself. Lighthouse is a lab audit; PageSpeed Insights may also show CrUX field data when available.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitches
