Insights & Resources
Performance

Drupal Performance: Why Sites Slow Down, What Fixes It, and How to Keep It Fast

Why Drupal sites slow down, the layers that keep them fast, what Drupal 11 changed, what a performance audit covers, and what to monitor, for the people who own the site and its budget.

10 min readNovember 18, 2026

Drupal performance: the load time Google rates as good is 2.5 seconds

A Drupal site stays fast when most visits never reach its servers, the pages that do are assembled from ready-made parts, and someone checks speed every week instead of waiting for complaints. When a Drupal site is slow, the cause is almost always on a short list: caching that is not doing its job, a database that has grown for years without upkeep, heavy images and third-party scripts, hosting sized for an ordinary day instead of the busiest one, or an outdated version of Drupal. Each of these can be fixed, and most cost less to fix than to live with.

We run Drupal for universities and government agencies, and performance is part of that work every week. This guide is for the people who own the site and its budget: why speed matters for a public institution, how it is measured, why Drupal sites slow down, what Drupal 11 changed, what a performance audit covers, and what to monitor so the site stays fast.

Drupal performance in one minute

  • Google measures speed with three Core Web Vitals: how fast the main content appears, how quickly the page responds to a click, and whether the layout jumps around.
  • Most slow Drupal sites share the same few causes, and caching is usually the first place to look.
  • Drupal 11.3 made Drupal itself much lighter, cutting database and cache work on pages built from scratch by about a third. Drupal 10 sites do not get these gains.
  • Performance is ongoing work. A one-time cleanup erodes with every release unless someone measures and guards it.

Why Drupal Performance Matters for a Public Institution

A slow website is easy to tolerate because it still works. For a university, an agency, or a nonprofit, the cost shows up in places that are harder to see:

  • Visitors leave. Applicants, residents, and donors compare your site with the commercial sites they use every day, often on a phone and on a weak connection. A page that takes eight seconds to show anything loses many of them before it finishes.
  • Search visibility suffers. Google recommends good Core Web Vitals "for success with Search" and says they align with what its ranking systems seek to reward. Relevant content still comes first, but between two relevant pages, the faster one has the edge.
  • Accessibility gets harder. Pages that load slowly or shift while someone is reading or tapping are hardest on people using assistive technology, older devices, or slow connections.
  • Hosting costs more. An inefficient site needs bigger servers to serve the same visitors, and the bill grows with traffic.
  • The busiest days are the riskiest. The days applications close, registration week, severe weather, elections, and public-comment periods bring traffic many times the usual level. A site that is merely slow on an ordinary day can fail on those days.

How Drupal Performance Is Measured

Google's Core Web Vitals are the common yardstick, and they are measured on real visits, not just in a lab test. A page passes when at least three out of four visits meet the "good" mark.

MeasureWhat it means for a visitorGoodPoor
Largest Contentful Paint (LCP)How long until the main content, such as the hero image or headline, appears2.5 seconds or lessMore than 4 seconds
Interaction to Next Paint (INP)How quickly the page responds to a click, tap, or key press200 milliseconds or lessMore than 500 milliseconds
Cumulative Layout Shift (CLS)Whether the page jumps around while it loads0.1 or less0.25 or more
Core Web Vitals thresholds, judged at the 75th percentile of real visits. Source: Google, web.dev, November 2026.

You can see your own numbers for free in Google's PageSpeed Insights and in the Core Web Vitals report in Search Console. Two more measures matter for Drupal specifically, and your hosting team should be able to give you both: how quickly the server answers when a page is not already cached, and how much of your traffic the content delivery network answers without touching your servers at all.

Why Drupal Sites Slow Down

These are the causes we find most often, roughly in order of how often they turn out to be the main problem.

  1. Caching is not doing its job. Drupal is designed to store finished pages and reuse them. When the content delivery network is missing, is not refreshed when content changes, or caches are stored in the database on a busy site, every visit costs far more than it should. Our Drupal caching guide explains the layers and the warning signs.
  2. Custom features switch caching off. One block that personalizes itself for every visitor, such as a greeting or a "recently viewed" list, can stop a whole page from being cached. This is the most common cause of a site that got slower after a release and never recovered.
  3. The database has grown without upkeep. Years of saved revisions, logs, and leftover data make every lookup slower. It happens gradually, so nobody notices until the site is struggling.
  4. Too many add-on modules. Sites collect modules over the years. Some are no longer used, and some add work to every page.
  5. Heavy images, video, and third-party scripts. Oversized hero images, autoplaying video, chat widgets, embedded maps, and marketing tags are often the biggest drag on Core Web Vitals, and none of it is Drupal's fault.
  6. Hosting sized for an ordinary day. The servers cope until the busiest week of the year, then slow down or fail when they are needed most.
  7. An outdated version of Drupal or PHP, the server software Drupal runs on. Newer releases are faster, and Drupal 11.3 is a large step on its own.

The Layers That Keep Drupal Fast

A fast Drupal site is a stack of layers, each taking work off the one behind it. The aim is for as few visits as possible to reach the slow, expensive layers at the back.

LayerWhat it doesSign it needs attention
Content delivery networkAnswers most public page views from locations near your visitors and absorbs traffic spikesBusy days slow the whole site; edits take a long time to appear
Drupal's page cachesStore complete pages for the public and reusable parts of pages for signed-in usersSigned-in staff and students see a much slower site than the public
In-memory cache storeKeeps cached items in a fast dedicated service instead of the databaseThe database is always the busiest part of the system
DatabaseHolds the content, settings, and history of the siteSlow searches, slow editing screens, and slow pages that are not cached
Web servers and PHPRun Drupal itself and build the pages that are not cachedSlow responses on uncached pages; an old Drupal or PHP version
Front endImages, styles, scripts, fonts, and third-party tags sent to the browserPoor Core Web Vitals even when the server responds quickly
The layers of a fast Drupal site, from the visitor inward.

The first three layers do the most for the least money, which is why a performance review starts there. The front end is where most Core Web Vitals problems surface, because it is what the visitor's browser actually has to download and draw.

What Drupal 11 Changed for Performance

Drupal's core team called Drupal 11.3, released in December 2025, the biggest performance boost in a decade. In Drupal's own performance tests, it cut database queries and cache operations by about a third on pages built from scratch, and cut database queries by almost half on a page that was partly cached. It also made the feature that streams personalized parts of a page much lighter, so less code has to load in the browser. The Drupal team expects every site to see significantly less database and cache work per visit after updating.

Three things follow for site owners:

  • The gains are only on Drupal 11.3 or later. Drupal 10 does not get them, and Drupal 10 reaches end of life on December 9, 2026. Moving to Drupal 11 now brings both security support and a faster site. Our Drupal upgrade guide covers what the move involves.
  • Drupal 11 needs newer server software. It requires PHP 8.3 or later, which is faster than the older versions many Drupal 10 sites still run.
  • Drupal now guards its own speed. Since Drupal 10.2, Drupal itself has included automated performance testing, so slowdowns are caught before a release ships. The same approach can be applied to your own site, so a new feature that would slow every page is caught before it goes live.

What a Drupal Performance Audit Covers

A good audit measures before it recommends anything, and ends with a short, ranked list instead of a long report. It should cover:

  • Real-visitor Core Web Vitals for your key page types: the home page, landing pages, news and events, search, and forms.
  • The content delivery network: how much traffic it answers, and whether it refreshes automatically when you publish.
  • Caching, including the experience of signed-in staff and students, and the custom features that switch it off.
  • The slowest pages, and the database work behind them.
  • Add-on modules: which are unused, outdated, or slow.
  • Images, scripts, and third-party tags, with the cost of each one.
  • Capacity: a load test at the traffic of your busiest day.
  • Versions: Drupal, PHP, and the database, against what is supported.

What you should get back is a prioritized list, with quick wins first and the expected effect of each item, plus baseline numbers so you can tell whether the work paid off.

What to Monitor, and When to Be Alerted

Most performance problems arrive quietly, with a release, a new tag, or a slowly growing database. Monitoring is what catches them early:

  • Core Web Vitals from real visitors, per key page type, reviewed as a weekly trend.
  • Uptime and server response time, with an alert when responses stay slow, not just when the site is down.
  • The share of traffic the content delivery network answers. A sudden drop means something changed in caching.
  • Database and server load, checked ahead of known busy periods so capacity is added before it is needed.
  • A performance check before each release, against agreed targets, so a slower page is a reason to hold the release.

Agree the targets in writing, for example "good" Core Web Vitals on every key page type, and make one named person or team responsible for them.

Seven Questions to Ask Your Team or Hosting Provider

  1. What are our Core Web Vitals from real visitors, and which pages fail?
  2. How much of our traffic does the content delivery network answer, and does it refresh automatically when we publish?
  3. Which versions of Drupal and PHP are we on, and when do we move to Drupal 11.3 or later?
  4. When was the site last tested at the traffic of our busiest day?
  5. Which add-on modules and third-party scripts could we remove?
  6. Who checks performance before each release, and against what targets?
  7. What is monitored, who is alerted, and how quickly do they respond?

If the answers are vague, an audit will usually find quick wins.

How eWay Runs Drupal Performance

Performance is part of every managed Drupal hosting engagement we run, not a separate project. That means a content delivery network that refreshes automatically when you publish, an in-memory cache store, database upkeep on a schedule, Drupal and PHP kept on current versions, a performance check before every release, real-visitor monitoring, and capacity planned ahead of known busy periods such as admissions, registration, elections, and budget season. It is the same ongoing ownership we describe in what is WebOps.

We do this for universities and for government agencies, with a monthly uptime SLA of up to 99.99% and around-the-clock response to severity-1 incidents. Comparing platforms? Our Drupal vs WordPress comparison covers performance alongside the other trade-offs.

Drupal site slow? Request a Drupal performance assessment. We measure your real-visitor Core Web Vitals, review every caching layer, your content delivery network, and your custom features, and give you a ranked list of what to fix first.

Frequently Asked Questions

How do I make my Drupal site faster?

Start with caching: put a content delivery network in front of the site, make sure it refreshes when content changes, and move Drupal's caches out of the database on a busy site. Then deal with heavy images and third-party scripts, clean up the database and unused modules, and move to Drupal 11.3 or later. Measure before and after, using real-visitor Core Web Vitals.

Why is my Drupal site slow?

The usual causes are caching that is missing or misconfigured, custom features that switch caching off for whole pages, a database that has grown without upkeep, heavy images and scripts, hosting sized for an ordinary day, or an outdated version of Drupal or PHP. A performance audit shows which one applies to your site.

What is a good page speed for a Drupal site?

Google rates a page as good when its main content appears within 2.5 seconds, it responds to a click within 200 milliseconds, and its layout does not jump around, for at least three out of four real visits. A well-run Drupal site can meet all three.

Is Drupal slower than WordPress?

Not when both are run properly. Drupal's caching is more precise and handles signed-in users better, which suits large sites with many editors and logged-in visitors. WordPress is simpler to cache for public pages. The bigger difference is how well the site is operated, not which platform it runs on.

Does upgrading to Drupal 11 improve performance?

Yes. Drupal 11.3 cut database and cache work on uncached pages by about a third in Drupal's own tests, and Drupal 11 runs on newer, faster versions of PHP. Drupal 10 does not receive these improvements and reaches end of life on December 9, 2026.

What does a Drupal performance audit include?

Real-visitor Core Web Vitals for your key pages, a review of the content delivery network and caching, the slowest pages and the database work behind them, add-on modules, images and third-party scripts, a load test at your busiest day's traffic, and a check of your Drupal and PHP versions. The result is a ranked list of fixes with baseline numbers.

Should performance be a one-time project or part of ongoing operations?

Both. An initial audit and cleanup establishes the baseline and captures the quick wins. Ongoing monitoring and a performance check before every release keep the gains, because each new feature, tag, and year of content can slowly undo them.

Ready to take ownership of your platform?

Stop managing vendors. Start operating a platform.

We assess your current environment, identify operational gaps, and outline what a managed engagement looks like for your organization.

No commitment requiredResponse within 1 business dayTrusted by 100+ institutionsWe will not spam your inbox