Remove Analytics Remove Code Remove Hardware Remove Magazine
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. Large preview ).

article thumbnail

How Improving Website Performance Can Help Save The Planet

Smashing Magazine

how much data does the browser have to download to display your website) and resource usage of the hardware serving and receiving the website. In this screenshot below, for example, we can see that loading the Smashing Magazine website for the first time incurs just under a megabyte of data transfer. These include data transfer (i.e.

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 2021

Smashing Magazine

This guide has been kindly supported by our friends at LogRocket , a service that combines frontend performance monitoring , session replay, and product analytics to help you build better customer experiences. Study common complaints coming into customer service and sales team, study analytics for high bounce rates and conversion drops.

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

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? To get accurate results and goals though, first study your analytics to see what your users are on.

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. In the case that new development changes the file size to the point of exceeding the defined limit, the script will complete with non-zero code.