Loading time is not an end in itself but a chain of network, server, transfer and rendering in the browser. This category lays the groundwork: how a page display is produced technically, which steps block each other, why lab and field measurements differ, and which order of work delivers the greatest effect on a limited budget. We classify common recommendations, separate effective measures from cosmetics and show how optimisation can be anchored permanently in operations — with page weight budgets, checks before every release and clear responsibilities. Articles on sustainability are included too: less transferred data means less energy per page view. We also clarify which metrics are suitable for management reporting and which are only useful inside the technical team.
On this page you will find all posts on the topic “Fundamentals & strategy”. The newest posts are at the top.
Below each title there is a short text about it. Click on a post. Then you can read the whole text.
Above the list you also see the other topics. At the bottom, a link takes you back to all posts.
PageSpeed optimization costs depend on templates, shop system, scripts, server and images. How to plan analysis, fixed price, monitoring and a 2027 budget.
How load time becomes a verifiable acceptance criterion: target value, method, data source and proof date per metric – and what German contract law makes of it.
A performance budget as a budget.json rule checks every pull request in Lighthouse CI and stops the build the moment LCP, INP or CLS breach the threshold.
Sustainable websites: how fewer bytes, lean JavaScript and efficient caching cut the CO2 footprint while improving Core Web Vitals at the same time.
Lighthouse lab scores do not affect ranking. Google rates Core Web Vitals via CrUX field data at the 75th percentile. How to use RUM, CrUX and budgets.
Visual Stability Index (VSI): in 2026 Google measures layout stability across the whole visit, not just page load. How to make your website future-proof.
LQIP, blur-up and responsive images for faster image build-up: better perceived and measured performance, fewer layout shifts, strong Core Web Vitals.
SSR delivers HTML fast, but hydration costs performance. Islands, partial hydration and resumability for fast shops and strong Core Web Vitals.
Avoid CLS: fix layout shifts from images, fonts, ads and injections precisely. The result is measurably more stable shop layouts with a good CLS score.
Trimming third-party scripts: audit tags, defuse them with defer and lazy loading, use facades and measurably improve INP and LCP for better Core Web Vitals.
HTTP/3 with QUIC cuts latency and connection setup time in online shops. How the protocol works, when migration pays off and how to enable it correctly.
Core Web Vitals 2026: INP replaces FID, updated thresholds and optimization strategies. How to measure and improve your scores systematically.
Optimize Time to First Byte: identify causes of slow server response times and fix them systematically with DNS, TLS, backend and caching strategies.
Extract, inline and automate Critical CSS: load the visible area in milliseconds, keep the rest out of the way and improve your LCP score for the long run.
WebP, AVIF, responsive images and lazy loading: How to optimize images for faster loading times, better Core Web Vitals and considerably smaller image data.
Minimize JavaScript impact on INP and loading time: performance budgets, code splitting, tree shaking and third-party management for Core Web Vitals.
Multi-tier caching architecture with Varnish, Redis and browser cache: strategies for TTFB under 100ms, a high cache hit rate and optimal invalidation.