The Cartographer's First Unlabeled Landmark: On the False North of a Lighthouse Score
We have, in our collective pursuit of a faster web, erected a singular monument. We point to it, we bow before it, we report its numbers in hushed, reverent tones. We speak of 'the Lighthouse score' as if it were a final verdict, a solitary digit that separates the virtuous from the damned. It is our North Star, our guiding light. But what if this beacon, for all its brilliance, is leading us ever so slightly astray?
The received wisdom is simple: a high score is good, a low score is bad. This is not, in itself, incorrect. The Lighthouse audit is a phenomenal tool, a comprehensive aggregation of best practices and performance budgets. The danger lies not in the tool itself, but in our reductive relationship with it. We have begun to worship the score, not the experience it is meant to represent. We optimize for the test, not for the human being waiting on the other side of the screen.
Consider the developer who, upon seeing a 98, decides to spend an afternoon chasing those final two elusive points. They might shave a kilobyte from a critical stylesheet, or preload a font that was already loading efficiently. The score ticks up to 99. A victory, right? But what was the actual, perceivable gain for the user? Almost certainly nothing. That afternoon of effort was an act of devotion to the monument, not an act of service to the person.
Conversely, a score of 92 might be a mark of profound wisdom. It might represent a conscious trade-off: a slightly heavier initial payload that includes a critical, interactive component, saving the user multiple frustrating round-trip requests later. The algorithm penalizes the weight, but the user experiences a fluid, uninterrupted journey. The score sees a number; the user feels a well-considered rhythm.
Lighthouse provides a map, a stunningly detailed one. But a map is not the territory. It is a representation, an abstraction built on rules and assumptions. Our job is not to blindly follow the map until we fall off the edge of the known world. Our job is to use the map to understand the territory—the messy, human, unpredictable reality of how people actually use our sites. The true north we should be navigating by is not a number in a report, but the quiet confidence of a person who found what they needed, without friction, without waiting, and without ever knowing we were there.
Chase the perfect experience, not the perfect score. Use the tool, but do not be used by it. The greatest performance optimization is one that serves a human purpose, not an algorithmic one.
Notes & further reading
A few pages I came back to while writing this: