nhoizey, to random French
@nhoizey@mamot.fr avatar

“An even faster Microsoft Edge” by Microsoft Edge Team

🔗 https://blogs.windows.com/msedgedev/2024/05/28/an-even-faster-microsoft-edge/

> JavaScript must be downloaded, then run through a JIT compiler (even if you don’t use it), and then executed, and all this must be done before any of the JavaScript can start rendering the UI. This introduces a lot of delay before users can see the UI, especially on low-end devices.

⚓️ https://nicolas-hoizey.com/links/2024/05/29/an-even-faster-microsoft-edge/

Nephou,
@Nephou@mamot.fr avatar

@nhoizey let’s hope they will have some opportunity to exchange — pun intended — with their m365 colleagues and make them strip down the madness of SPFx 😅

nhoizey,
@nhoizey@mamot.fr avatar

@Nephou 😅

nhoizey, to random French
@nhoizey@mamot.fr avatar

“Why Lighthouse Performance Score Doesn’t Work” by @fox

🔗 https://calibreapp.com/blog/downsides-of-performance-score

> There is some correlation between the [Lighthouse] Performance Score and how well your site will do for real users. Still, lab testing alone doesn’t capture all speed issues (similarly, field testing might prove inadequate in showcasing other speed problems). That’s why relying on Performance Score is not a bulletproof strategy. We…

#WebPerf #Lighthouse

⚓️ https://nicolas-hoizey.com/links/2024/06/07/why-lighthouse-performance-score-doesn-t-work/

tammy, (edited ) to UX
@tammy@webperf.social avatar

It's heartening to see how many media sites in @speedcurve's Page Speed Benchmarks have sub-2.5s LCP times!

For some of the sites with poorer LCP, perceived / isn't the issue. They're fast to start render. The main culprit is that the LCP element is just wrong.

The takeaway: don't just look at the numbers for your metrics. Visually validate them to make sure they're measuring the right things!

https://app.speedcurve.com/benchmarks/usa/media/fast/largest-contentful-paint/

nucliweb, to javascript
@nucliweb@webperf.social avatar

Comprehensive guide to JavaScript performance analysis using Chrome DevTools

https://blog.jiayihu.net/comprenhensive-guide-chrome-performance/

speedcurve, to UX
@speedcurve@webperf.social avatar

Debugging Interaction to Next Paint (INP) can be tricky! You're in great hands with @andydavies. In this detailed must-read post, Andy walks through:

🔵 How to identify causes of poor INP
🟡 Examples of the most common issues
🟢 How to optimize for INP

https://www.speedcurve.com/blog/debugging-interaction-to-next-paint-inp/

#webperf #ux #corewebvitals #sitespeed #pagespeed #webperformance

tammy, to UX
@tammy@webperf.social avatar

If you care about...

🟡 Delivering a fast UX to your users
🟢 Knowing the minute your site speed starts to suffer (including metrics like Core Web Vitals)
🔵 Fixing performance issues FAST

...then you need performance budgets.

Not sure what a performance budget is? Check out this complete guide: https://www.speedcurve.com/blog/performance-budgets/

nhoizey, to random French
@nhoizey@mamot.fr avatar

Is that the hashtag to use for waterfalls shaming websites with really bad #WebPerf? 🤔
https://mastodon.bot/@trending/112525334902480602

nhoizey, to random French
@nhoizey@mamot.fr avatar

“An even faster Microsoft Edge” by Microsoft Edge Team

🔗 https://blogs.windows.com/msedgedev/2024/05/28/an-even-faster-microsoft-edge/

> JavaScript must be downloaded, then run through a JIT compiler (even if you don’t use it), and then executed, and all this must be done before any of the JavaScript can start rendering the UI. This introduces a lot of delay before users can see the UI, especially on low-end devices.

⚓️ https://nicolas-hoizey.com/links/2024/05/29/an-even-faster-microsoft-edge/

nhoizey, to random French
@nhoizey@mamot.fr avatar

“New field insights for debugging INP” by Jeremy Wagner

🔗 https://www.youtube.com/watch?v=xfjumh8ySRY

> Interaction to Next Paint (INP) is a Core Web Vital that measures how responsive a page is to interactions. Due to INP's scope, it can be difficult to identify why some interactions are slow. Learn how to use new Chrome APIs that provide detailed information on the causes behind slow interactions, and how to collect insights from your website's…

#INP #WebPerf #CoreWebVitals

⚓️ https://nicolas-hoizey.com/links/2024/05/20/new-field-insights-for-debugging-inp/

slightlyoff, to random
@slightlyoff@toot.cafe avatar

One of the teams I've been working with to climb the performance management maturity ladder is...Edge!?!

We build a lot of the browser out of web "stuff" these days (think bookmarks, history, downloads, settings, new-tab-page, etc.), and moving away from React to a modern Web Components + HTML-first architecture has had a huge benefit for users, particularly folks on low-end hardware:

https://blogs.windows.com/msedgedev/2024/05/28/an-even-faster-microsoft-edge/

#webcomponents #webperf #usetheplatform #sorrynotsorry

slightlyoff,
@slightlyoff@toot.cafe avatar

This is building on the same open source, FAST-based design system ("Fluent Web Components v3"):

https://github.com/microsoft/fluentui/tree/master/packages/web-components

But the framework isn't what makes the difference; actually looking and caring about the performance is what has enabled this work to deliver 40-75% wins.

tammy, to UX
@tammy@webperf.social avatar

If your site uses consent popups/banners (and it probably does), this post is a must-read. CMPs create huge web performance challenges, such as:

  1. Single point of failure
  2. Mask third-party issues
  3. Identify wrong LCP element
  4. Hurt CLS score
  5. Delay INP

https://www.speedcurve.com/blog/web-performance-cookie-consent/

speedcurve, to UX
@speedcurve@webperf.social avatar

Cookie consent popups and banners are everywhere, and they're silently hurting the speed and UX of your pages. Learn the most common problems – and solutions – with measuring web performance with a content manager platforms (CMP) in place.

https://www.speedcurve.com/blog/web-performance-cookie-consent/

ryantownsend, to webdev
@ryantownsend@webperf.social avatar

Oliver Lingberg just published an interview with me about the industry and my upcoming talk at his conference Pixel Pioneers on June 14th: https://pixelpioneers.co/blog/speaker-spotlight-ryan-townsend

If you're considering coming you can get 10% off with the code 'Friends10', making the price just ~£140 ex VAT. Student tickets are also available for £60 – exceptional value! Full details 👉 https://pixelpioneers.co/

A talking-head video with Ryan Townsend sat at a desk.

orangeacme, to random
@orangeacme@fosstodon.org avatar

Yet again I am on high latency, low-bandwidth hotel WiFi and am thankful for teams that prioritise web performance

speedcurve, to UX
@speedcurve@webperf.social avatar

ICYMI: Our latest release includes RUM attribution and subparts for INP! @cliff explains:

🟡 Element attribution

🟢 Where time is spent within INP, leveraging subparts

🔴 How to use this information to fix INP issues

https://www.speedcurve.com/blog/rum-attribution-subparts-interaction-to-next-paint/

#webperf #ux #corewebvitals #sitespeed #pagespeed #webperformance

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • mdbf
  • ngwrru68w68
  • modclub
  • magazineikmin
  • thenastyranch
  • rosin
  • khanakhh
  • InstantRegret
  • Youngstown
  • slotface
  • Durango
  • kavyap
  • DreamBathrooms
  • megavids
  • GTA5RPClips
  • tacticalgear
  • normalnudes
  • tester
  • osvaldo12
  • everett
  • cubers
  • ethstaker
  • anitta
  • provamag3
  • Leos
  • cisconetworking
  • lostlight
  • All magazines