NO_SCREENSHOTS means Lighthouse finished a navigation run without finding screenshot frames in its trace. It does not prove that the page was blank or too slow. On AWS Lambda, first verify that Lighthouse is connected to the Chromium instance you launched, then check the chrome-aws-lambda launch settings, browser and Lighthouse version compatibility, sandbox permissions, and memory. If the error persists intermittently across Lambda instances, repeated runs may reduce noise, but a stable VM, container, or CI worker may be a better place to run Lighthouse.
What NO_SCREENSHOTS means—and what it does not
Lighthouse needs screenshot frames in the navigation trace to calculate the Speed Index audit. When the trace contains none, Lighthouse reports NO_SCREENSHOTS and cannot calculate a performance result that depends on that audit. The error describes missing trace data; by itself, it does not show that the page had no visible content, nor does it identify why capture failed.
A reported Lambda reproduction returned the error even for a fast-loading MDN page. That makes page slowness a possible factor to investigate, not a sufficient diagnosis. The Lighthouse issue tracker characterizes the problem as rare and random in Lambda instances, so an intermittent result can be an environment or capture issue rather than a consistent property of the site.
Diagnose the failure in a useful order
Change one factor at a time and keep the Lighthouse and Chrome logs for both a successful and a failed run. This helps distinguish a connection problem from a launch, permission, resource, or variance problem.
Recommended Free Tools
#1 Best Overall
- CRISP CLARITY: This 23.8″ Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
- WORK SEAMLESSLY: This sleek monitor is virtually bezel-free on three sides, so the screen looks even bigger for the viewer. This minimalistic design also allows for seamless multi-monitor setups that enhance your workflow and boost productivity
- A BETTER READING EXPERIENCE: For busy office workers, EasyRead mode provides a more paper-like experience for when viewing lengthy documents
1. Verify Lighthouse is using the Chromium instance you launched
Start one Chromium instance for the measurement, then confirm Lighthouse is targeting that instance’s debugging endpoint. If Lighthouse connects to a different browser—or does not connect to the intended one—it may collect some data without capturing the frames expected in the trace.
- Log whether Chromium launched successfully and which debugging endpoint it exposes.
- Log the Lighthouse invocation and its output alongside the Chrome logs.
- Check that the endpoint passed to Lighthouse belongs to the current invocation, not a stale or reused browser process.
- Compare the endpoint and browser lifecycle in successful and failed runs before changing unrelated page settings.
Do not assume that a report containing some audits proves Lighthouse used the right browser. A partial run can still lack the trace frames required for Speed Index.
2. Use the chrome-aws-lambda launch contract
The chrome-aws-lambda README specifies the package’s launch values: args: chromium.args, defaultViewport: chromium.defaultViewport, executablePath: await chromium.executablePath, and headless: chromium.headless. It also supports ignoreHTTPSErrors. Use the package-provided values rather than substituting a generic local-Chrome configuration without a reason.
Here is the essential browser-lifecycle pattern in Node.js. It shows the package launch contract and cleanup; connect Lighthouse to the debugging endpoint from this browser using the interface supported by the Lighthouse version you have installed.
Rank #2
- CRISP CLARITY: This 22 inch class (21.5″ viewable) Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- 100HZ FAST REFRESH RATE: 100Hz brings your favorite movies and video games to life. Stream, binge, and play effortlessly
- SMOOTH ACTION WITH ADAPTIVE-SYNC: Adaptive-Sync technology ensures fluid action sequences and rapid response time. Every frame will be rendered smoothly with crystal clarity and without stutter
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
const chromium = require('chrome-aws-lambda');
exports.handler = async () => {
let browser;
try {
browser = await chromium.puppeteer.launch({
args: chromium.args,
defaultViewport: chromium.defaultViewport,
executablePath: await chromium.executablePath,
headless: chromium.headless,
ignoreHTTPSErrors: true
});
const endpoint = browser.wsEndpoint();
console.log('Chromium debugging endpoint:', endpoint);
// Run Lighthouse against this browser using the connection
// option supported by your installed Lighthouse version.
// Preserve the Lighthouse result and Chrome logs for diagnosis.
return { statusCode: 200, body: 'Browser launched; run Lighthouse here.' };
} finally {
if (browser) await browser.close();
}
};This is a launch-and-cleanup scaffold, not a complete Lighthouse invocation: Lighthouse’s connection options vary by version, and the available documentation here does not establish a single compatible invocation signature. Add the Lighthouse call appropriate to your pinned version and verify that it uses this browser endpoint. The finally cleanup matters in repeated or warm Lambda execution because abandoned browser processes can consume resources and complicate later runs.
3. Align Chrome, Puppeteer, and Lighthouse versions
Protocol errors can arise when Chrome and Lighthouse are incompatible; Lighthouse CI notes that this is especially common with Puppeteer. Pin compatible versions of the browser package and Lighthouse, and update the pair together rather than upgrading one component in isolation. After a version change, confirm the actual Chromium executable and Lighthouse package used by the deployed Lambda—not only the versions in a developer workstation.
If the logs show a protocol error, resolve that compatibility problem before interpreting missing screenshots as a page issue. A browser connection that starts but cannot communicate correctly is not a sound basis for comparing performance results.
4. Check sandbox and container permissions
Lighthouse CI identifies “No usable sandbox” as a common browser failure. Review the permissions of the Lambda deployment and any container that runs it. Where the environment permits, use a Chrome user group; use --no-sandbox only when the deployment requires it and you understand the security trade-off. Containers may need the documented SYS_ADMIN capability.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Rank #3
- Clear visuals. Fluid motion: A 144Hz refresh rate and 1ms MPRT deliver smooth, tear‑free motion across work, gaming, and streaming for clearer, more fluid viewing.
- Eye comfort: TÜV Rheinland 3‑star* certification reduces harmful blue light while preserving stunning color quality without compromise. *TÜV Rheinland 3-star eye comfort certification.
- Wide viewing angle: Get consistent views across a wide 178° /178° viewing angle.
- In-Plane Switching (IPS): See excellent color accuracy and consistency across wide viewing angles with In-plane Switching (IPS) technology.
- Ultra-thin bezels: Maximize your viewing experience with thin bezels.
Do not add flags blindly. Establish whether the failure is actually related to sandboxing from the Chrome logs and environment first. A flag that lets Chromium start may have security implications and does not, by itself, prove that Lighthouse captured screenshots.
5. Give the Lambda enough memory
The chrome-aws-lambda maintainers state that a Lambda should have at least 512 MB of RAM, with 1600 MB or more recommended. Treat those figures as package guidance, not a guarantee that every run will produce trace frames. If you are below the stated minimum, raise memory before drawing conclusions from the result. If already above it, use logs and repeated runs to determine whether memory pressure is actually implicated.
6. Reduce run-to-run variation
Keep the conditions around each measurement as consistent as possible. Random timers, A/B behavior, unstable third-party requests, and changes in authentication or geography can make runs differ. Hold the device, throttling, authentication state, headless mode, and region constant when comparing results.
Lighthouse CI recommends three runs by default and allows a higher run count. Repeated runs help reveal whether a result is intermittent; they do not repair a broken browser connection, incompatible protocol, or missing permission. Record individual outcomes rather than relying only on an average that can conceal a run with no screenshots.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #4
- CURVED FOR ENHANCED ENGAGEMENT: An immersive viewing experience with a curved monitor that wraps more closely around your field of vision; It creates a wider view, enhancing depth perception and minimizing peripheral distraction
- SMOOTH PERFORMANCE FOR SEAMLESS CONTENT: Stay in the action when playing games, watching videos, or working on creative projects; The 100Hz refresh rate reduces lag and motion blur so you don't miss a thing in fast-paced moments¹
- MORE GAMING POWER: Gain the edge with optimizable game settings; Color and image contrast can be adjusted to see scenes more vividly and spot enemies hiding in the dark; Game Mode adjusts any game to fill the screen so you can view every detail²
- KEEP IT EASY ON THE EYES: Care for your eyes and stay comfortable, even during long sessions; Advanced eye comfort technology certified by TÜV reduces eye strain by minimizing blue light and reducing irritating screen flicker²
- INCREASED VERSATILITY: Connect to more; Plug devices straight into your monitor for increased flexibility, making your computing environment even more convenient
When to move Lighthouse off Lambda
Lambda is convenient for event-driven work, but a performance measurement benefits from predictable browser resources and repeatable conditions. The Lighthouse issue tracker describes NO_SCREENSHOTS as rare and random across Lambda instances, and points to project guidance against function-as-a-service infrastructure. A reported reproduction found a cluster or similarly stable worker to be the practical alternative when Lambda failures persisted.
Choose an execution environment by comparing the factors that affect your measurement and operations:
| Factor | Questions to answer |
|---|---|
| Screenshot reliability | Do trace screenshots appear consistently across repeated runs? |
| CPU and RAM consistency | Are browser resources predictable enough for meaningful comparisons? |
| Browser-version control | Can you pin and update Chrome, Puppeteer, and Lighthouse together? |
| Sandbox permissions | Can the worker run Chrome with the permissions its environment requires? |
| Cold starts and isolation | Do startup delays or concurrent invocations affect the measurement? |
| Geography and settings | Can you keep location, device, throttling, authentication, and headless mode consistent? |
| Operational cost | Does the cost of a stable worker make sense for the frequency and importance of your measurements? |
A dedicated VM, container, or hosted CI worker is not automatically better in every respect; the useful choice is the one that gives your team stable, controllable conditions at an acceptable operating cost. If moving off Lambda removes the intermittency, keep the same pinned versions and measurement settings so that the environment change is the main difference.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Keep Lighthouse screenshots and screenshot capture separate
A website screenshot and a Lighthouse performance result solve different problems. A screenshot service can return an image or PDF of a page, but it does not create the Lighthouse trace frames needed to calculate Speed Index or produce a Lighthouse performance score. If the task is diagnosing NO_SCREENSHOTS in a Lighthouse report, continue to fix or relocate the Lighthouse run; do not treat a separate screenshot as a replacement for that report.
Free tools Windows power users keep installed
One-click scans. No signup required.
Best Value
- 【INTEGRATED SPEAKERS】Whether you're at work or in the midst of an intense gaming session, our built-in speakers provide rich and seamless audio, all while keeping your desk clutter-free.
- 【EASY ON THE EYES】 Protect your eyes and enhance your comfort with Blue-Light Shift technology. This feature reduces harmful blue light emissions from your screen, helping to alleviate eye strain during long hours of use and promoting healthier viewing habits.
- 【WIDEN YOUR PERSPECTIVE】Our sleek minimal bezel design ensures undivided attention. The nearly bezel-free display seamlessly connects in a dual monitor arrangement, delivering an unobstructed view that lets you focus on more at once, completely distraction-free.
Or skip the browser setup
If you only need a website screenshot—not a Lighthouse performance score—ScreenshotNeo can return one with a single GET request. The following cURL example saves a WebP capture; see the ScreenshotNeo API documentation for request options.
curl -G "https://api.screenshotneo.com/v1/shot"
-d access_key=YOUR_API_KEY
--data-urlencode url=https://stripe.com
-o shot.webpScreenshotNeo accepts and removes known cookie-consent banners, newsletter popups, and chat widgets before capture, and those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed; response headers indicate the page verdict and billing status. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for AI agents using Claude, Cursor, or another MCP client. The free plan includes 1,000 shots per month with no card, and paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan to try screenshot capture without a card.
Troubleshooting checklist
| Symptom | Likely area to inspect | Next step |
|---|---|---|
NO_SCREENSHOTS appears only on some invocations |
Lambda instance or run-to-run variability | Keep conditions fixed, retain per-run logs, and compare repeated runs; consider a stable worker if the pattern persists. |
| Lighthouse reports a protocol error | Chrome and Lighthouse compatibility | Pin compatible versions and update them together; confirm the deployed versions. |
| Chrome logs mention “No usable sandbox” | Sandbox or container permissions | Review the deployment’s Chrome user/group and container capabilities; use --no-sandbox only when necessary. |
| Browser launches, but the trace still has no frames | Wrong or stale debugging endpoint, partial connection, or intermittent capture | Log the endpoint from the current browser, verify Lighthouse targets it, and inspect both Chrome and Lighthouse logs. |
| Failures continue under load or in repeated invocations | Memory pressure or unstable execution environment | Meet the package memory guidance, close the browser in finally, and assess whether a VM, container, or CI worker offers more consistent resources. |
A practical decision rule
Fix a confirmed configuration problem first: point Lighthouse at the current Chromium instance, follow the package launch contract, align versions, and resolve permissions. Then stabilize and repeat the measurements. If correctly configured runs still lose screenshot frames intermittently on Lambda, treat that as an environment reliability problem and move the Lighthouse workload to a more stable worker rather than tuning the target page indefinitely.
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.
