Open a new browser tab and go to pagespeed.web.dev. Type in your website address. Wait thirty seconds. If you see red or orange, this article is for you.
Steady Drupal now has an organisation profile on Drupal.org, the official home of the Drupal project.
A prospective client asked me this recently, almost apologetically. They'd collected three quotes for moving their mid-size site off Drupal 7. Two agencies came in between $12,000 and $15,000.
It's a blunt question, and it deserves a straight answer: yes — but fewer sites than a decade ago, and the ones that remain are a very particular kind of site.
Yes. Let's just say it plainly, because too many comparison articles hedge on this. For a beginner setting up their first website, Drupal is harder than WordPress — noticeably so.
Tesla.com — one of the highest-traffic, highest-profile brand websites on the internet — runs on Drupal.
Ask anyone who's run a Drupal major version upgrade what actually ate the calendar, and it's rarely core itself.
If you've been told that moving your website from Drupal 7 to the current version is more complicated than a normal update, that's true — and it's worth understanding why before you start the project.
If your website runs on Drupal 7, here's the short version: that version of the software stopped being supported in January 2025. No more security fixes, no more safety net.
Drupal 7 first came out in 2011, and it did its job for a remarkably long time — right up until it stopped being supported in January 2025.
"Updating Drupal core" sounds like a small task, and for a patch release, it usually is. But it's also the step where a rushed process can take a production site down for an afternoon.
If you've ever started a Drupal major version upgrade only to get blindsided by a pile of deprecated code halfway through, the Upgrade Status module is the tool that's supposed to stop that from happening.