Remove Code Remove Magazine Remove Speed Remove Testing Tools
article thumbnail

What Web Designers Can Do To Speed Up Mobile Websites

Smashing Magazine

What Web Designers Can Do To Speed Up Mobile Websites. What Web Designers Can Do To Speed Up Mobile Websites. I recently wrote a blog post for a web designer client about page speed and why it matters. What I didn’t know before writing it was that her agency was struggling to optimize their mobile websites for speed.

Website 110
article thumbnail

Performance Game Changer: Browser Back/Forward Cache

Smashing Magazine

WebPageTest is one of the few web performance testing tools that actually tests a reload of the page using a primed HTTP Cache — most of the other tools just flag if your HTTP resources are not explicitly set to be cached. Back/Forward Cache Testing Tool. Large preview ).

Cache 91
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

The State Of Mobile And Why Mobile Web Testing Matters

Smashing Magazine

Lighthouse CI is quite remarkable: a suite of tools to continuously run, save, retrieve, and assert against Lighthouse results. One thing is certain though: your websites will rank better if they are better optimized for mobile, both in terms of speed and mobile-friendliness — it goes for accessibility as well. Large preview ).

Mobile 133
article thumbnail

Solving CLS Issues In A Next.js-Powered E-Commerce Website (Case Study)

Smashing Magazine

We use Lighthouse and WebPagetest as our synthetic testing tools for performance to measure CLS. At first, we decided to run some tests using synthetic testing tools. Therefore having a low CLS value for a page ensures there are no random layout shifts causing user frustration. 004 which is quite low.

Website 105
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? Note : If you use Page Speed Insights or Page Speed Insights API (no, it isn’t deprecated!),

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? Start Render time, Speed Index ). Rendering metrics provide an estimate of how fast content renders (e.g.

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.