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
How to Improve Website Performance in Webflow – 5 Quick Tips
Slow websites hurt conversions, frustrate visitors, and impact SEO. These are the key things I focus on to keep sites fast:
1️⃣ Optimize Images
Large images are the most common cause of slow pages.
Use WebP or AVIF
**Webflow automatically serves responsive images for different devices.
2️⃣ Clean Up Unused Classes
Remove unused styles to reduce CSS weight.
**Be careful: classes used inside Embed elements may appear as unused in Webflow.
3️⃣ Limit heavy interactions
Too many Lottie files, scroll effects, or animations can slow the page.
4️⃣ Be Careful With Embeds
Widgets, feeds, and external scripts add load time. Use them sparingly.
5️⃣ Minimize Third-Party Scripts
Only keep essential integrations. Poorly optimized scripts are a common performance issue.
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
Our own homepage scored 54 on mobile. Here is how we got it to 99.
We build fast sites for clients. Then we ran PageSpeed on our own homepage and got 54 on mobile.
Three things were doing most of the damage:
1) An autoplaying 4K hero film. It was about 21 MB of a 22 MB page.
2) Google Tag Manager. It alone blocked the main thread for around 4 seconds.
3) A booking widget loading its scripts and cookies on every visit.
What we changed:
• The film became a small poster image. The video now starts on the visitor's first interaction.
• Tags load on first interaction or after 5 seconds. No tag was removed.
• The booking widget is gone.
• Images are served as AVIF and WebP in the right size.
Result on the mobile homepage: 54 to 99. Page weight went from about 22 MB to about 0.5 MB. Total Blocking Time went from 4,740 ms to 30 ms.
One caveat: lab scores move. The same page scored between 86 and 99 on the same day, so we report the median of three runs.
Full write-up with every number: https://codevibe.in/case-studies/website-speed-optimization
If your site feels slow, the hero video and the tag manager are the first two places I would look.
codevibe.in
Website Speed Case Study: PageSpeed 54 to 99 | Codevibe
How Codevibe took its own Next.js site from 54 to 99 on mobile PageSpeed and 100 on desktop: 22,563 KiB to 530 KiB, blocking time 4.7 s to 30 ms.
54 to 99 is wild. the cobblers kids have no shoes thing is so real lol
Parralax Effect Website Design
I launched my new Next.js portfolio in 5 days with an average mobile PageSpeed score of 98/100
When someone opens my portfolio on their phone, they’re there to see the work. My challenge was to give the images in each case study room to breathe while keeping the pages fast on a mobile connection.
I built the site in Next.js with help from Claude and deployed it to Vercel. I optimized the images, fonts, and code to reduce load times and added structured data as part of the technical SEO work to help search engines understand the content.
The project took 5 days from start to launch. In PageSpeed Insights, the site averaged 98/100 for mobile performance, scored 100/100 for desktop performance, and earned 100/100 on the SEO audit.
I’m taking on new web design projects in November and December.
