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 →NO_SCREENSHOTS means Lighthouse received no screenshot frames in the trace. It does not prove that the page was blank or slow. In AWS Lambda, the fastest path to a reliable result is to verify that Lighthouse is attached to the Chromium instance you launched, use the complete chrome-aws-lambda launch contract, keep Chrome/Puppeteer/Lighthouse versions compatible, resolve sandbox and memory limits, and repeat runs with stable settings. If failures remain intermittent, run Lighthouse on a persistent VM, container worker, or hosted CI runner instead of a function-as-a-service instance.
What the NO_SCREENSHOTS error actually says
Lighthouse calculates visual metrics such as Speed Index from screenshot frames recorded during navigation. The NO_SCREENSHOTS error means that the trace contains none of those frames, so the performance result cannot be calculated. A run can still contain other audits, and a fast page can still produce this error. Treat it as a browser, tracing, or execution-environment failure first—not as proof that the target page took too long to render.
Lambda adds variables that are uncommon on a workstation: cold starts, changing CPU allocation, constrained memory, container permissions, and concurrent browser processes. A single successful invocation therefore does not establish that the setup is reliable.
Fix it in this order
1. Confirm that Lighthouse is connected to the browser you launched
Start exactly one Chromium process for the invocation, obtain its debugging endpoint, and pass that port to Lighthouse. A mismatch between the launched browser and the port Lighthouse uses can leave you with partial audits but no expected frames. Keep both Lighthouse and Chrome logs in the invocation output; without them, a transient connection or protocol failure is difficult to distinguish from a page problem.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
- Do not launch a second browser through a separate Puppeteer or Chrome launcher.
- Read the port from the running browser’s WebSocket endpoint rather than hard-coding a port.
- Run one URL per diagnostic invocation before adding concurrency.
2. Use the complete chrome-aws-lambda launch contract
The package’s documented settings are a matched set. Use chromium.args, chromium.defaultViewport, await chromium.executablePath, and chromium.headless. Set ignoreHTTPSErrors only when your target requires it, and always close the browser in a finally block so abandoned Chromium processes do not accumulate across warm invocations.
const chromium = require('chrome-aws-lambda');
async function openBrowser() {
return chromium.puppeteer.launch({
args: chromium.args,
defaultViewport: chromium.defaultViewport,
executablePath: await chromium.executablePath,
headless: chromium.headless,
ignoreHTTPSErrors: true
});
}
module.exports.handler = async () => {
let browser;
try {
browser = await openBrowser();
const page = await browser.newPage();
await page.goto('https://example.com', {waitUntil: 'networkidle0'});
return {statusCode: 200, body: await page.title()};
} finally {
if (browser) await browser.close();
}
};The example only verifies that Chromium can navigate. Lighthouse must still attach to that same process, as shown below.
3. Pin compatible Chrome, Puppeteer, and Lighthouse versions
Protocol errors commonly occur when Lighthouse speaks a newer or older Chrome DevTools Protocol than the browser supports. This is especially common when Puppeteer brings its own expected browser revision. Pin the three packages in your deployment, update them as a tested group, and rebuild the Lambda artifact after every change. Do not assume that a package upgrade is isolated just because the JavaScript API still loads.
- Record the versions of
chrome-aws-lambda, Puppeteer, Lighthouse, Node.js, and the Chromium binary in every diagnostic log. - Use one lockfile and one artifact for all concurrent measurements.
- If a protocol error appears after an upgrade, roll back the complete set before changing page settings.
4. Resolve sandbox and container permissions
Chrome can fail before it records frames when the Lambda container cannot create or use its sandbox. A “No usable sandbox” message is an environment failure, not a website failure. Prefer running Chrome with the permissions and user group required by your platform. Use --no-sandbox only when the deployment environment leaves no safer option, and document the security trade-off because it weakens Chrome’s isolation. Some containerized workers require the documented SYS_ADMIN capability.
Recommended Free Tools
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Capture the complete Chrome stderr stream. A missing shared library, denied namespace, or unwritable temporary directory often appears there before Lighthouse reports NO_SCREENSHOTS.
5. Allocate enough Lambda memory
chrome-aws-lambda documentation states that 512 MB is the minimum allocation and recommends 1600 MB or more. Treat that as a baseline, not a guarantee. Lighthouse runs browser, tracing, page JavaScript, and report generation in the same invocation; memory pressure can terminate or destabilize any of them.
- Raise memory before increasing timeout or concurrency.
- Watch the platform’s maximum-memory metric and the duration of cold and warm invocations.
- Keep one browser per invocation while diagnosing; multiple pages multiply CPU and RAM demand.
6. Remove measurement variance
Random timers, A/B tests, third-party scripts, authentication state, geolocation, and throttling can change what Chrome records from one run to the next. Hold device emulation, viewport, headless mode, authentication, network conditions, and geographic placement constant. Block or remove nonessential third-party requests during diagnosis, then reintroduce them deliberately.
Run several measurements instead of trusting one result. Lighthouse CI runs three times by default and allows a higher run count; use the same principle in your own worker and compare the distribution, not only the best score. If only some invocations have frames, note the instance, memory setting, cold-start state, and timestamp for each run.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
7. Move Lighthouse when Lambda remains intermittent
The Lighthouse issue tracker describes this failure as rare and random across Lambda instances, and project guidance cautions against function-as-a-service infrastructure for Lighthouse. When a correctly connected, version-pinned, adequately sized browser still loses frames, a stable worker is usually the practical fix. Moving execution does not repair a bad launch command, so complete the earlier checks first.
A diagnostic Lighthouse runner for Node.js
This script launches one chrome-aws-lambda browser, derives its remote-debugging port, runs Lighthouse against that same process, writes an HTML report, and closes Chrome even when Lighthouse throws. Install versions as a compatible, locked set in your deployment package.
const fs = require('fs');
const chromium = require('chrome-aws-lambda');
const lighthouse = require('lighthouse');
const target = process.argv[2] || 'https://developer.mozilla.org/';
(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 port = Number(new URL(browser.wsEndpoint()).port);
console.error(`Chrome debugging port: ${port}`);
const result = await lighthouse(target, {
port,
output: 'html',
logLevel: 'info'
});
fs.writeFileSync('/tmp/lighthouse.html', result.report);
console.log(JSON.stringify({
url: target,
performance: result.lhr.categories.performance.score,
report: '/tmp/lighthouse.html'
}));
} catch (error) {
console.error(error.stack || error);
process.exitCode = 1;
} finally {
if (browser) await browser.close();
}
})();For Lambda, return or upload the report from a writable location such as /tmp before the invocation ends. Preserve the raw logs and the Lighthouse JSON alongside the HTML report so you can inspect trace and protocol failures after a timeout.
Choose an execution environment deliberately
| Environment | Reliability characteristics | Control you gain | Typical trade-off |
|---|---|---|---|
| Lambda | Variable CPU, cold starts, ephemeral instances, and permission differences can make frame capture intermittent. | Event-driven scaling and regional placement. | Harder debugging, concurrency isolation, and browser-process cleanup. |
| Dedicated VM | Stable hardware and long-lived browser workers make repeated traces more consistent. | Chrome version, sandbox, user, filesystem, and process limits. | You pay for an always-available machine and must operate updates. |
| Container or hosted CI worker | Reproducible images and documented privileges reduce “works on one instance” behavior. | Pinned browser artifact, repeatable runs, and controlled concurrency. | Image maintenance and worker scheduling still require operations. |
For any environment, keep CPU and RAM consistent, isolate concurrent browsers, pin the browser build, and place workers near the geography you intend to measure. A stable worker also makes retries and trend comparisons meaningful.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Performance, reliability, and cost notes
- Increasing Lambda memory can improve CPU allocation as well as available RAM, but it cannot correct a browser-port mismatch or protocol incompatibility.
- Retries are useful for identifying randomness, not for hiding a deterministic launch failure. Record every attempt and its reason for retry.
- Reducing third-party traffic often improves repeatability, but it changes the page being measured; report that condition with the result.
- The project documentation’s statement that its bundle is 40% to 50% faster than an off-the-shelf Puppeteer bundle is a bundle-speed benchmark, not evidence that it prevents
NO_SCREENSHOTS. - Lambda cost depends on memory, duration, invocation count, and concurrency. A persistent worker has a different cost profile: you pay for reserved capacity but gain predictable hardware and fewer discarded runs.
Or skip the browser setup
If your goal is dependable website images or PDFs rather than a Lighthouse performance trace, ScreenshotNeo provides a single-call screenshot API and an MCP server for AI agents. It accepts cookie and consent banners as a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each cleanup step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status.
Use the API documentation at https://screenshotneo.com/docs/ for authentication and options.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo supports full-page captures with lazy images loaded, CSS-selector element shots, dark mode, 12 device presets plus custom viewports, retina scale, PDF paper and page controls, HTML/CSS-to-image, custom JavaScript, clicks before capture, selector hiding, selector or network-idle waits, ad/tracker/request blocking, custom headers, cookies, user agents and Authorization, timezone and geolocation, transparent backgrounds, resizing, chosen cache TTLs, signed image links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, a usage API, and an OpenAPI specification. Common parameter names used by other screenshot APIs are accepted to ease migration.
The MCP server exposes take_screenshot, get_page_info, and capture_pdf to Claude, Cursor, and other MCP clients. Every plan includes every feature. The Free plan includes 1,000 shots per month with no card; paid plans are Starter $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000. Yearly billing provides two months free.
Create a free ScreenshotNeo account to get 1,000 screenshots each month without adding a card.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Troubleshooting matrix
| Symptom | Likely cause | Action |
|---|---|---|
| All runs fail immediately with a protocol error | Chrome, Puppeteer, and Lighthouse are incompatible. | Pin a known-compatible set, rebuild the artifact, and update the packages together. |
| Chrome logs “No usable sandbox” | The Lambda or container lacks required sandbox privileges. | Run under the supported Chrome user/group, add required container capability, or use --no-sandbox only as a documented last resort. |
| Some URLs work, others return no frames | Navigation variance, third-party scripts, bot checks, or authentication differences. | Hold settings constant, capture network and Chrome logs, and test with third-party requests reduced. |
| Failures correlate with cold starts or concurrency | CPU/RAM pressure or multiple Chromium processes. | Use one browser per invocation, raise memory, lower concurrency, and compare warm versus cold runs. |
| Lighthouse reports audits but no screenshots | It connected to a different Chrome port or tracing ended without frames. | Derive the port from the launched browser endpoint, verify one process, and preserve the trace logs. |
| Retries eventually succeed but production scores fluctuate | Lambda instance variability. | Increase run count for diagnosis, then move scheduled measurements to a stable VM, container, or hosted CI worker. |
Frequently Asked Questions
Does NO_SCREENSHOTS mean the page was empty?
No. It only establishes that Lighthouse’s trace had no screenshot frames; the page may have displayed content and other audits may still have completed.
Should I increase the Lighthouse timeout first?
Usually not. Verify the browser port, launch contract, protocol versions, sandbox, and memory before changing timeout; a timeout does not create missing trace frames.
How many runs should I use when validating a fix?
Use repeated runs with identical settings and inspect the failure rate. Lighthouse CI uses three runs by default, and you can increase that count when Lambda variance is high.
When is Lambda no longer a sensible place for Lighthouse?
When a pinned, correctly connected, adequately resourced setup still loses frames intermittently. A persistent VM, container worker, or hosted CI runner then offers more predictable browser and hardware control.
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.
