A client’s wallpaper gallery took down its own dashboard hours after launch. Pruning the image sizes WordPress generates and offloading originals to object storage cut upload processing by about 70%.
An agency gallery held 14 years of high-resolution assets and took 12 seconds to load. Caching the resolution URLs in a transient made it worse; generating the links from a CDN naming convention fixed it.
A client’s WooCommerce sync kept dropping SKUs because the same iterator was read twice. Here is what the iterator protocol actually does, and why an iterable and an iterator are not the same thing.
A legacy vendor portal with no IDs, no classes and no API broke every CSS selector we threw at it. One XPath expression replaced fifty lines of them, and it has not broken since.
Console logging the Gamepad API at 60 frames per second tells you nothing useful. Here is the visual debugger I built instead, with its styles isolated in a CSS cascade layer so they stop fighting the theme.
A client with 15,000 archived articles lost hours a week to slow front-end search. The fix was the REST API plus the _fields parameter, queried from a local tool rather than a browser tab.
A Meet the Team row of overlapping avatars broke every time the client added a person. Here is the CSS that works out the negative margin itself, using sibling-count() and container query units.
A JavaScript library added for smooth page transitions hijacked every internal link on a WooCommerce store. Pulling it out and using View Transitions, namespaced classes and accessibility tokens fixed more than it broke.
A reCAPTCHA v2 install stopped a WooCommerce shop’s registration spam and about 15% of its real conversions with it. Turnstile, magic links and a honeypot field did the job without locking customers out.
A client’s organic traffic fell off a cliff and nothing on their site was broken. Google had started answering the queries itself. Here is what I checked, and where the real work sits in a WordPress build.