Consulting website rebuild: from 3 seconds to 450ms
I rebuilt the frontend of a technology consulting firm's website from their Figma designs. The site has a lot of service pages, and it was slow. After the rebuild, pages load in about 450ms instead of around 3 seconds, with a Lighthouse performance score of 96+ and a search-ready structure on every page.
A content-heavy site with many service pages that took about 3 seconds to load and wasn't structured well for Google.
What I built
The full frontend from Figma, about 10 pages, with reusable service page templates and technical SEO built into every page.
The result
Load time down from about 3 seconds to about 450ms. Lighthouse performance 96+. Titles, schema, sitemap, and canonical URLs on every page.
Timeline
16 weeks
Budget
$23,000 (frontend from existing Figma designs)
The problem: a slow website with too many pages to fix one by one
The firm offers a broad range of technology and consulting services, and each one has its own page. That's good for search, because each page can rank for its own service. It also means any slowness or messy structure is repeated on every page.
The site took around 3 seconds to load. On a phone, that's long enough for a visitor to leave before reading anything. The brief was clear: keep the Figma design, make the site fast, and make every service page easy for Google to understand.
Building the website from Figma with reusable page templates
I built about 10 pages from the Figma files: the core company pages plus the service and capability pages. Instead of building each service page by hand, I built a small set of reusable templates. Every service page uses the same structure and keeps its own content.
That pays off after launch. Adding a new service means filling in a template, not designing and building a new page from scratch.
Website speed optimization: from 3 seconds to 450ms
Speed was the main engineering goal, so I didn't leave it for a final pass. I checked performance as each page was built and fixed problems while they were still small. The animations stayed. They were built so they don't block the page from loading, which is how the site kept its design and still scored 96+ on Lighthouse.
What I changed:
Image optimization and lazy loading
Less JavaScript sent to the browser
A better loading order for scripts and assets
Faster rendering of the first screen
Animations that don't block the page from loading
Lighthouse testing throughout the build
Technical SEO for a content-heavy service website
A service page that Google can't read properly won't rank for that service, however good it looks. I built SEO into the page templates, so every page gets it by default and nothing depends on someone remembering to add it later:
Page titles and meta descriptions
Open Graph metadata for social sharing
Structured data (schema)
XML sitemap and robots.txt
Canonical URLs
Internal links between related services
A clean heading structure on every page
Image alt text
Readable, keyword-friendly URLs
Search Console setup and indexing
Results
~3s → ~450ms
page load time
96+
Lighthouse performance score
~10
pages built from Figma
Key decisions
01
Build speed in from the first page
Fixing performance at the end of a project usually means undoing work. Checking it page by page kept the site fast without a second rebuild.
Trade-off: It takes more care during the build, but nothing has to be redone later.
02
Reusable templates for service pages
Service firms add and change services over time. Templates keep every page consistent and make a new page quick to publish.
Trade-off: More planning before the first page is built.
03
SEO inside the templates, not added afterwards
When titles, schema, and headings live in the template, every new page is set up correctly without extra work.
What the client said
“Milan turned our Figma designs into a site that loads almost instantly. The service pages work as well as they look, and he walked us through every decision.”
Can you make my website faster without changing the design?
Usually, yes. On this project the Figma design stayed as it was, animations included, and load time still dropped from about 3 seconds to about 450ms. Most slowness comes from how images, scripts, and animations are loaded, not from the design itself.
Does website speed affect Google rankings?
Yes, as one signal among many. Google measures real-visitor speed through Core Web Vitals, which count toward page experience. The bigger effect is on people: a slow page on a phone loses visitors before they read anything, so you get fewer enquiries whatever your ranking.
What is a good Lighthouse performance score?
Google's Lighthouse tool rates 90 to 100 as good. This site scored 96+. Lighthouse is a lab test, so it's most useful as a check during the build. What matters in the end is how fast the site loads for real visitors on real phones.
Do I need a new website, or just a faster one?
If your pages already rank and your content is good, a frontend rebuild like this one keeps what works and fixes speed and structure. If the content, the offer, or the design need rethinking too, you're looking at a full redesign, which costs more and takes longer.