Remove 2015 Remove Benchmarking Remove Latency Remove Network
article thumbnail

The Performance Inequality Gap, 2024

Alex Russell

It's time once again to update our priors regarding the global device and network situation. JavaScript-Heavy # Since at least 2015, building JavaScript-first websites has been a predictably terrible idea, yet most of the sites I trace on a daily basis remain mired in script. [1] What's changed since last year? and 75KiB of JavaScript.

article thumbnail

The Performance Inequality Gap, 2021

Alex Russell

Thanks to progress in networks and browsers (but not devices), a more generous global budget cap has emerged for sites constructed the "modern" way: ~100KiB of HTML/CSS/fonts and ~300-350KiB of JS (compressed) is the new rule-of-thumb limit for at least the next year or two. Modern network performance and availability.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Netflix at AWS re:Invent 2019

The Netflix TechBlog

In this talk, we share how Netflix deploys systems to meet its demands, Ceph’s design for high availability, and results from our benchmarking. Netflix runs dozens of stateful services on AWS under strict sub-millisecond tail-latency requirements, which brings unique challenges.

AWS 37
article thumbnail

Front-End Performance Checklist 2020 [PDF, Apple Pages, MS Word]

Smashing Magazine

If you don’t have a device at hand, emulate mobile experience on desktop by testing on a throttled 3G network (e.g. To make the performance impact more visible, you could even introduce 2G Tuesdays or set up a throttled 3G/4G network in your office for faster testing. 300ms RTT, 1.6 Mbps down, 0.8

article thumbnail

Front-End Performance Checklist 2021

Smashing Magazine

Networking, HTTP/2, HTTP/3 OCSP stapling, EV/DV certificates, packaging, IPv6, QUIC, HTTP/3. If you don’t have a device at hand, emulate mobile experience on desktop by testing on a throttled 3G network (e.g. Estimated Input Latency tells us if we are hitting that threshold, and ideally, it should be below 50ms. 300ms RTT, 1.6