Remove Code Remove Hardware Remove Internet Remove Magazine
article thumbnail

How Improving Website Performance Can Help Save The Planet

Smashing Magazine

You may not think about it often, but the Internet uses a colossal amount of electricity. This, in turn, means that the Internet’s carbon footprint has grown to the point where it may have eclipsed global air travel , and this makes the Internet the largest coal-fired machine on Earth. These include data transfer (i.e.

article thumbnail

Eye-Tracking In Mobile UX Research

Smashing Magazine

In the late 1990s, marketing and advertising agencies saw the potential of eye-tracking for the Internet and started using the technology to analyze how people consume content online. For instance, Nielsen’s research conducted in 2006 showed that people read content on the Internet in an F-shaped pattern. More after jump!

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

How To Build Resilient JavaScript UIs

Smashing Magazine

Different browsers running on different platforms and hardware, respecting our user preferences and browsing modes (Safari Reader/ assistive technologies), being served to geo-locations with varying latency and intermittency increase the likeness of something not working as intended. Pessimism over optimism favours resilience.

Network 145
article thumbnail

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

Smashing Magazine

Is it worth exploring tree-shaking, scope hoisting, code-splitting, and all the fancy loading patterns with intersection observer, server push, clients hints, HTTP/2, service workers and — oh my — edge workers? The first render tends to warm up a bunch of lazily compiled code, which a larger tree can benefit from when it scales.

article thumbnail

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

Smashing Magazine

Is it worth exploring tree-shaking, scope hoisting, code-splitting, and all the fancy loading patterns with intersection observer, server push, clients hints, HTTP/2, service workers and — oh my — edge workers? It’s much easier to reach performance goals when the code base is fresh or is just being refactored.

article thumbnail

How To Make Performance Visible With GitLab CI And Hoodoo Of GitLab Artifacts

Smashing Magazine

It’s happening because of new features being added and the fact that we sometimes don’t have a second thought on packages that we constantly add and update, or think about the complexity of our code. For example, for an internet shop, it may be a page with a product list, product details page, shopping cart, checkout, and so on.

article thumbnail

Front-End Performance Checklist 2021

Smashing Magazine

Have we optimized enough with tree-shaking, scope hoisting, code-splitting, and all the fancy loading patterns with intersection observer, progressive hydration, clients hints, HTTP/3, service workers and — oh my — edge workers? It’s much easier to reach performance goals when the code base is fresh or is just being refactored.