Remove Code Remove Hardware Remove Magazine Remove Traffic
article thumbnail

How We Improved SmashingMag Performance

Smashing Magazine

And suddenly, before you know it, the code base gets a little bit overweight and fragmented , third-party scripts have to load just a little bit earlier, and shiny new dynamic content finds its way into the DOM through the backdoors of fourth-party scripts and their uninvited guests.

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.

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

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. This saves clients traffic — sometimes traffic which the client is paying for. The script was finished with a non-zero code.

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? How do we actually know where we stand in terms of performance, and what our performance bottlenecks exactly are?

article thumbnail

HTTP/3: Performance Improvements (Part 2)

Smashing Magazine

Many network interface controllers (NICs) even have built-in hardware-offload features for TCP. We can also expect QUIC-specific hardware to become available. This is why we should never just test our pages on our own hardware (but also use a service like Webpagetest ) and also why you should definitely deploy QUIC and HTTP/3.