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
We've been looking at reducing our bandwidth costs when running Lighthouse recently. If I understand correctly, running Lighthouse currently opens the tested page 1 or 2 times:
Is it possible to block e.g. image requests for the bf cache navigation? And maybe also others like JavaScript? Since the point is just to check if the page can be served from the bfcache. Doing that would also reduce CPU load.
Not sure if there are any reasons to load the page in full. Like bfcache checks for iframes maybe?
I can submit a PR for this if there's interest.
The text was updated successfully, but these errors were encountered:
mattzeunert
changed the title
Reduce bandwidth usage when runnin bfcache check
Reduce bandwidth usage when running bfcache check
Jan 31, 2025
Not a bad idea, Lighthouse used to test the page with network requests blocked to verify offline behavior I believe. I wonder if we could get away with blocking all network activity. Can maybe disable JS too.
We've been looking at reducing our bandwidth costs when running Lighthouse recently. If I understand correctly, running Lighthouse currently opens the tested page 1 or 2 times:
Is it possible to block e.g. image requests for the bf cache navigation? And maybe also others like JavaScript? Since the point is just to check if the page can be served from the bfcache. Doing that would also reduce CPU load.
Not sure if there are any reasons to load the page in full. Like bfcache checks for iframes maybe?
I can submit a PR for this if there's interest.
The text was updated successfully, but these errors were encountered: