Museum sites that hold up through visitor surges

One review in the right paper can outdraw a year of steady visitors

The problem

Cultural traffic is spiky in a way a museum or gallery's usual daily numbers do not prepare a site for. A single favourable review, a school term starting or a piece of coverage travelling further than expected can send a surge of visitors to the site on almost no notice, and that surge lands at the exact moment a slow-loading page turns curiosity into a closed browser tab.

The usual answer

Institutions without dedicated infrastructure for this either accept the occasional outage as a cost of getting attention, which is a strange thing to be punished for, or over-provision permanently for a spike that might come once a year, carrying the cost of that capacity for the other three hundred and sixty days it goes unused.

How we approach it

We serve the public-facing pages from an architecture built for surges: content is cached and delivered close to the visitor rather than generated fresh for every request, so a jump in traffic is absorbed rather than fought. The parts of the site that genuinely need to be dynamic, like a ticket booking flow, are isolated so a spike in general browsing does not take down the ability to actually book.

What changes

The day an exhibition finds its audience is the day the site is fastest, not the day it falls over. Coverage translates into visits instead of a support ticket, and the institution does not pay for peak capacity on the days nobody is rushing to the site.