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
One of the biggest score jumps I’ve worked on had nothing to do with page speed.
At RH I was a frontend developer on the move from Adobe AEM to Contentful. Part of the job was accessibility, and that work took Lighthouse from about 70 to 95+.
What I kept from it is simple. A score like that moves when you fix the things people actually trip on. A button a screen reader can’t name. A menu you can’t reach without a mouse. Grey text you can’t read on a phone in the sun. Chase the number and you get a green circle. Fix the trip-ups and the number comes with them.
So here’s a weekend test for your own store: put the mouse away and try to add something to the cart with only Tab and Enter.
How far did you get? Tell me where it broke.
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
This post format used to take me over an hour. Now it takes under 5 minutes.
Landing page in, Figma MCP connected, Claude handles the layout.
Cool branding!
Made a 20-second ad for Nomlet, my free Framer template for food brands. The jar turns, opens and pours as you scroll, and it scores 100/100 PageSpeed on mobile and desktop. Free on the Framer Marketplace: https://www.framer.com/marketplace/templates/nomlet/?utm_source=contra&utm_medium=social&utm_campaign=nomlet&utm_content=ad-post-2026-11-04
Quick one for anyone who tests responsive layouts: do you drag the browser window to random widths and see what breaks, or pick a fixed list of device sizes in dev tools and only check those?
No wrong answer, just curious which one people actually default to. Reply with "drag" or "fixed."