WordPress runs a large share of the business websites in Kuwait, and most of them are slower, heavier and harder to maintain than they need to be. Not because WordPress is weak — because of how they were built.
The usual story: a theme bought from a marketplace, a page builder installed to make it look right, thirty plugins added over three years to patch things the theme could not do, and nobody maintaining any of it. The site works, technically. It also takes six seconds to load on a phone, nobody on staff dares edit a page, and the only person who understands it left.
How I build WordPress differently
Custom themes, not marketplace themes with a builder on top
A purpose-built theme ships the markup your site actually needs. A marketplace theme ships the markup that 40,000 other sites might need, and a page builder adds several layers on top of that. That is where the weight comes from — and it is why builder sites are so hard to speed up afterwards. I build the theme around your content, so the HTML stays small and the site stays fast without a caching plugin doing damage control.
Fewer plugins, chosen deliberately
Every plugin is code you did not write, running on your server, with access to your database, updated on someone else’s schedule. Some are essential and excellent. Most sites are carrying several that duplicate each other or that solved a problem nobody remembers. I keep the count low and each one justified.
Your team has to be able to use it
A site the marketing person cannot update is a site that goes stale. Content should be editable in the standard WordPress editor, without a support ticket and without the risk of breaking the layout. That is a design decision made early, not a training problem solved later.
Arabic and English as a real structure
Bilingual WordPress done properly means correct right-to-left layout, an Arabic typeface chosen for screen reading, separate indexable URLs per language, and hreflang set correctly — not a translation plugin dropped on an English theme. It affects the theme, the URL structure and the SEO setup together.
What I work on
New WordPress websites
Corporate and business sites built from a custom theme, structured for search from the first page and fast on the connections your customers actually use.
Redesigns and replatforming
Moving off an ageing theme, a page builder or another platform — with every existing URL mapped and redirected so the search value you have already earned survives the move. This is the step most redesigns skip, and it is the expensive one to fix afterwards.
Speed and Core Web Vitals
Diagnosing what is actually slow — usually the theme and the plugin stack, not the hosting everyone blames — and fixing the cause rather than layering another caching plugin over it.
Security, maintenance and recovery
Hardening, updates, backups and a sensible maintenance rhythm. And if a site has already been hacked or is throwing errors after an update, cleaning it up and closing the hole that let it happen.
WooCommerce and payments
Stores planned around Kuwaiti checkout reality: KNET through a local provider, delivery and stock workflows that match how the business actually operates.
Custom functionality
Custom post types, fields and integrations when the business genuinely needs them — built as clean code rather than assembled from four overlapping plugins.
How a WordPress project actually runs
Most WordPress projects that go wrong were lost before anyone opened a design tool. The scope was never written down, nobody agreed what happens to the old URLs, and the question of who edits the site after launch was left until the week of launch. So the work runs in five phases, and the first two get more attention than clients usually expect.
The migration phase is where existing rankings are won or lost. Every URL that changes needs a one-to-one redirect, titles and meta descriptions have to survive the move, and no page should quietly disappear because it was missed in the content audit. I have seen more Kuwaiti sites lose traffic to a careless relaunch than to any competitor, and the damage is usually invisible for weeks — which is exactly why it goes unnoticed until it is expensive to fix.
Hand-over is treated as part of delivery rather than as an afterthought. You get the documentation, the access, the reasoning behind the decisions, and a site your own team can actually edit without calling anyone. If a project ends with the agency holding the keys, the arrangement was wrong.
What it costs to own, not just to build
The quote covers the build. It is the running cost that decides whether a site is still working two years later, and it is the part most proposals are quiet about.
Hosting and a CDN are monthly. Premium plugin and theme licences renew annually, and a stack assembled without discipline turns into a renewal bill nobody can justify — which is one of the reasons I keep the plugin count deliberately low. Updates and security are the line most businesses skip, right up until a neglected plugin lets someone in. And content, particularly Arabic content written rather than translated, is underestimated on essentially every project I have been called into.
I will give you an honest view of all of it before you commit, including the parts that argue against hiring me. If the running cost of a properly built WordPress site does not fit the business, it is better to know that at the start than to discover it when the licences come up for renewal.
Why WordPress sites get slow
Almost always the same handful of causes, in roughly this order: a page builder generating far more markup than the page needs; a dozen plugins each loading their own CSS and JavaScript on every page whether it is used or not; images uploaded at full camera resolution; a bloated marketplace theme carrying features you will never switch on; and hosting chosen on price alone. None of that is fixed by installing another plugin, which is the usual first attempt.
The fix is structural — fewer moving parts, server-rendered HTML, images sized properly, and caching configured with an understanding of what must not be cached. Speed is then measured against Core Web Vitals on a real phone on a mobile connection, not on a desktop in the office. The practical, step-by-step version of this is set out in my guide to optimising WordPress for Kuwaiti audiences.
Built to be found, in search and in AI answers
A site now has three readers: a person, a search engine, and an AI assistant summarising an answer on someone’s behalf. They want different things from the same page, and a build that only considers the first will quietly underperform. That means clean heading structure, questions answered plainly on the page, valid structured data following Google’s structured data documentation, and content that is genuinely useful in the sense described in Google’s helpful content guidance. The differences between optimising for search, for answers and for AI assistants are set out in my guide to SEO, AEO and GEO for Kuwait.
Arabic is where most bilingual Kuwaiti sites lose ground, and rarely because of the writing. It is separate indexable URLs for each language, correct hreflang, and a layout built with logical properties rather than right-to-left bolted on at the end — the detail is in the guide to Arabic UX in the GCC. On the security side, WordPress’s own security guidance is the baseline I build to, and the official documentation is worth more than most tutorial sites your team will find.
When WordPress is the wrong answer
It is not always the right platform, and I will tell you when it is not. If the product is the application logic, a custom build is usually cleaner. If you need a simple marketing site and have no one to maintain anything, a hosted platform may serve you better — I have written an honest assessment of where Webflow fits and where it does not. If the real question is which technology decisions the business should be making at all, that is a Fractional CTO conversation rather than a build one. WordPress earns its place when you publish regularly, care about search, and want to own your content and your data. That covers most businesses — but not all of them.
This site is the example
Almoosawi.com runs on a custom WordPress theme I built: no page builder, no bloat, server-rendered HTML, one stylesheet, and structured data and AI-visibility files generated from WordPress itself. If you want to know what I would build for you, you are looking at it. The wider web work — platform choice, migrations and the parts that are not WordPress — sits on the web consulting page.
Frequently asked questions
Do you build custom WordPress themes or use ready-made ones?
Custom. A ready-made theme carries markup and features for thousands of other businesses, which is where the weight, the page-builder dependency and most of the speed problems come from. A custom theme ships only what your site needs, which is why it stays fast and stays maintainable.
Can you fix a slow WordPress website?
Usually, yes — and usually the cause is not what people expect. Hosting takes the blame, but the culprit is more often the theme, a page builder, or a stack of plugins loading on every page. I diagnose the actual bottleneck first, then fix the cause rather than adding another caching plugin on top.
Will moving my site to a new WordPress theme hurt my Google rankings?
Only if it is done carelessly. Rankings attach to specific URLs, so the risk comes from changing or dropping URLs without one-to-one 301 redirects. Done properly — URLs preserved, redirects mapped, titles, metadata and structured data carried across — a rebuild should hold or improve your position.
Can you make a WordPress site work properly in Arabic and English?
Yes, and it is one of the areas where most Kuwaiti sites are weakest. Proper bilingual WordPress means real right-to-left layout, an Arabic typeface chosen for screen reading, separate indexable URLs per language and correct hreflang — not a translate plugin over an English theme.
My WordPress site was hacked. Can you help?
Yes. That means cleaning the infection, finding how it got in — almost always an outdated plugin, a nulled theme or a weak admin password — and closing that hole, then putting updates, backups and hardening in place so it does not happen again.
Do you offer ongoing WordPress maintenance?
Yes, as a monthly arrangement: updates applied and tested, backups verified, security monitored and performance checked. Unmaintained WordPress is the single most common reason business sites get compromised.