At 40Q, we think about WordPress differently than most agencies.
We do not treat it as a fragile CMS that needs to be tiptoed around. We treat it like a serious application platform.
That means we care deeply about infrastructure, deployment workflows, maintainability, and how fast a team can move without creating problems six months later.
That is the real reason we moved our website to Kinsta.
And after the move, one result stood out immediately: our PageSpeed score improved by around 20 points without changing the codebase or database. We simply migrated the site.
That performance gain was great, but it was not the only reason we moved. The bigger reason is that Kinsta makes life easier for developers, and when the developer experience is better, clients benefit too.
Infrastructure that supports modern WordPress development
A lot of WordPress hosting still assumes an older way of working. It assumes developers will make small changes directly in the theme, rely on ad hoc workflows, use drag-and-drop builders, and contact support whenever they need to do anything beyond the basics.
That is not how we work at 40Q.
Our workflow is built around modern tooling, structured environments, and development practices that reduce risks.
Hosting is not just “where the website lives.” Hosting either supports a professional workflow or gets in the way of it.
Kinsta supported the way we already like to build.
The Roots ecosystem
At 40Q, we are deeply invested in Roots tools because they bring more structure and consistency to WordPress development.
One of their tools, Bedrock, gives us a modern, Composer-based project structure. Another one, Sage, gives us a component-driven frontend workflow.
For non-technical readers, here is why that matters.
Bedrock helps make WordPress projects cleaner and more reliable
Most people never see the internal structure of a website, but that structure has a huge effect on long-term quality.
Bedrock gives us a cleaner foundation for WordPress projects. Instead of treating a site as just web pages on a server, it helps us organize dependencies and configuration with more discipline.
For clients, that translates into a few practical benefits:
- Updates are easier to manage
- Environments are more consistent
- There is less room for “it works on one server but not on another”
- Onboarding new developers is faster
- Long-term maintenance becomes less risky
Bedrock helps us run WordPress projects in a more professional, predictable way.
Sage helps us build better frontends, faster
Sage matters for a different reason. It improves how we build the theme itself.
One of the things we love about Sage is that it lets us use Laravel Blade inside WordPress.
For non-technical people, the benefit is not “Blade” as a buzzword. The benefit is what enables:
- Cleaner templates
- More reusable components
- More consistency across the site
- Easier collaboration across developers
- Faster iteration without creating a mess
That leads to websites that are easier to improve over time. And that matters to clients because websites are never really “done.” The real test is whether a site can evolve without becoming fragile or expensive to maintain.
Kinsta supports our workflow without friction
One of the reasons the move made sense is simple: Kinsta does not fight this way of working.
Some platforms make you feel like you are constantly negotiating with the hosting provider. You want to use modern tooling, and suddenly you’re having to figure out workarounds, opening support tickets, or changing your process to match the platform’s limitations.
Kinsta felt different.
We could use the tools and conventions we already believe in. We could work in a way that feels natural to a modern engineering team.
We like doing things ourselves
This may sound like a small point, but it is one of the most important ones.
We are power users. We do not want to be blocked by basic operational tasks. We do not want to wait on support for things that a capable team should be able to handle on its own.
A good hosting platform gives advanced teams room to operate.
That does not mean support is unimportant. It means the best support experience is often not needing support at all for day-to-day tasks. Kinsta gives us a dashboard that is actually useful, and enough access that our team can move quickly.
That speed is not just convenient for us. It is good for clients, too.
When an agency can diagnose issues faster, deploy with more confidence, manage environments cleanly, and avoid unnecessary back-and-forth, clients get a smoother experience. Less delay. Less friction. Less operational drama.
A tool we rely on: Kinsta’s APM
Kinsta ships with a built-in Application Performance Monitoring tool, and at some point during our time on the platform, it earned its place.
We had a performance issue that was genuinely hard to pin down.
The kind of thing that does not show up obviously in PageSpeed scores or error logs, an underlying process quietly doing damage.
Kinsta’s APM made it immediately visible. We could see exactly where the bottleneck was, fix it directly, and in some specific cases recover up to two seconds in load time as a result.
Having this tool built into the platform, without needing a third-party integration or a support ticket just to get visibility, is exactly the kind of thing we mean when we say Kinsta supports the way a capable team likes to work.
Better developer experience leads to better client outcomes
This is the part many non-technical buyers miss.
Developer experience is not just about making engineers happy. It affects the quality of the final product.
When developers work in a cleaner environment, they make better decisions. They ship more predictably. They spend less time fighting infrastructure and more time improving the actual website.
That means clients get better performance, fewer avoidable issues, more stable releases, easier future improvements, and a more maintainable site over time.
That is one reason we care so much about tools like Bedrock and Sage, and why it matters that Kinsta supports that kind of setup.
And when the foundation is right, everything built on top of it gets better.
Maximo Martínez Soria is the CTO of 40Q, an enterprise WordPress agency. With over 10 years of experience in web development, he is passionate about crafting high-performance digital experiences for enterprise clients.
