Skip to main content [Tab]
AM
Asib Mahmud
←Back to Project Index
Editorial Feature/WordPress
02
Archival Record
●[CLIENT: Independent Culture & News Publication]

●[PROJECT NAME: High-Performance Editorial CMS & Headless Publisher]

Rebuilding a bloated 80-plugin WordPress monolith into a clean, sub-second publishing engine that handles viral traffic spikes without breaking.

RoleLead Full-Stack Web & WordPress Engineer
Year & Duration2024 • ●[6 WEEKS]
Team Structure●[SOLO ENGINEER COLLABORATING WITH DESIGNER & MANAGING EDITOR]
Focus DisciplineWordPress
Core Stack
WordPress (Custom Theme & Block API)PHP 8.3Tailwind CSSRedis Object CacheCloudflareDocker
// Plain-English Summary for Stakeholders

A media brand was losing readers because their site took seven seconds to load on phones. I stripped out dozens of conflicting plugins, built a bespoke theme using native WordPress blocks, configured caching at the edge, and made reading enjoyable again.

Phase 01 • The Problem

The client ran a decade-old WordPress installation that had accumulated 64 active plugins.

Every article page rendered 1.4 MB of unused JavaScript and triggered over 110 unindexed SQL queries. Whenever an article was featured on social platforms, database CPU spiked to 100% and readers were met with 504 Gateway Timeout errors.

The editorial team also dreaded writing articles because the bloated visual page builder took 15 seconds just to load an edit draft.

“A publishing site's entire reason for existing is to get words onto a human being's screen without friction.”
— Project Retrospective Note
Phase 02 • Interactive Verification & Numbers
Quantitative Performance Profile
Audit Mode:
PageSpeed Mobile Score
●[98]/100

Up from 34/100 on the prior commercial theme

Largest Contentful Paint
●[1.1]s

Cold cache mobile test over 4G simulated connection

Database Queries per Request
●[16]queries

Down from 114 queries on the old plugin stack

Hosting Bill Reduction
●[45]%

Migrated away from bloated oversized server instances

Google Lighthouse Audit Scores (Mobile • Simulated 4G)
performance98 / 100
accessibility100 / 100
bestPractices100 / 100
seo100 / 100
Phase 03 • Engineering Decisions & Tradeoffs

Architectural choices and what was explicitly rejected.

Bespoke Gutenberg Blocks instead of Heavy Page Builders

Replaced Elementor with 9 lean, semantic WordPress Block components written with native Block APIs and vanilla markup. Editors retained drag-and-drop flexibility without emitting 400 nested <div> elements per paragraph.

Alternative Rejected

Rejected keeping the page builder with aggressive caching wrappers (caching doesn't fix terrible DOM depth).

Edge Page Caching with Stale-While-Revalidate via Cloudflare Workers

Editorial content changes only when published or revised. We configured edge caching with instant tag-based invalidation upon article save, ensuring 94% of visitors hit an edge node in less than 50ms.

Alternative Rejected

Rejected pure client-side SPA rendering which penalizes search engine crawlers and cold mobile visits.

Phase 04 • Technical Topology
System Architecture & Data Pipeline

A streamlined PHP 8.3 core with Redis transient caching, custom semantic Gutenberg blocks, and Cloudflare edge micro-caching with automated cache purge hooks.

NODE_01// pipeline

Clean Core Theme & Custom Block Suite

Zero external framework dependencies. Semantic HTML5 markup styled with purposeful utility CSS.

NODE_02// pipeline

Persistent Redis Object Cache

Complex navigation trees, taxonomy lookups, and author bios cached in memory.

NODE_03// pipeline

Automated Edge Invalidation

Post publish hooks purge only the updated post, category archives, and RSS feeds across edge nodes.

Phase 05 • Outcome & Retrospective

The site successfully weathered multiple front-page traffic spikes with zero downtime and a [SCORE: 98/100] mobile Lighthouse profile.

Key Engineering Takeaways:
  • 01.WordPress is not inherently slow; careless plugin accumulation is.
  • 02.Native Gutenberg blocks provide modern editing ergonomics without payload baggage.
  • 03.Edge caching transforms server requirements by an order of magnitude.
What I Learned

“Clients appreciate code speed when it translates directly to lower hosting costs and happier journalists.”