From 450ad8b7d5eb105ef05d902178f2df344647cb02 Mon Sep 17 00:00:00 2001 From: Harry Roberts Date: Mon, 25 Sep 2023 22:19:34 +0100 Subject: [PATCH] =?UTF-8?q?Hopefully=20this=20fixes=20my=20CLS=20problems?= =?UTF-8?q?=E2=80=A6?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- _posts/2019-03-04-cache-control-for-civilians.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/_posts/2019-03-04-cache-control-for-civilians.md b/_posts/2019-03-04-cache-control-for-civilians.md index 34c9c903..f6ac6cbf 100644 --- a/_posts/2019-03-04-cache-control-for-civilians.md +++ b/_posts/2019-03-04-cache-control-for-civilians.md @@ -10,8 +10,6 @@ The best request is the one that never happens: in the fight for fast websites, avoiding the network is far better than hitting the network at all. To this end, having a solid caching strategy can make all the difference for your visitors. -

๐Ÿ“Š How is your knowledge of caching and Cache-Control headers?

— Harry Roberts (@csswizardry) 3 March, 2019
- That being said, more and more often in my work I see lots of opportunities being left on the table through unconsidered or even completely overlooked caching practices. Perhaps itโ€™s down to the heavy focus on first-time visits, or