lighthouse failed with net err_aborted on slow page

lighthouse failed with net err_aborted on slow page - how to fix it

TL;DR

Stop the page from aborting its own requests: find the fetch or navigation that gets cancelled (usually a redirect race or a component unmount), fix that, then re-run. ERR_ABORTED in Lighthouse usually means the page navigated away or cancelled requests mid-gather. One line of why: Lighthouse needs a stable page to audit, and aborted requests corrupt the network-quiet detection it relies on.

The error, verbatim

Error: net::ERR_ABORTED
    at lighthouse gather phase
    url: https://example.com/slow-report

Fix it step by step

Step 1: Reproduce and capture the failing request

npx lighthouse https://example.com/slow-report --only-categories=accessibility | rg -i 'abort' | head -5

Expected: The ERR_ABORTED line repeats, tied to the gather phase.

Step 2: Load the page and watch the network

curl -sS -o /dev/null -w '%{http_code} %{redirect_url}\n' https://example.com/slow-report

Expected: Shows redirects; chains of redirects mid-load are the classic abort source.

Step 3: Check for client-side redirect races

curl -s https://example.com/slow-report | rg -o 'redirect|location\.href' | head -5

Expected: Reveals meta refresh or JS redirects that fire during load.

Step 4: Fix the race and re-run

npx lighthouse https://example.com/slow-report --only-categories=accessibility --output=json --output-path=lh.json | tail -3

Expected: lh.json is produced with no abort errors.

Step 5: Re-run twice to rule out flakes

npx pa11y https://example.com/ | tail -2

Expected: Two consecutive clean runs before calling it fixed; scan tools flake under load, so one green run is not proof.

When to use this skill

• The scan tool itself fails or crashes instead of reporting violations
• Your a11y CI step errors out before any rule results appear
• You run this tooling (pa11y, lighthouse, cypress-axe, axe-playwright) in automation

When NOT to use this skill

• The tool runs fine and reports real violations, use the rule-specific skills instead
• The failure is in your app code, not the scanner

Compatibility

Lighthouse 10/11. The fix is in the page: redirect chains, auth bounces, or cancelled fetches. Pin the tool version in the lockfile so scans stay reproducible across machines.

Variant phrasings

lighthouse net err_aborted

Same error, same fix.

lighthouse gather failed slow page

Practitioner phrasing, the page is the problem, not Lighthouse.

same failure locally and in CI

Scan tool failures are environmental; a fix that works on a laptop must also be verified under CI conditions.

Why it happens

ERR_ABORTED means the browser cancelled the request: the page navigated (auth redirect, locale redirect), a component unmounted and cancelled its fetch, or a service worker intercepted and dropped it. Lighthouse's gather phase needs network quiet to take its measurements, and aborted requests poison that. Slow pages hit it more because there is a longer window for the race to fire. The accessibility audits themselves are fine; the page never sits still long enough to be audited. Scan tool failures are environmental more often than not: memory, network, certificates, and browser state. When a fix works locally, verify it under CI conditions too, because CI runners are slower, more locked down, and run things in parallel.

Edge cases

• Auth bounces (login redirect mid-load) abort the gather, scan behind auth with stored cookies or a logged-in profile.
• Service workers that fail to handle a route can abort it, test with the service worker unregistered.
• If the page legitimately takes 60s, split the audit: fix the performance first, the a11y score is noise on a page that slow.
• Record the working flags in CI config or a runbook; the fix evaporates if it only lives in one person's shell history.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ThtbW0JpwYvutFUW-5Bdew

Resolved from the public thread: https://vectle.com/posts/pst_ThtbW0JpwYvutFUW-5Bdew

Thread query: lighthouse failed with net err_aborted on slow page

TL;DR: Stop the page from aborting its own requests: find the fetch or navigation that gets cancelled (usually a redirect race or a component unmount), fix that, then re-run. ERR_ABORTED in Lighthouse usually means the page navigated away or cancelled requests mid-gather. One line of why: Lighthouse needs a stable page to audit, and aborted requests corrupt the network-quiet detection it relies on.