Remove Cache Remove Strategy Remove Website Remove Workshop
article thumbnail

Refactoring CSS: Optimizing Size And Performance (Part 3)

Smashing Magazine

In previous articles from this series, we’ve covered auditing CSS codebase health and the incremental CSS refactoring strategy , testing, and maintenance. 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.

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

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

Jamstack CMS: The Past, The Present and The Future

Smashing Magazine

The world’s first website was made from static HTML files created in a text editor. Fast-forward 30 years, and website technology has changed significantly — we have images, stylesheets, JavaScript, streaming video, AJAX, animation, WebSockets, WebGL, rounded corners in CSS — the list goes on. Mike Neumegen. released 1998.

Ecommerce 139
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

This approach was touted to be better for fine-grained caching because each subresource could be cached individually and the full bundle didn’t need to be redownloaded if one of them changed. Your user has requested that you navigate to example.com (a website you’ve never visited before), and you’ve used DNS to resolve that to an IP.

Network 105