WordPress & PHP developer / Server support — Giza, Egypt
I build WordPress sites and keep the servers under them running. Speed, uptime, stability.
Custom themes and WooCommerce builds in the front, PHP, MySQL and hosting configuration in the back — usually all three on the same project. When a production site goes down, I am the person who finds out why.
The projects worth writing up — what the brief was, what I built, and what it runs on.
P1Oct 2025 — Jan 2026Travel & hospitality
New Belquis Tours
A production travel booking platform on WordPress, with the booking, pricing and payment logic written as custom plugins rather than assembled from off-the-shelf parts.
Developed custom plugins to extend core functionality.
Implemented Paymob payment integration via a custom shortcode-based plugin.
Created a custom currency switcher plugin for multi-currency pricing.
Designed and managed custom database tables for booking and pricing logic.
A corporate site with nobody else on it. I provisioned the server, pointed the domain, installed WordPress, designed the layout and the logo, built the pages, and handed over a site that was already fast and already stable — one person from the empty server to the live URL.
Started at the server: provisioned it, configured the domain and DNS, installed WordPress clean rather than on a migrated mess
Designed the UI/UX layout myself, plus the logo and the rest of the branding — there was no designer on the project
Built every page in Elementor, then went back over it for weight and render order instead of shipping the default build
Ran the client relationship directly: brief, review rounds, revisions and handover, with no account manager in between
Tested across real devices before launch — the responsive behaviour was checked, not assumed
A high-traffic Arabic news site on shared hosting that was going down two or three times a day and taking over a minute to draw its own homepage. It turned out to be three separate problems wearing one costume: no real caching, a database that had been left to bloat for years, and a backdoor somebody else had already walked through. I took them in that order.
Measured first: 62.9s to generate the homepage, 291 database queries per load, no persistent object cache, and repeated 503s from the host's resource limiter
Found the outage pattern was not traffic but a cache TTL conflict — the CDN and the page cache expiring together and sending every visitor to PHP at once
Found wp_postmeta had grown to 3.7 million rows, with MySQL reading from disk on every request and load averages touching 190
Found live backdoors (sso.php, csoold.php) and SEO spam injected into wp-config.php pointing at an external link farm — cleaned the files and closed the way back in, which is the half that matters
Installed a real caching layer and a persistent object cache, then set the CDN to a long edge TTL with stale-while-revalidate so an expiry never becomes a stampede again
Moved WP-Cron off page loads onto a real system cron, raised the memory ceilings, and locked down XMLRPC and the login with challenge rules and rate limiting
Fixed the PHP notices the theme had been throwing on every request, and wrote the client a plain-language summary of what happened and what stops it recurring
A site is only finished when it stays up. This is the work that happens after launch.
01
Monitoring
Uptime and SSL checks on every production site, with alerts that reach me before the client notices.
02
Backups
Scheduled off-server backups, and a restore I have actually tested.
03
Hardening
File permissions, login protection, and closing the entry points that malware uses.
04
Reporting
A monthly summary of what was updated, what broke, and what I changed.
S5 — Results
What actually changed
Measured before I touched anything, and again after. Taken from rescue jobs on sites that were already in trouble.
Daily outages
Before
2–3 a day
After
None
A news platform on shared hosting was going down two or three times every day. It turned out to be the page cache and the CDN expiring together and sending every visitor straight to PHP at once — not traffic volume.
Object cache
Before
None
After
Persistent
The homepage was taking 62.9 seconds to generate and running 291 database queries per load, with nothing caching the result of any of them.
Live backdoors
Before
2 found
After
Closed
Someone had already been in. Cleaning the files is the easy half — closing the way back in is the job.
WP-Cron
Before
Every page load
After
System cron
Moved off the visitor request onto a real schedule, so a busy hour stops making the site slower for the people causing it.
CDN edge TTL
Before
Expiring together
After
12h, serve stale
Stale-while-revalidate, so an expiry refreshes in the background instead of turning into a stampede.
S6 — FAQ
Before you ask
Do you work with agencies as a subcontractor?
Yes. I have done white-label builds and post-sale customization for agencies and template sellers, and I am comfortable working inside an existing process, repo or design handoff.
Can you take over a site someone else built?
Regularly. Most of my maintenance work starts that way — I audit the install, document what is there, clean up conflicts, then take over updates and monitoring.
Do you handle hosting and migrations too?
Yes, over terminal rather than plugins where possible. Server setup, DNS, SSL, mail and the actual move are all part of the job I do day to day.
What happens in an emergency — malware or downtime?
Message me on WhatsApp. First step is getting the site back up and closing the entry point, then a written summary of what happened and what stops it recurring.
Are you open to full-time roles?
Yes, alongside freelance and subcontract work. I have worked both in-house and remotely, and I am used to reporting into a team.