Remove Cache Remove Network Remove Website Remove Workshop
article thumbnail

Five Data-Loading Patterns To Improve Frontend Performance

Smashing Magazine

The resource loading waterfall is a cascade of files downloaded from the network server to the client to load your website from start to finish. It essentially describes the lifetime of each file you download to load your page from the network. You can see this by opening your browser and looking in the Networking tab.

Cache 126
article thumbnail

Refactoring CSS: Optimizing Size And Performance (Part 3)

Smashing Magazine

Deploying the refactored codebase shouldn’t result in worse website performance and worse user experience. After all, users won’t wait around forever for the website to load. Jump to online workshops ?. More after jump! On design systems, CSS/JS and UX. With Carie Fisher, Stefan Baumgartner and so many others. Critical CSS.

Media 109
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

GraphQL On The Front-End (React And Apollo)

Smashing Magazine

We’ll be learning how to do this with GraphQL Features like Cache Update, Subscriptions, and Optimistic UI. website to download the latest version. Continue reading below ↓ Meet Smashing Online Workshops on front-end & UX , with practical takeaways, live sessions, video recordings and a friendly Q&A.

Cache 115
article thumbnail

Improving The Performance Of An Online Store (Case Study)

Smashing Magazine

Real-life performance for your users and how the website “feels” when you’re using it should not be discounted, even if it costs you a point or two in Page Speed (otherwise, we would all just have a search bar and unstyled text). Today, the website is much faster and ranks highly in various showcases and benchmarks. Large preview ).

article thumbnail

How We Improved SmashingMag Performance

Smashing Magazine

It always starts with the long-awaited website overhaul. Plus a service worker that caches all static assets and serves them for repeat views, along with cached versions of articles that a reader has already visited. Throughout the workshop, I was diligently taking notes and revisiting the codebase. Vitaly Friedman.

article thumbnail

HTTP/3: Practical Deployment Options (Part 3)

Smashing Magazine

Next, we’ll look at how to set up servers and clients (that’s the hard part unless you’re using a content delivery network (CDN)). Using just a few (but still more than one), however, could nicely balance congestion growth with better performance, especially on high-speed networks. Servers and Networks.

Network 105
article thumbnail

Percentiles don’t work: Analyzing the distribution of response times for web services

Adrian Cockcroft

A later version of the slides is included in my Microservices Workshop deck from later that year, slides 168–200 ( pdf , keynote are available in GitHub.com/adrianco/slides ). What Is the Expected Distribution of Website Response Times?

Lambda 98