Multiple third-party origins but no preconnect/dns-prefetch hints
Every time a page loads content from another domain, such as Google Fonts, an analytics script, or a payment provider's iframe, the browser has to look up that domain, connect to it, and negotiate a secure connection before anything can be fetched, costing 200-400 milliseconds per new origin. Preconnect and dns-prefetch hints let the browser start this process early, in parallel with the rest of the page loading. This site loads from multiple third-party origins without either hint present. Each missing hint means visitors wait longer than necessary for fonts, analytics, or embedded tools to become usable, particularly noticeable on slower mobile connections where every extra connection setup step is felt more strongly by the visitor waiting for the page. Your developer should add preconnect hints for the three to five most critical third-party origins in the page's head, for example a preconnect link to fonts.googleapis.com. This pairs especially well with above-the-fold web fonts and analytics. Budget about ten minutes.
Why this matters
Each missing hint means visitors wait longer than necessary for fonts, analytics, or embedded tools to become usable, particularly noticeable on slower mobile connections where every extra connection setup step is felt more strongly by the visitor waiting for the page.
How to fix it
Your developer should add preconnect hints for the three to five most critical third-party origins in the page's head, for example a preconnect link to fonts.googleapis.com. This pairs especially well with above-the-fold web fonts and analytics. Budget about ten minutes.