Blog
A Drupal site at 15 on Google PageSpeed Mobile. Not 50. Not 40. Fifteen.
We took it to 95 in 8 hours. Here’s what actually happened — and why the same approach let us do it a third time in a single month.
Performance is the only score that’s genuinely hard. Accessibility, best practices, SEO — you can fix those with a checklist. Performance on a Drupal site requires real understanding of what’s slowing things down: render-blocking resources, unoptimized image pipelines, heavy module weight, misconfigured caching, missing preconnect hints.
Getting the diagnosis wrong doesn’t just waste time — it actively sends you in the wrong direction.
This is the gap AI closes.
Two websites. Same optimization task. Both on Drupal. Same traffic, same size. Same developer, same AI tools.
Site 1 — small company with full access:
Idea → test → see result → next idea. Loop time: 5–10 minutes.
AI generates hypotheses. We test them. Most fail. Some work. We keep going.
8 hours later: score went from 15 to 95 on mobile.
Site 2 — large corporation with approval chains:
Want to change something? That requires a security review, a compliance check, and sign-off from three departments. Testing one idea takes two weeks — if everything goes smoothly.
It’s been over a year. Same tools. Same AI. Same developer. The difference is purely speed of iteration.
100 tests in a day vs. 1 test in two weeks. That’s the entire story.
Here’s the actual workflow that got us to 95:
Step 1: Run the full Lighthouse audit, export the diagnostics.
Don’t fix anything yet. Read everything first. AI analyzes the full report and prioritizes by impact — not by how easy something is to fix.
Step 2: Render-blocking resources.
This is almost always the biggest hit on Drupal. Aggregation settings, CSS/JS asset loading order, and Google Fonts blocking the render path. AI identifies exactly which assets are blocking, suggests the load strategy change, and explains the risk of each change.
Step 3: Image pipeline.
Drupal has image styles. The problem is that most installations use them inconsistently — some images go through styles, some are uploaded raw and served full-size. We audited every image on the page, converted to WebP where missing, added loading="lazy" and explicit dimensions to stop Cumulative Layout Shift.
One image on a client site was 4.2MB. A single file. That was a large portion of the entire LCP problem on its own.
Step 4: Caching configuration.
Drupal’s caching is powerful but misconfigured by default on most production sites. AI walks through the cache layers — page cache, dynamic page cache, block cache — and identifies exactly which modules are bypassing cache without good reason.
Step 5: Third-party scripts.
Analytics, chat widgets, marketing pixels. Every one of them runs before your content loads unless you defer them properly. We moved everything non-critical to load after the main content renders.
Step 6: Iterate.
Score goes from 15 → 45 → 67 → 82 → 90 → 95. Each jump tells you something. AI reads the new report and recalibrates.
After the first result, we applied the same workflow to two more Drupal sites that month. Both crossed 90 on mobile.
91 on mobile. Third time that month.
The workflow is now documented. It’s replicable. What used to take days of trial-and-error now runs in a few hours because the diagnostic process is structured and the iteration loop is tight.
If your Drupal site is below 60 on PageSpeed Mobile, there are almost certainly 3–5 specific issues responsible for most of the gap. They are findable. They are fixable. The question is whether you have someone who knows where to look and how fast they can move.
A slow Drupal site is not a Drupal problem. It’s an optimization problem — and optimization is a process, not a one-time audit.
If your site scores below 60 on mobile, get in touch. We’ll run the diagnostic and tell you exactly what’s holding it back.
Related: What is an AI-native web studio · Drupal 7 to 11 AI migration
ilf.studio — web development and AI automation for growing businesses across Europe.