Hi, we recently finished building and publishing a case study for one of our projects, and for none other than Mario Testino OBE himself.
When we inherited the site, things were… spicy. Broken Vercel pipelines, a failed Sanity migration, ~200% API overages, and more than 160 missing redirects. The site technically existed, but stability, security, and performance were all compromised.
We rebuilt the foundations using Next.js, Sanity, and Vercel, and a big part of the win came from getting the infrastructure right instead of fighting it.
On the Vercel side, the impact was immediate:
- CI/CD became predictable again. Deployments stopped breaking, builds were faster, and shipping no longer felt like defusing a bomb.
- Edge delivery + sane caching meant the site felt instant without relying on brittle hacks.
- Bot ID + firewall rules helped us shut down aggressive scrapers and automated traffic that were hammering APIs and inflating usage. That alone stabilised costs and removed a whole class of “mystery problems.”
- Observability made it obvious where things were going wrong, so we could fix issues instead of guessing.
Read the entire case study here: Mario Testino