4 stories to explore
Web Performance
How do you make a website feel instant?
Perceived speed comes from shipping less and blocking less: static HTML where possible, deferred fonts and scripts, images sized and lazily decoded, and prefetch on intent. Crashtech treats performance as an architecture decision rather than a post-launch audit.
CRASHTECH / DISCOVERY
Go deeper into web performance.
A fresh way into this beat, shaped by your curiosity.
Tune your mix
Make room for what interests you.
Reading progress and saves shape this browser’s suggestions. Use + to follow a beat or − to see less of it.
Stored in this browser. No sign-in needed.
Find every story in the complete collection below.
Pick up where you left off
Every story on this beat
Search the whole collection or take a different route.
No matches —
Questions we answer on this beat
- What problem does HTTP/2 solve compared with HTTP/1.1?
- What is head-of-line blocking and does HTTP/2 remove it?
- Why does HTTP/3 use UDP?
- How can I check which HTTP version a site is using?
- What is the difference between latency, bandwidth and throughput?
- Why measure p95 and p99 instead of the average?
- What is the quickest win for network latency?
- How do I decide whether to make something asynchronous?
- What is a cold start?
- How does SnapStart reduce cold start time?
- What is provisioned concurrency?
- What can I do in my own code to reduce cold starts?
Entities on this beat
Frequently asked questions
What actually improves Core Web Vitals?
Cutting render-blocking resources, reserving layout space for images and ads, and reducing main-thread JavaScript move the needle far more than micro-optimisations. Static rendering removes most of the problem before measurement starts.
How many Web Performance articles has Crashtech published?
4 articles on this beat, the most recent published November 14, 2026 and the earliest November 13, 2026. 16 questions have a dedicated answer page with an authored direct answer.