New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance Audit 2017: Beacon: Review cookie access #173

Open
nicjansma opened this Issue Dec 22, 2017 · 0 comments

Comments

Projects
None yet
1 participant
@nicjansma

nicjansma commented Dec 22, 2017

Boomerang and its plugins are getting/setting the page's cookie several times during the onload beacon preparation.

In most browsers, getting and setting the cookie is a semi-expensive operation, since it often involves reading or writing state to the disk.

RT alone calls getCookie 6 times during the load beacon preparation:

image

We should investigate if all of these gets/sets are necessary and combine/eliminate any extraneous ones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment