Skip to main content
Header Image
May, 2026

The Experience-Performance Paradox: Why Beautiful Museum Websites Are Failing Their Visitors

Josh Skelly
Josh Skelly
Chief Executive Officer

The best-designed museum website in our study scored just a 37 out of 100 on mobile. That was a common pattern we saw, not an exception.

When my team and our partners at Pantheon set out to benchmark 50 museum websites across visitor experience, performance, accessibility, and security, I expected the obvious story: well-funded museums do everything well, and the under-resourced ones struggle everywhere. That is not what the data showed, and the gap it exposed is now the central question in any serious museum digital strategy.

This discrepancy is a recurring theme. One of the top three institutions for experience registered a mobile performance (speed) score of only 22. Another museum, ranked in the top five, achieved an 81 for visitor experience while plummeting to 18 for desktop performance. I personally observed pages that were rated as excellent by nearly every design standard we applied that still took 8+ seconds to load according to our testing.

What we found is, in my opinion, the most important line in the entire report: visitor experience quality and technical health don't correlate.

We call this the "experience-performance paradox," and it represents the primary digital challenge for cultural institutions today.

What is the experience-performance paradox?

The core of the paradox lies in the discovery that a museum website’s user experience and aesthetic appeal has no statistical connection to its operational performance. Our study revealed that sites that were easy to use and visually stunning frequently struggled with security, accessibility, and load speed, while technically robust sites often lacked a memorable user experience. Accessibility sits in both camps, since a site that excludes users is both a technical failure and a UX one.

To a visitor, however, these distinctions are irrelevant; a beautifully designed page is ultimately a failure if it takes too long to load.

The data illustrates a sharp contrast: while visitor experience scores remained relatively consistent around a 67.1 average, technical performance fluctuated wildly. Mobile performance scores ranged from 16 to 91, and security ratings varied from 20 to 95, with no clear link to an institution’s budget or size. In fact, some of the most prestigious museums in our study recorded the lowest technical scores in the entire dataset.

What does the paradox actually reveal?

A zero correlation is far from just noise. It reveals a fundamental disconnect: the teams crafting the visual experience and those managing technical operations are effectively speaking different languages.

When marketing and IT operate in silos or report through divergent leadership chains, the results are predictable. We observed museums building sophisticated visitor journeys while technical foundations like security headers, page speed, and accessibility remained neglected. Conversely, some high-performing technical sites lacked any engaging user experience. This "experience-performance paradox" is the measurable byproduct of decentralized governance.

The practical implications of this divide are significant:

  • Security risks: Seven out of the 50 institutions surveyed utilize CMS versions with known critical vulnerabilities documented since 2021. This jeopardizes sensitive data, including member financial records and donor payment details.
  • Accessibility gaps: A mere three sites were free of accessibility violations on the homepage. With an average of 4.1 violations per site homepage, even visually impressive designs often masked user experiences and development that excludes users.
  • Revenue neglect: Critical conversion points underperformed, with ticketing pages averaging an experience score of 57.2, significantly lower than the 77.8 average for homepages, suggesting investment is prioritized for first impressions over actual transactions.

While a homepage launch is celebrated with fanfare, a critical security patch is often relegated to an obscure technical report. Although only the former may be visible to a board of directors, both are equally apparent to visitors, donors, and those looking for system vulnerabilities.

Why does treating the website as separate portals fail visitors?

Because nobody visiting your museum experiences it as a collection of departments. They experience it as one thing. This is an issue we see throughout many industries—websites that are designed around internal department structures, rather than how the customer, member or website visitor wants to and should experience it.

A family deciding between your museum and a movie has no idea that ticketing lives with a vendor, the collections database belongs to curators or the registrar's office, and the events calendar is owned by marketing. They don't know any of that, and they shouldn't have to. What they know is that the site was slow, the checkout was confusing, and they couldn't find out what was happening this weekend. Most museums are still running their websites as a set of independent software portals rather than one cohesive visitor journey, and our data says that's costing them visitors who never even get the chance to complain about it.

How should museum leaders actually respond?

This is a governance problem in addition to a technical one, so the fix has to start at the leadership level, not in a sprint backlog.

  1. Give the web product a single owner. Someone in your organization needs to be accountable for the website KPIs, how the site looks and how it performs. If you can't name that person right now, you've just found the root cause.
  2. Put technical health on the same dashboard as design. Mobile performance, accessibility violations, and security scores belong in the same leadership review as brand and content metrics.
  3. Align the teams, not just the tools. The opportunity here is organizational in addition to technological. The museums at the top of our benchmark weren't the richest ones. They were the ones where marketing, design, and engineering functioned as one product team rather than three.
  4. Audit before you redesign. If a redesign is on your roadmap, benchmark your technical health first. We walk through a practical version of that audit, including the questions worth asking before you sign a statement of work, in our piece on the hidden costs of "good enough" museum websites. Skip that step and you'll likely ship a better-looking version of the same broken foundation.
  5. Look at what unified ownership actually produces. The National WWI Museum and Memorial's redesign is a good reference point. Performance and accessibility were treated as requirements from day one because one team owned the whole outcome.

Which side of the paradox is your institution on?

We can tell you. We build a custom scorecard covering experience quality, performance, accessibility, and security, benchmarked against the full 50-institution dataset, with a prioritized action plan. Request your custom scorecard or contact us to talk through your digital strategy.

The complete findings, including page-type scoring across 54 criteria, performance tiers for all 50 institutions, and our full methodology, are available in the State of Museum Digital: 2026 Benchmark.