Closed patrickhulce closed 5 years ago
all these struggled with TTI, but all also hit the 30s timeout
loadEventEnd
) was usually not found in the trace taken30s may be too short
the new throttling is going to make this true for a lot of sites now, we will basically fail on all sites from deep's TTI variability study that had TTI of >25s, which is a lot
re: https://airhorner.com I'm not seeing anything fishy, what fails usually? re: https://react-hn.appspot.com/ to provide more color here, this app actually renders in response to websocket messages and fixing would require a CPU quietness signal over the protocol since we can't reasonably guess when to stop tracing with the current network request signals alone
atob is not defined
debug string)@benschwarz could you elaborate with what issues you're seeing there? On a couple runs the only issue I'm seeing is running up to the 30s timeout before TTCI is computed
@benschwarz could you elaborate with what issues you're seeing there? On a couple runs the only issue I'm seeing is running up to the 30s timeout before TTCI is computed
Ok, if it runs at all it must've been fixed in the last two weeks. π The 30s timeout is a whole other thing, which is being tracked elsewhere, right?
[ ] https://www.davidemaggio.it/ fails to finish.
large number of network requests: ~300
huge number of DOM nodes: 11,180 to be precise. Lighthouse spends a lot time in evaluating getEventListeners for ExternalAnchorsUseRelNoopenerAudit
and other related audits.
@patrickhulce any update on these issues? we are experiencing TTI issues quite frequently during our testing
@upugo-dev these were mostly addressed by 3.0 and is quite old, probably a candidate for closing. If you have a specific, reproducible error on a particular URL then file it in a separate issue π
these were mostly addressed by 3.0 and is quite old, probably a candidate for closing
closing! We can have other issues for sites that give Lighthouse trouble without confusing things mixing in pre-3.0 issues :)
To Investigate
Axe failures
Service worker/offline issues
Stopped tracing too early
Site misbehavior (aborted request, failed document, extremely slow server, etc)
Working but needed more than 30s
Working as of 2.6
Legend
π¨ = can be flaky (received a bad trace or axe failure on at least one run, but not reproducible) π’ = undesirable metric result (but correct according to definition) π = Lighthouse is slow, i.e. multiple seconds spent in gathering/auditing