Drupal 11.3 performance jump: when an upgrade is stewardship, not a rewrite
The 11.3 release post describes cold-cache database and cache operations cut by roughly a third in core tests. Performance figures cite Drupal.org release messaging; your results will vary with hosting, caching, and custom code.
Upgrade as stewardship
| Rewrite narrative | Stewardship narrative |
|---|---|
| "We need a new platform" | "We need a supported core and compatible modules" |
| Big-bang migration | Phased core + module updates |
| Canvas as day-one promise | Theme readiness + component plan |
| Ignore technical debt | Inventory custom code and contrib |
Modernization partners should say what not to do: do not rebuild in Canvas before your theme and component library are ready; do not defer security-supported core because "we will migrate later."
Five questions before you schedule 11.3
- What core version are we on now, and is it security-supported?
- Which contrib modules block the jump, and is there a maintained alternative?
- Does our hosting stack (PHP, database, object cache) meet 11.3 requirements?
- Where is custom code tied to deprecated APIs?
- What is the rollback plan if staging shows regressions on critical journeys?
Honest answers beat a slide deck with benchmark screenshots alone.
When a rewrite might still be right
Sometimes technical debt, unsupported modules, or organizational change genuinely warrant a rebuild. Stewardship means making that call with evidence, not because a blog post said "26% more requests."
If 11.3 is the right next step, treat it as a release project: staging, automated tests where you have them, performance baselines on key URLs, and editor sign-off on critical templates.
How we help
We plan Drupal upgrades with module compatibility matrices, staging discipline, and performance checks on the templates that matter. No tribal "Drupal is dead" or "just use Canvas" shortcuts.
Talk to us about Drupal stewardship
Sources: Drupal 11.3.0 release: https://www.drupal.org/blog/drupal-11-3-0 · Drupal CMS 2.0: https://www.drupal.org/blog/drupal-cms-20-is-here-visual-building-ai-and-site-templates-transform-drupal