I partially agree, but on the other hand — 0.25s is quite a lot.

And, keep in mind that reducing load time by 0.25s for a decent network/browser will be an even larger (and noticeable) win for slower networks and/or devices.

I too am used to super-fast network connections, so when travelling somewhere with crappier connectivity, everything seems to take forever to load. The finest A/B tested copy and button colors will not help you if I close the page because I had to stare at a blank loading state for too long :)

Do you mean “good” from the user's perspective, or from a business perspective? Because for many businesses, the best consent form is probably something that obscures the details and tries to force the visitor to choose YES! — using deceptive labels, tiny cancel buttons, manipulative copy.

I believe the best user consent form is the one you don't have.

If designing a consent thing is a challenge, then there are too many options (like a thousand 3rd party trackers and spammy newsletters).

If you can edit the post, encose the code snippet in backticks, so it renders correctly :)

@Igor A sidenote: the cookie should be: document.cookie="VISITOR_INFO1_LIVE=fPQ4jCL6EiE" (markdown ate your underscore characters)

They just moved it:

Don't have any actual research to show, but it seems the safe and reasonable thing to do would be simply: default the checkbox to checked on mobile…

And Apple:

I believe the DocumentRevisions data will get automatically cleaned up when disk space gets low enough. That is — you will get a space boost by deleting it, but the actual effect is mostly psychological, as that space is never really "permanently" lost in the first place :)

Do your web apps have settings screens to hide menus I don't want to see? ;)