I just earned the Official Framer Expert badge — here's what that means for you
After 150+ delivered projects and thousands of hours in Framer, I've been recognized as an Official Framer Expert. This isn't just a title — it means you're working with someone who has been vetted for quality, reliability, and deep platform knowledge.
Whether you need a Figma-to-Framer conversion, custom code components, CMS setup, responsive builds, or complex interactions — I've shipped it. On time. Clean code. No excuses.
Open to new projects on Contra. Drop a message or book directly from my profile.
Congrats on the Framer Expert recognition. 150+ delivered projects is what makes that badge mean something. The Figma-to-Framer conversion work especially is a skill set that not many people execute cleanly at scale.
I've been seeing a lot of designers moving from Framer to Astro, posting their new Lighthouse scores, and calling Framer the problem.
I think we're missing a bigger conversation here.
Astro is fast. No argument there. It ships static HTML with very little JavaScript by default, and having full control over your code is a real advantage.
But how many designers actually understand what's making their websites slow?
Do you know what LCP, INP, and CLS measure?
Are you checking image sizes and formats? Video compression? Font loading? Third-party scripts? The JavaScript behind your interactive components?
What about those scroll animations, huge blur effects, and background videos running on mobile?
Framer has made something incredible possible: designers can now build, host, and publish complete websites without depending on a developer.
But that freedom doesn't mean web fundamentals suddenly stop mattering.
And I'm not saying Framer is perfect. Its runtime has overhead, and Astro gives developers a level of control that Framer simply doesn't.
I'm a web engineer who builds with Framer, and I think both tools have their place.
What I find strange is seeing people treat a higher Lighthouse score after a complete rebuild as proof that the previous platform was the entire problem.
Sometimes it's the tool. Sometimes it's how you built the website. Often it's both.
Before switching stacks, understand what you're actually trying to fix.
Agree, Jalal. Most Lighthouse drops I see on Framer sites come from oversized images, heavy embeds and too many font weights rather than the platform itself.
New here, so I'm slowly filling in my portfolio and getting to know the place. So far I like it.
Here's an extract from Software Intelligence, a Framer site I designed and built a few months ago for an enterprise data consulting startup.
The visual idea mirrors what they do with data: compact blocks that animate, break apart and recompose, like charts taking shape. Few effects, all consistent, everything managed through the CMS.
If you have a minute, take a look at the full case study.
I'd love to know what you think, especially whether the motion supports the content or ends up overpowering it.