Performance issues aren’t about the slowest page. They’re about the page that impacts the most us...

Performance issues aren’t about the slowest page. They’re about the page that impacts the most us...Performance issues aren’t about the slowest page. They’re about the page that impacts the most us...

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

Neelesh Kumar

• Jan 9

Performance issues aren’t about the slowest page. They’re about the page that impacts the most users.

In QA and performance testing, I’ve seen 100ms regressions on high-traffic flows cause more damage than multi-second delays on rarely used pages.

Prioritization should follow impact × usage, not just worst metrics.

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)👇🏻

Framer ux

Simon Presland

pro

• 11h

Migrating a website is a serious project. If it's done badly you can lose years of organic rankings and your traffic can disappear overnight.

For some reason this is often an afterthought, with content migration left until the last minute after the new site has already been built.

To maintain organic traffic after a migration, SEO has to be part of the process from day one, not a final checklist item before launch.

Most SEO risk in a migration happens before a single line of code is written.

If you don’t know which content and URLs drive traffic, you’re rebuilding the site blind.

When migrations fail it’s rarely because the new site looks bad, it’s because the URL structure, redirects, and content mapping weren’t handled properly.