Drupal performance
Slow Drupal sites are almost always solvable. We audit real user metrics, fix the slow parts, and set up monitoring so performance stays fixed after we leave. Common wins live in cache configuration, image handling, database queries, and front-end asset delivery.
How we approach it
Real users over synthetic tests
Field data from real visitors drives our priorities. Not just Lighthouse in a Chrome tab.
Cache correctly, not aggressively
Aggressive caching hides bugs. Correct cache tags and contexts keep pages fast and content fresh.
Database first
Slow Drupal pages are usually slow queries. We profile the actual SQL, add indexes, and cache the right layer.
Monitoring is part of the deliverable
We hand off dashboards that flag regressions before your users do.
What's included
- Core Web Vitals audit (real user + lab data)
- Drupal cache configuration (page cache, dynamic page cache, Redis)
- BigPipe and lazy-loading
- Query profiling and database index review
- Image optimization and responsive image handling
- Asset delivery (aggregation, HTTP/2, CDN configuration)
- Third-party script audit
- Monitoring setup (Grafana, New Relic, or your existing stack)
Who it's for
Sites that were fast at launch and slowed down
Content grew, modules accumulated, or the site outgrew its cache configuration.
High-traffic events and campaigns
Membership drives, campaign launches, media moments where response time matters.
Sites failing Core Web Vitals
LCP, INP, and CLS scores that need to move for SEO and user experience.
What it costs
A focused performance audit + fix engagement is typically $15K to $40K. Ongoing performance work is included in monthly support retainers.
Common questions
How much faster can you make our site?
Depends on where we start. Most engagements land in the 40 to 80 percent LCP improvement range. We will set expectations after the audit.
Do we need a CDN?
Usually yes. Cloudflare, Fastly, or a Pantheon-native CDN. We recommend based on your traffic patterns and origin location.
Will performance work break other things?
We build against a staging environment first, test against your real content model, and roll out behind a feature-flagged deploy pipeline.
Ready to talk through it?
Book a free discovery call. We'll talk through what you need, what we'd recommend, and whether we're the right fit.