Testlify's marketing site is large — 11,000+ pages — and running on WordPress, where page loads were slow enough to hurt bounce rates and publishing changes was heavier than it should be. I made the call to move it to a Jamstack architecture, and the migration is currently underway.

The decision

Jamstack over WordPress: At 11,000+ pages, the WordPress setup was paying a rendering and plugin cost on every request. Moving to a static Jamstack build serves pre-rendered pages instead, which is where most of the speed comes from — and faster loads directly help bounce rate on a marketing site.
CMS-driven content: Content moves into a headless CMS, so the marketing team publishes and updates pages through it and the site rebuilds from that source — faster to ship content than the old flow, and cleaner to maintain at this page count.
Migrating at scale: The work is about moving 11,000+ existing pages onto the new architecture without losing SEO equity or breaking URLs — the hard part of any migration this size, and the reason it's a staged rollout rather than a flip.

Why it mattered

The migration is projected to cut page load times by around 60%. On a marketing site that's not a vanity metric: faster pages mean lower bounce and better search ranking, and the CMS-driven pipeline lets the marketing team move content out the door without waiting on engineering.