Performance Audits — Beyond the Lighthouse Score
Measuring perceived performance and editorial efficiency in heavy decoupled environments, where a green Lighthouse score can hide real problems.
Lighthouse is a proxy, not a goal
A 98 Lighthouse score on a staging page with 50ms RTT to the CDN is not the same thing as a fast site. The metric that matters is the one your users feel.
What I actually measure
p95 TTFB from the cheapest device on the slowest network your audience uses. Editorial publish-to-live latency. The time from "I know I need to fix this" to "the fix is visible to the customer".
The tools I use
WebPageTest, Blackfire, Drupal's own performance logger, and — more than anything — conversations with the editorial team about what actually slows them down day to day.
Read next
- May 25, 2026
Stop Making Users Pay for Work Your CI Pipeline Could Do
Most slow Drupal sites are not slow because the code is wrong. They are slow because expensive work runs at request time when it could have run in the CI pipeline instead. Cold caches, image derivatives, search indexes. The pattern repeats. The fix is the same in every case: move the cost off your users and onto a controlled environment where nobody is waiting. This is a principle, not a tip. Three examples below to make it concrete.
- May 15, 2026
Drupal Got Cache Invalidation Right. The Rest of the Industry Is Catching Up.
Drupal's cache tag system is one of the better-designed cache invalidation models in modern web frameworks. A practitioner's look at why it works, where it breaks across system boundaries, and the mental model that travels to any stack.
- May 11, 2026
Drupal's Queue API is the Most Underused Feature in Core
Most Drupal teams reach for cron, Batch API, or external job runners when Queue API would solve the problem with less code and fewer moving parts. Three patterns where Queue API earns its place, with snippets and architecture diagrams.