Sander van Surksum

Audit finding: 2 sprints on image optimisation, zero LCP improvement. LCP sub-parts breakdown told the story: - TTFB: 2.1s - Resource Load Delay: 1.4s - Resource Load Duration: 500ms - Render Delay: 200ms TTFB was half the LCP budget. Once that was addressed → LCP 1.6s.

Your website has a UX Score and you've probably never seen it. It's based on real Chrome user data from real visits. Not a lab test. Not a guess. Enter any URL, get your score in 10 seconds: iron-out.io/benchmark Free. No login 🚀 #pagespeed #corewebvitals #uxscore

@OvernameExpert Ik kan hier helaas ook niet opzeggen, zowel zakelijk als privé lukt het niet. Volgens de helpdesk is er sprake van een storing 🤡

Website Easypark: opzeggen is héél simpel, 'één druk op de knop'. Enfin ik die ene knop in de app aanklikken: 'kan niet, u heeft een abonnement' 🙈🙈 #easypark #parkeren #doei

We've seen many sites launch with performance issues. Addressing performance throughout the #SDLC is more effective, saving time and resources while ensuring a smoother, faster, and more reliable website from the start. iron-out.io/blog/webperfor…

We're excited to announce a new partnership with Iron/Out Web Performance Experts!    Thanks to the talented @SSurksum for his detailed feedback and insights into web performance and effective monitoring.

- INP is heavily influenced by JS execution happening independent of the interaction - Hydration is a frequent source of such JS execution RSC helps because it doesn't hydrated The other big thing that helps is React 18's partial hydration. While it doesn't reduce total CPU, it does let the user action to interrupt the hydration.

Shoutout to @sanderheilbron for fixing INP issues for a client - now below the 200ms 'good' threshold on mobile! The Goal: Optimal UX via better INP The Win: CrUX data confirms success! Proud of his work and dedication Need a web performance boost? Let's chat! #WebPerformance

@real_ozcoder @ChromiumDev Firefox and Safari download images only for the specific viewport, which I expected to happen in Chrome as well.

@SSurksum @ChromiumDev AFAIK, all the images will be requested, just the ones that don't match the media query will have a low priority, in case the user resizes the browser. This is true even if there is a display:none style in a media query.

Is this a bug in @ChromiumDev ? Both mobile and desktop images will be requested on desktop if loading="lazy" is not set #webperf #pagespeed