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
render-blocking-resources computes savings using the FCP graph. In theory this savings estimate should be fine to use for LCP as well since render blocking resources are always loaded before FCP (i.e. none affect LCP and not FCP).
I do wonder how far this assumption goes, and if it's worth it to use the same calculation. Perhaps making a resource non-render blocking doesn't completely eliminate it's LCP impact.
The text was updated successfully, but these errors were encountered:
Related, we were looking at unused-js. Some of the items there can be are render-blocking. Others not.
But when we compute estimatedSavings for unused-js, we treat them uniformly. (Roughly, all network scripts are half- blocking (per lantern magic 🧙♀️ )
We could adjust this behavior to have more precision in the savings calculation.
#15238 (comment)
render-blocking-resources
computes savings using the FCP graph. In theory this savings estimate should be fine to use for LCP as well since render blocking resources are always loaded before FCP (i.e. none affect LCP and not FCP).I do wonder how far this assumption goes, and if it's worth it to use the same calculation. Perhaps making a resource non-render blocking doesn't completely eliminate it's LCP impact.
The text was updated successfully, but these errors were encountered: