You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary
There's a lot of estimates happening in network-analyzer. We can sanity check more of these to make sure there's nothing fishy going on.
In estimateIfConnectionWasReused, compute the maximum number of parallel requests (N) and ensure we have at least N requests that required new connections.
Expand the findMainDocument handling of edge cases
The text was updated successfully, but these errors were encountered:
In estimateIfConnectionWasReused, compute the maximum number of parallel requests (N) and ensure we have at least N requests that required new connections.
In general prevalence of H2 has made this much less relevant and we've moved away from fatal errors when things seem just a little fishy (🎉). It's not clear what we action Lighthouse would take if our estimates determined there were only N-1 available connections instead of N.
Expand the findMainDocument handling of edge cases
Definitely worth doing, but super complicated and I'm already addressing pieces as we go for #8984
Summary
There's a lot of estimates happening in network-analyzer. We can sanity check more of these to make sure there's nothing fishy going on.
estimateIfConnectionWasReused
, compute the maximum number of parallel requests (N) and ensure we have at least N requests that required new connections.findMainDocument
handling of edge casesThe text was updated successfully, but these errors were encountered: