Switch Calendley preconnect to dns-prefetch

It turns out that `c839db0a` wasn’t a simple CORS thing (are they
ever?). Because `calendly.com` doesn’t response with an
`Access-Control-Allow-Origin` header, we can’t reuse the same
CORS-enabled connection that our `preconnect` opened. In fact, we can’t
use `preconnect` at all without forcing a wasted connection, a lost
round trip, and opening a final connection JIT and in-band. In this
case, `dns-prefetch` is actually faster as it avoids waste.

Author: csswizardry

contact.md

@@ -17,7 +17,7 @@ Or book a free call:
 
 <div class="calendly-inline-widget" data-url="https://calendly.com/csswizardry/30min?background_color=f9f9f9&text_color=333333&primary_color=f43059" style="min-width:320px;height:700px;margin-bottom:1.5rem;"></div>
 <script src="https://assets.calendly.com/assets/external/widget.js" async fetchpriority=high></script>
-<link rel="preconnect" href="https://calendly.com" crossorigin>
+<link rel="dns-prefetch" href="https://calendly.com">
 
 - - -
 

performance-audits.md

@@ -141,4 +141,4 @@ triage the extent of performance issues with your site.
 
 <div class="calendly-inline-widget" data-url="https://calendly.com/csswizardry/fix-it-fast?background_color=f9f9f9&text_color=333333&primary_color=f43059" style="min-width:320px;height:700px;margin-bottom:1.5rem;"></div>
 <script src="https://assets.calendly.com/assets/external/widget.js" defer fetchpriority=high></script>
-<link rel="preconnect" href="https://calendly.com" crossorigin>
+<link rel="dns-prefetch" href="https://calendly.com">