Optimize Your Website's INP: Lessons from Real-World TestingOptimize Your Website's INP: Lessons from Real-World Testing
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
Luca's avatar
Luca Da Corte
max
• 2d
I’m currently on a retainer with a Framer ENT client, and last week we investigated why part of their site was struggling with Core Web Vitals - specifically INP.
Using dev tools and some throttling, I recorded a performance trace and was able to repro the issue with an average recorded INP of over 300ms.
The pages were built by me and fairly simple, so I knew there wasn’t any heavy logic running in the background. So my main suspect was the usual: tracking scripts.
So I duplicated the project, paused the scripts, and ran the exact same test under the same conditions. This change alone made the avg INP drop below 50ms.
The team is now discussing which tools are actually necessary and which ones aren’t, but the bottom line is the same.
(ran out of space)👇🏻
Framerux
Post image
Stephanie's avatar
Stephanie Asoegwu
pro
• 1d
That INP drop from 300ms+ to below 50ms is massive! This is such a good reminder to audit third-party scripts regularly.
Luca's avatar
Luca Da Corte
max
• 2d
Every new script, every new pixel, every new tag added to the site takes away resources and has a direct impact on the user experience.
Obv the solution isn’t to stop tracking altogether, but it’s always a good exercise to see what tools you need, and how much you are willing to compromise on UX for better data.
Back to feed
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