Earlier this year, my team at Urban Insight partnered with Pantheon to evaluate 50 cultural institution websites across the United States. We scored each one on visitor experience, performance, accessibility, and security. Of everything we found, one number has stayed with me.
40.6 out of 100. That's the average mobile performance score across all 50 museums.
To put that in context: more than a third of the museums we tested scored below 30 on mobile, the range where pages routinely take ten or more seconds to load and visitors simply give up. Desktop performance averaged 57.8, a full 17 points higher (which is still a poor score for desktop speed). The gap between the two isn't an inevitability though. It's a choice made by the technical architecture of the site, from the plugins to the tracking to every platform decision made when the site is built and maintained.
What is a good mobile performance score for a museum website?
A museum website should target a mobile PageSpeed score of 70 or higher. In our 2026 benchmark of 50 cultural institutions, the average was just 40.6, and the best performer reached 91, proving strong mobile performance is achievable. Below 30, load times can stretch past ten seconds, and most visitors abandon the page before it finishes loading.
The range we measured ran from 16 to 91, a fivefold difference between the worst and best sites. Notably, it didn't correlate with institutional size or budget. Some of the most prominent museums in our sample posted some of the worst scores.
Why does mobile performance matter so much for museums?
Because for a museum, the mobile visitor is often standing in your lobby.
This is the part most performance conversations miss. Slow mobile sites are usually framed as an e-commerce problem, a lost online ticket sale, but for museums it's also an on-site wayfinding issue. Visitors pull out their phones to buy tickets and skip the line, to load an exhibition page while standing in a gallery, or to check what's happening at the museum that afternoon. When the page takes 12 seconds to load on lobby Wi-Fi, the website is actively degrading the in-person experience your institution has invested millions to create.
And the numbers get worse exactly where the stakes are highest. Across our sample, ticketing pages averaged a mobile performance score of 38.6, lower than the overall average, with several sites scoring below 15. These are visitors who already decided to buy, and losing them at checkout because the page won't load is a conversion failure that happens before any design decision gets a chance to matter. If you need to translate that into budget terms for your board, our free museum website ROI calculator models exactly how much friction at the point of purchase costs an institution each year.
What causes poor mobile performance on museum websites?
Two culprits showed up consistently across the 50 sites we analyzed.
JavaScript bloat. Analytics stacks, marketing pixels, chat widgets, and third-party embeds each add JavaScript that must execute before the page responds to a tap. We measured this through Total Blocking Time, and the pattern was clear: every added script carries a performance cost, and most museums aren't measuring that cost at all.
Technology stack complexity. Museums running 25 or more detected technologies consistently underperformed on mobile compared to institutions running leaner stacks. The lesson isn't that technology is bad. It's that every addition needs the tradeoffs thought through, and someone in the organization needs to own that.
On ticketing pages specifically, a third factor compounds everything: third-party platform dependency. Ticketing systems built for enterprise CRM and donor management were never designed for mobile-first visitor conversion, and the off-the-shelf ticketing modules they ship with typically perform poorly as a result. The few museums that score well on ticketing performance have invested in configuring those platforms around the visitor experience, not the back office.
How can museums fix slow mobile websites?
Here's where I'd start, based on what actually moved the needle across the 50 sites we looked at:
- Audit your script load. Go through every analytics tag, pixel, and widget on your main pages. Most museums find at least one tool nobody's touched in years. Cut what you can't justify keeping.
- Measure ticketing and visit pages, not just the homepage. In our benchmark, homepages averaged 77.8 on experience quality while ticketing came in at 57.2. Test where the money actually moves.
- Treat your ticketing platform as a UX decision, not just an ops one. When we folded The Broad's ticketing flow directly into their website and dropped the third-party redirects, checkout fell to 44% fewer steps.
- Reconsider your architecture before your next redesign, not after. A lot of mobile performance problems trace back to platform decisions made years ago, often by people who've since left the organization.
- Put performance on someone's job description. Every site in our sample that performed well had one person accountable for it. Every site that didn't, didn't. The National WWI Museum and Memorial's redesign is a good model here: mobile performance and accessibility were requirements from day one, not a punch list after launch.
Where does your museum stand?
Our full benchmark report breaks down mobile and desktop performance, experience quality across seven page types, accessibility, and security for the 50-institution sample. You can explore the complete 2026 museum digital benchmark here.
If you want to know your own numbers, we'll run your site through the same methodology: a detailed UX review, security check, and PageSpeed scores for your homepage, ticketing, and collections pages, benchmarked against the full dataset, with a prioritized action plan. Request your custom scorecard or contact us to talk through your digital strategy.
