Remove 2013 Remove Hardware Remove Network Remove Website
article thumbnail

How Improving Website Performance Can Help Save The Planet

Smashing Magazine

How Improving Website Performance Can Help Save The Planet. How Improving Website Performance Can Help Save The Planet. But as it stands, websites are growing ever more obese, which means that the energy demand of the Internet is continuing to grow exponentially. Jack Lenox. 2019-01-15T13:30:32+01:00. 2019-04-29T18:34:58+00:00.

article thumbnail

Touch Design For Mobile Interfaces: Defining Mobile Devices (Excerpt)

Smashing Magazine

Mobile phones are rapidly becoming touchscreens and touchscreen phones are increasingly all-touch, with the largest possible display area and fewer and fewer hardware buttons. The hardware matters, but the underlying OS is the same , and pretty much all apps will run on any device of the same age.

Mobile 104
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

radEventListener: a Tale of Client-side Framework Performance

CSS - Tricks

When even a bit of React can be a problem on devices slow and fast alike, using it is an intentional choice that effectively excludes people with low-end hardware. Server rendering is also cool—even if that’s just how we say “send HTML over the network” these days. A ASUS X550CC laptop from 2013 running Windows 10 on Chrome 83.

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.

article thumbnail

Front-End Performance Checklist 2021

Smashing Magazine

So, if we created an overview of all the things we have to keep in mind when improving performance — from the very start of the project until the final release of the website — what would that look like? Networking, HTTP/2, HTTP/3 OCSP stapling, EV/DV certificates, packaging, IPv6, QUIC, HTTP/3. 300ms RTT, 1.6 Mbps down, 0.8

article thumbnail

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

Smashing Magazine

So, if we created an overview of all the things we have to keep in mind when improving performance — from the very start of the process until the final release of the website — what would that list look like? ( Large preview ). Moto G4) on a slow 3G network, emulated at 400ms RTT and 400kbps transfer speed. 300ms RTT, 1.6