Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Performance Audit 2017: Unload beacon size #168
We should investigate if we want all of the data we have on the unload beacon.
That's only 487 bytes less on the unload beacon. We might want to skip things like the
I also think we should have a better system for removing data once it has been beaconed. I like how the User Timing API plugin has a mechanism to ensure that data sent on load is not also sent on unload.
Presumably, there are some cases where you may still want that data. I think it would be helpful if we exposed an easier method to remove data once it is beaconed.