WordPress runs a large share of the web and is genuinely good at publishing articles. We build custom themes on it with a deliberately short plugin list, because plugin weight is the reason most WordPress sites end up slow.
What is WordPress?
WordPress is a PHP content management system with an enormous plugin ecosystem. Its strengths are real: the editing interface is familiar to millions of people, almost any feature exists as a plugin, and hiring someone who can maintain it is easy anywhere including Dubai.
Its weakness is the same ecosystem. Every plugin brings its own CSS, JavaScript and database queries, and a site with twenty of them is loading twenty authors' idea of what a page needs. That is where the speed goes.
Used deliberately — a custom theme, a handful of plugins chosen on purpose — WordPress is a perfectly good platform. Used as a bag of plugins, it becomes the site we get called in to rescue.
When we choose WordPress
When the site is content-led and the client's team already uses WordPress. Retraining people on a new interface has a cost, and if the current one works there is often no reason to pay it.
When the budget is genuinely small. A well-built WordPress site costs less than a custom build and gets a business online properly, and pretending otherwise to sell a bigger project is not advice.
And when we are asked to fix an existing WordPress site rather than replace it — which is most of our WordPress work.
It is also frequently the honest recommendation on a limited budget. A well-built WordPress site with a custom theme and a short plugin list does most of what a small business needs, and spending three times as much to gain control they will not use is not advice worth paying for.
When we do not use WordPress
When the site needs to be an application — bookings that cannot collide, permissions per user, calculations finance will audit. Bending WordPress into that means five plugins each updating on their own schedule, and that is where the maintenance cost appears.
When the site must be properly bilingual. Multilingual WordPress is possible and it is nobody's favourite part of the platform; a custom build handles Arabic considerably better.
And when Core Web Vitals are a hard requirement and the existing plugin set has made them unreachable without a rebuild.
What we build with WordPress
Custom themes, not page builders
A theme built to your design with the fields your content actually has. Page builders produce markup nobody can optimise later and are the most common reason a WordPress site cannot be made fast.
Speed and security rescues
Taking a slow, out-of-date site and getting it green again: auditing plugins, removing what is unused, fixing images, updating everything that has been left behind. Usually two to three weeks and far cheaper than a rebuild.
Content sites built for search
Structured data, clean internal linking, fast templates and an editor workflow the marketing team can actually use without asking a developer to publish an article.
Migrations off a page builder
Moving content out of Elementor or Divi into a proper theme, which is usually the only way to make a site of that kind fast. Content is preserved; the markup is rebuilt underneath it.
How we ship WordPress projects
With a written plugin list and a reason next to each one. Anything without a reason does not go on.
Updates and backups configured before launch, not discussed after an incident. An unmaintained WordPress site is the most commonly compromised thing on the web, and that is a maintenance question rather than a platform flaw.
With images handled at upload rather than left to a plugin. A 5MB photo from a phone becomes properly sized WebP automatically, because the alternative is a site that is fast at launch and slow within a year as the media library fills with originals nobody resized.
What WordPress costs you
Security requires attention. The platform is a large target and vulnerabilities are usually in plugins rather than core, which means an unattended site accumulates risk quietly.
Performance also has a ceiling. A well-built WordPress site is fast; it is rarely as fast as a server-rendered custom build, because there is more machinery between the request and the HTML.
The other honest cost is that WordPress accumulates. Every plugin added over five years is one somebody has to keep updated, and the person who added it has usually left. Budget for a review once a year rather than treating the site as finished at launch.
WordPress questions we get asked
Usually, yes. Most slow WordPress sites are slow for three reasons: too many plugins, unoptimised images and a page builder. The first two are fixable in two to three weeks. If it is the third, we will tell you honestly whether a rebuild is the better use of the money.
Fewer plugins, updates applied on a schedule rather than when something breaks, tested backups, and locked-down admin access. Almost every compromised WordPress site we are called to had an out-of-date plugin nobody was watching.
It can be made bilingual, and it is nobody's favourite part of the platform. Arabic RTL through a plugin usually means fighting a theme designed left-to-right. If Arabic is a first-class requirement, we will usually recommend a custom build instead.
Yes — content lives in the database and the theme only controls presentation, so a rebuild replaces the templates underneath your existing posts and pages. The exception is a page builder, where the layout is stored inside the content itself and the migration is genuinely more work. We check which situation you are in before quoting.
Website development starts at $8,000 and typically runs four to ten weeks. A custom theme with a short plugin list sits near the lower end; a bilingual site with custom post types and integrations sits higher. A speed and security rescue on an existing site is usually two to three weeks and considerably less.