Items tagged with: webperf

Search

Items tagged with: webperf



Microsoft Mgmt Deteriorates GitHub UX - Goodbye Perf and Progressive Enhancement?

Mu-An Chiou writes @muan:

"React got pushed down from Microsoft management and most of us on the [GitHub] front-end team quit."

muan.co/posts/javascript

#webperf #ProgressiveEnhancement #github #Microsoft


Some impressive test results from
@PatMeenan about Compression Dictionaries (just approved to ship in Chrome!):
github.com/WICG/compression-di…

Unlike traditional gzip or brotli usage, this allows compression ACROSS requests.

So app-v1.js could be reused when downloading app-v2.js so only the differences are downloaded basically.

Or a separate dict could be used to compress similar pages (e.g. those using same templates or layout) so they basically only include page-specific content.

#webperf



Please don't bloat web pages!

"Modern web bloat means some pages load 21MB of data - entry-level phones can't run some simple web pages"

tomshardware.com/tech-industry…

#webperf #webdev #webdevelopment #usability #sustainability




I've a new blog post out on all the lovely Speculation Rules improvements in Chrome.

I'm VERY excited about Document Rules and how easy it makes it to add low-risk prefetch or prerendering to your site:
developer.chrome.com/blog/spec…

Try it out and let me know how you get on!

#webperf








Modern Health, frameworks, performance, and harm

ericwbailey.website/published/…

"Performance, accessibility, and usability are more than inconvenient truths you can pretend don’t exist. They have a direct impact on the quality of someone’s life."

#webdev #webperf #ux #usability #a11y #uxd #webdesign




Are you sure you need an SPA? Probably not. "Why I'm not the biggest fan of Single Page Applications" matuzo.at/blog/2023/single-pag… Great points by @matuzo #webdev #spa #webperf




Accessibility: the land that time to interactive forgot | Léonie Watson | performance.now() 2022 youtube.com/watch?v=tQkPog-stj… #a11y #webdev #webperf "We tend to think of performance in terms of latency, code optimization, and things like the critical rendering path, but what happens when the browser creates an accessibility tree as well as the DOM?"