Server-level cache (LiteSpeed/Varnish) configuration
LiteSpeed or Varnish caching configured correctly — only where your host actually offers it.
Nothing here is broken. This is the work a site accumulates while it is running normally — content that needs updating, an integration that needs building, a report someone has asked for, hosting that needs moving or documenting.
Showing 209–224 of 248 fixes
LiteSpeed or Varnish caching configured correctly — only where your host actually offers it.
A shared media library configured across subsites, without forcing every subsite into it.
A complete documentation pack compiled — how your site is built, where things live, how to do common tasks.
A skip-to-content link, so keyboard users aren't stuck tabbing through the same menu every page.
Site events routed into the right Slack channel or Teams space, not a flood into one place.
Slow query logging enabled and analysed — only where your host actually allows it.
An SSL certificate installed through your control panel — free or purchased, whatever your host actually offers.
An SSL Labs grade audit and a written improvement plan — without necessarily making the changes ourselves.
Leftover staging URLs removed with a serialization-safe method, not a plain find-and-replace.
Stripe's dashboard and webhook configured through restricted access — never your account password.
A subdomain created and correctly mapped to the right folder.
A new subsite created, optionally cloned from a template rather than starting blank.
One subsite carefully extracted from the network into its own standalone install.
TL;DR blocks generated from a post's own body — condensed, never a fresh editorial take.
TL;DR blocks generated for up to 200 posts, each condensed from its own body content.
A table of contents generated from headings already on the page — no new content needed.
Nothing here is broken. This is the work a site accumulates while it is running normally — content that needs updating, an integration that needs building, a report someone has asked for, hosting that needs moving or documenting.
It is priced the same way as the fixes and for the same reason: each one is a defined piece of work with a known shape, so the page can say what it costs and when it will be done rather than quoting for it.
What differs is how you arrive. Nobody lands here from an error message. You come with a task you have already decided you want, and the only open questions are the price and the date. If you are not sure whether what you need is a fault or a task, describe it and we will point you at the right one.