Gatsby to Webflow Migration & Core Web Vitals for Aubergine

Aubergine Solutions is a design and technology studio with offices in India, the USA and Singapore, recognised as one of the top B2B companies on Clutch. For a studio like this, the website is the shop window: it's where clients judge the quality of the work, and where most new enquiries begin.

I joined on a maintenance contract, and over 3 years and 4 months my role grew into looking after Aubergine's whole web presence: first speeding up the Gatsby site and WordPress blog, then migrating both into one Webflow site at aubergine.co.

Client: Aubergine Solutions, India · USA · Singapore

My role: Web developer, from maintenance to leading the Webflow migration

Timeline: 3 years 4 months

Stack: Gatsby, React, WordPress, AWS, GitLab CI/CD, Webflow, HubSpot, Figma

Core Web Vitals passed on mobile and desktop, measured on 28 days of real Chrome visitors.

1.2 s LCP and 26 ms INP on desktop, with 0 layout shift on both mobile and desktop.

40+ pages built from Figma, including 6 service pages and 26 campaign landing pages in A/B pairs.

Releases cut to 1 push, from a manual, multi-step build and upload.

2 platforms merged into 1 Webflow site the marketing team runs themselves, with permanent redirects keeping the old site's search value.

Every enquiry straight into HubSpot, with the visitor's browsing history attached.

The site had to show off the quality of Aubergine's design and engineering and turn visitors into enquiries, but the setup was working against it: a Gatsby site and a WordPress blog on separate servers, hand-run releases, heavy CSS and JavaScript, SEO gaps, and every new page waiting on a developer.

A global CDN and one-push releases. I moved the Gatsby site from a single server to AWS S3 and CloudFront, then set up GitLab CI/CD. Merging to main now builds the site, deploys it and clears the CDN cache, with a separate staging site for reviews.

Pages faithful to Figma. Service pages, job openings and A/B campaign landing pages built from the design team's files on every screen size, plus contact forms with a country-code picker and proper phone validation.

Core Web Vitals work. Code splitting, unused libraries and CSS removed, minified assets, responsive images and no layout shift, on both the Gatsby site and the WordPress blog.

SEO that search engines notice. Canonical tags and share images on every page, one main heading per page, and the blog moved onto the main domain.

One Webflow site instead of two platforms. I migrated the Gatsby site and WordPress blog into one Webflow site, so marketing publishes pages and articles without a developer, and connected its forms to HubSpot.

Read the full case study, with the complete architecture and more screens, on my website: akshatarora.in/work/aubergine-solutions