Tight Mode: Why Browsers Produce Different Performance Results
Chrome and Safari both enforce a behavior called “Tight Mode” that changes how page resources are prioritized during loading—but almost no documentation exists about it. The term surfaced in a conversation with DebugBear's Matt Zeunert, who pointed to resources that led to a new Smashing Magazine article on the subject.
Tight Mode discriminates resources, taking anything and everything marked as High and Medium priority. Everything else is constrained and left on the outside, looking in until the body is firmly attached to the document, signaling that blocking scripts have been executed. It’s at that point that resources marked with Low priority are allowed in the door during the second phase of loading.
The practice has major implications: resources are not treated equally at face value. Chrome and Safari approach Tight Mode in wildly different ways, so performance results diverge significantly depending on which browser runs the test. Firefox does not enforce the mechanism at all, producing a third distinct behavior for resource fetching and rendering.
This makes web performance a moving target. Core Web Vitals offer a consistent set of metrics for evaluating and discussing performance, but those numbers cannot be consistent across browsers when resource access and prioritization differ underneath.
