Remove global Twitter widget

Author: csswizardry

_includes/head.html

@@ -4,18 +4,8 @@
 
 <title>{{ page.title }} {% if paginator and paginator.page > 1 %}Blog – Page {{ paginator.page }} {% endif %}– CSS Wizardry</title>
 
-{% comment %}
-<!--
-  - Preemptively open up connections for external assets (Twitter widgets etc).
-  - Only needed on pages with sidebars (i.e. non-feature pages).
-  -->
-{% endcomment %}
 {% if page.layout != "feature" %}
 <link rel=preconnect href=https://res.cloudinary.com>
-<link rel=preconnect href=https://cdn.carbonads.com>
-<link rel=preconnect href=https://srv.carbonads.net>
-<link rel=preconnect href=https://cdn.syndication.twimg.com>
-<link rel=preconnect href=https://syndication.twitter.com>
 {% endif %}
 
 {% if page.page-class == "page--services  page--workshops" or page.page-class == "page--services  page--downloads" %}
@@ -73,9 +63,6 @@
 
 <script src=https://cdn.speedcurve.com/js/lux.js?id=47684395 defer></script>
 
-{% if page.layout != "feature" %}
-<script src=https://platform.twitter.com/widgets.js defer></script>
-{% endif %}
 {% if page.page-class == "page--services  page--workshops" %}
 <script src=https://gumroad.com/js/gumroad.js defer></script>
 {% endif %}

_includes/sub-content.html

@@ -49,7 +49,7 @@
 <h4>Connect</h4>
 
 <ul>
-  <li><a href=https://twitter.com/csswizardry class=twitter-follow-button data-show-count=true data-lang=en>Follow @csswizardry</a></li>
+  <li><a href=https://twitter.com/csswizardry>𝕏 (Twitter)</a></li>
   <li><a href="https://webperf.social/@csswizardry" rel="me">Mastodon</a></li>
   <li><a href="https://bsky.app/profile/csswizardry.com">Bluesky</a></li>
   <li><a href="https://www.linkedin.com/in/csswizardry/">LinkedIn</a></li>

_posts/2016-06-01-improving-your-css-with-parker.md

@@ -277,7 +277,8 @@ href="http://t.co/0jAEb2h8VF">pic.twitter.com/0jAEb2h8VF</a></p>&mdash; Gaël
 Métais (@gaelmetais) <a
 href="https://twitter.com/gaelmetais/status/564109775995437057">7 February
 2015</a></blockquote>
-<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+<script src="https://platform.twitter.com/widgets.js" defer></script>
 
 A confusing mess of unrelated selectors all grouped together via coincidence as
 opposed to reason. This fragments style information across your project, creates

_posts/2017-02-08-code-smells-in-css-revisited.md

@@ -227,6 +227,8 @@ Rupert](https://twitter.com/davatron5000):
   — Dave Rupert (@davatron5000) <a href="https://twitter.com/davatron5000/status/829091851651149824">7 February, 2017</a>
 </blockquote>
 
+<script src="https://platform.twitter.com/widgets.js" defer></script>
+
 If we need to style something differently because of its context, where should
 we put that additional CSS?
 

_posts/2018-04-02-my-digital-music-setup.md

@@ -41,6 +41,8 @@ of a ‘dubious’ copy of this track? I’ll donate £25 to a charity of your c
 href="https://twitter.com/csswizardry/status/975337747169857537">18 March,
 2018</a></blockquote>
 
+<script src="https://platform.twitter.com/widgets.js" defer></script>
+
 If you want to listen to the track—of course you do, it’s stunning—then you’ll
 have to make do with the YouTube version. Couple it with some good headphones
 and a decent amount of volume and you’ll still get the picture:

_posts/2019-05-31-self-host-your-static-assets.md

@@ -64,6 +64,8 @@ Roberts (@csswizardry) <a
 href="https://twitter.com/csswizardry/status/1651599057608142849?ref_src=twsrc%5Etfw">27
 April, 2023</a></blockquote>
 
+<script src="https://platform.twitter.com/widgets.js" defer></script>
+
 ## Risk: Service Shutdowns
 
 A far less common occurrence, but what happens if a provider decides they need

_posts/2022-03-28-optimising-largest-contentful-paint.md

@@ -39,6 +39,9 @@ Let’s go.
 
 ## Solve Everything Beforehand
 
+_**Struggling to hit 2.5s?** [Work with me one-to-one and deliver a faster
+LCP](/consultancy/)._
+
 Let’s start with the easy stuff. LCP is a milestone timing—it measures…
 
 > …the render time of the largest image or text block visible within the
@@ -314,6 +317,8 @@ it.]</p>&mdash; Harry Roberts (@csswizardry) <a
 href="https://twitter.com/csswizardry/status/1436361516534620168?ref_src=twsrc%5Etfw">10 September
 2021</a></blockquote>
 
+<script src="https://platform.twitter.com/widgets.js" defer></script>
+
 This means that `background-image` LCPs are requested at the very last moment,
 which is far too late. We don’t like `background-image` LCPs.
 

_posts/2023-07-01-in-defence-of-domcontentloaded.md

@@ -420,6 +420,8 @@ tiny ones:
 
 <blockquote class="twitter-tweet"><p lang="en" dir="ltr">As a rule, RTT (α) stays constant while download time (𝑥) is proportional to filesize. Therefore, splitting one large bundle into 16 smaller ones goes from 1α + 𝑥 to 16α + 16(0.0625𝑥). Expect things to probably get a little slower. <a href="https://t.co/c0hEsIAwKq">pic.twitter.com/c0hEsIAwKq</a></p>&mdash; Harry Roberts (@csswizardry) <a href="https://twitter.com/csswizardry/status/1352402710688133122?ref_src=twsrc%5Etfw">21 January, 2021</a></blockquote>
 
+<script src="https://platform.twitter.com/widgets.js" defer></script>
+
 My advice in this case is to tweak their build to output maybe 8–10 bundles and
 re-test from there. It’s important to balance bundle size, number of bundles,
 and caching strategies, but it’s clear to me that the issue here is overzealous