6 posts tagged with "Performance"

Pantheon has been expanding Site Metrics and dashboard visibility through a series of updates published on February 4, 2026, February 23, 2026, and earlier dashboard modernization work from May 5, 2025. The feature set is genuinely useful, but only if teams stop treating "traffic" as one bucket.

For Drupal and WordPress operators, Pantheon Site Metrics changes one thing more than anything else: it makes it easier to separate performance problems, ownership problems, and noise problems before they become incident calls.

The hospitality sector thrives on speed. If a booking portal takes more than three seconds to load, hotel chains lose hundreds of thousands of dollars in abandoned reservations.

When a global financial institution processes thousands of multi-lingual regulatory reports, public development indicators, and economic whitepapers daily, the search experience cannot be purely functional—it must be instantaneous and exact.

One missing cache tag can quietly force expensive rebuilds on every request. A February 2026 report described exactly that pattern behind a 4.2-second Drupal product page.

I built a reproducible Next.js rebuild benchmark to answer one question quickly: which build profile is fastest, and did we just introduce a regression? It targets next@16.1.6, runs cold and warm cache scenarios, and produces JSON you can diff in CI.

Teams notice build regressions late. This tool makes them visible immediately.

Caching is usually the answer to everything in Drupal performance, but there is a crossover point where the overhead of the cache itself -- retrieval and unserialization -- outweighs the cost of just doing the work.