The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
95 on mobile PageSpeed — for a Webflow site with a full CMS.
Movva is a multi-page Webflow template I built for yoga and pilates studios: classes, schedules, instructors, events, blog — all CMS-driven. Heavy imagery, a big hero, a lot of content.
Mobile: 95 Performance · 100 Accessibility · 100 Best Practices · 100 SEO.
What made the difference:
• Hero image set to eager loading — lazy-loading the largest image on the page delays LCP
• Separate mobile and desktop images, especially for the hero — phones don't download desktop-sized files
• All images in WebP, sized for their actual display size
• SEO set up at the template level, so every CMS page gets proper metadata automatically
Plus a handful of smaller fixes — they add up.
Webflow sites aren't slow by default. They get slow through oversized assets and stacked third-party scripts.
If your Webflow site scores in the red on mobile, send me the link — happy to take a look.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
💫 Webflow website for an Observatory.
Have you ever wanted to visit an observatory and see the planets up close?
I created a minimalist website where you can book a multi-day trip like this. The website is built in Webflow, with easy-to-manage CMS collections, a booking system, and an engaging design.
I love micro-interactions.
They’re probably one of my favorite parts of building the new Offmade Studio portfolio...
this looks incredible!
AI is changing how we build websites.
But I don’t think AI is replacing Webflow developers.
I think it’s changing what developers spend their time on.
With AI, we can now speed up things like:
→ Generating custom code snippets
→ Troubleshooting CSS and JavaScript
→ Creating content structures
→ Building CMS schemas faster
→ Finding accessibility issues
→ Optimizing repetitive tasks
→ Turning ideas into working prototypes much faster
But there’s still a big difference between generating something and building something properly.
AI can give you a solution.
It doesn’t always know whether that solution is:
scalable
maintainable
responsive
SEO-friendly
accessible
appropriate for the actual business
That’s where Webflow development experience still matters.
I see AI as a developer multiplier, not a replacement.
The best workflow, in my opinion, is:
AI for speed → Developer for decisions → Webflow for execution.
I’m curious about the Webflow community:
Where are you currently using AI in your Webflow workflow?
Code generation? CMS? SEO? Design? Debugging? Content?
Or are you still keeping AI completely out of your process?
#Webflow #AI #WebflowDeveloper #WebDevelopment #AIDevelopment #NoCode