WordPress is not the problem. What people do to it is
WordPress runs a large share of the web because it is genuinely good at what it does. Most of the complaints about it — slow, insecure, impossible to edit — are complaints about a specific build: forty plugins nobody audited, a page builder generating megabytes of markup for a paragraph of text, and a theme bought once and never updated.
Built properly, it is fast, stable and cheap to run for years.
How I build
Custom themes, no page builders
The layout is code, not a stack of nested drag-and-drop containers. Pages load in a fraction of the weight, the design stays consistent because it cannot be casually broken, and there is no licence to renew for the privilege of editing your own site.
Plugins as a last resort
Every plugin is someone else’s code with access to your database and a maintenance schedule you do not control. Each one has to earn its place. Fewer plugins is the single biggest difference between a WordPress site that ages well and one that does not.
Editing your team can handle
Content fields that make sense to whoever updates the site, so changing a headline does not require a developer or courage.
Rescue work
A large part of what I do is inherited sites. Typically: the original developer is gone, nobody has the login to something important, updates have been avoided for two years because someone broke the site once, and there is no backup anyone has tested restoring.
That starts with an audit — what is installed, what is out of date, what is already compromised — then a safe path forward. Sometimes that is a repair. Sometimes it is honestly cheaper to rebuild.
Speed, security and the boring parts
- Core Web Vitals measured on real devices on a real connection, not a lab score
- Images served in modern formats at the size they are actually displayed
- Caching set up to match how the site is used rather than switched on and forgotten
- Login hardening, because the front door is where almost every WordPress compromise starts
- Backups that are tested by restoring them, which is the only test that counts
Arabic and English on one install
Bilingual WordPress is a solved problem when it is set up at the beginning and a painful one when it is retrofitted. One install, both languages, correct right-to-left rendering, and hreflang that tells search engines the two versions are the same page rather than duplicates competing with each other.
Maintenance
Updates applied and checked, not applied and hoped for. Monthly, on a staging copy first, with a note of what changed. A site nobody maintains is not saving money — it is deferring a much larger bill.
Related reading
Arabic-second always shows goes through the bilingual details that a WordPress build either gets right at the start or pays for later.