Atlas Fintech
B2B SaaS · Financial Services
Atlas Fintech: from a 3.8s LCP to 0.7s in twelve weeks
3.4× Content velocity
Published
01 — Challenge
What was in the way
Atlas's marketing site was a five-year-old WordPress install fronting a Salesforce Pardot pipeline. Lighthouse Performance was 41. The marketing team was shipping one post a month because every change required engineering review and a deploy that took 40 minutes.
02 — Approach
How we shipped it
We migrated Atlas to the multi-site platform: shared design-system, content collections in git, native lead form into HubSpot, Pagefind on-site search. The marketing team now ships content directly via PR. Engineering involvement dropped to a quarterly token review.
03 — Outcome
What changed
- LCP
- 0.7s
- Content velocity
- 3.4×
- Lighthouse
- 98
We stopped thinking of the marketing site as something engineering owns. The platform handed us back our own publishing rhythm.
Services involved
What we did on this engagement
What changed
The biggest shift wasn’t a single optimization — it was removing the WordPress + plugin sprawl entirely. The new site ships as static HTML with one client-side hydration island per page. Most pages load nothing JavaScript-side at all.
Content collections gave the marketing team typed authoring without the friction of a CMS. They write in Obsidian, push a PR, and a Coolify preview is up in two minutes.
What we didn’t do
We didn’t replatform the product app, the customer dashboard, or the admin tools. The scope was the marketing site — about 60 routes — and we held that line. It’s the reason we hit the date.