Brendan Tully0 Comments
October 7, 2026
Every tool a marketing team adds to a website arrives as a third-party file: Google Analytics, Tag Manager, the Facebook pixel, an opt-in tool, click fraud protection for paid campaigns. Each one makes the page take longer to finish loading, and the person who waits is the visitor who just clicked your ad or your search result. Removing tags is not always possible. Preconnect is a low-risk way to make the ones you keep cost less time.
The video uses a waterfall test of a real Australian site to show where the time goes on third-party files, then shows how a few preconnect hints in Autoptimize bring those connections forward in the page load.
Files from your own server or CDN usually arrive in tens of milliseconds. Marketing services are not built around your page speed, and many are hosted in the United States, so visitors elsewhere pay for the distance on every new connection. In the video’s test, run from Australia, ClickCease took 169 ms just to look up its domain and 856 ms in total. A marketing automation script from api.autopilothq.com took 824 ms.
There is an irony in that. A click fraud tool is installed to protect ad spend, yet it was adding close to a second to the very pages that spend is buying traffic for.
Before any file moves from a new domain, the browser has to do three things: look up the domain (DNS), open a connection and negotiate SSL. Normally that happens when the browser reaches the tag in the HTML. A preconnect hint in the page head tells the browser to do those steps immediately, in parallel with everything else. The vendor’s server is no faster, but its setup time now overlaps with work the browser was doing anyway.
Run a waterfall speed test on your most important landing pages, not just the homepage, and look for third-party rows where DNS, connect and SSL take up a large part of the bar. Candidates mentioned in the video:
Keep the list to hosts that load on most pages. A preconnect for a service used on one page opens a connection that goes unused everywhere else.
In Autoptimize, the field is “Preconnect to 3rd party domains” on the Extra tab. Enter each host in full with https://, save and clear the cache. Other optimisation plugins such as Perfmatters have an equivalent setting, and a developer can add the tags to the theme head by hand.
https://
Whoever manages Google Tag Manager should be part of this. When a new vendor tag goes live through Tag Manager, its host may be worth adding to the list, and when a vendor is dropped, its preconnect should go too.
Preconnect makes third-party tags cheaper; it does not make them free. While you are looking at the waterfall, check for tags nobody uses any more: an old pixel from a past agency, a trial tool that was never removed, two copies of the same live chat or analytics script. Removing a tag saves its whole cost, which no hint can do. Then preconnect the ones that earn their place.
Comments are closed.