Hi Clemens,
TSF doesn’t append any dns-prefetch
nor preconnect
elements to the page source.
Please check in with any advertising-plugins you have enabled — dwin1 seems to be related to Awin, which is an affiliation-advertising platform. Although unlikely, another plugin or theme may be outputting these tags in a nefarious fashion, much as the Astra theme did.
Hi Sybre,
if I output the HTML-code in the console I get the following result:
<!-- / The SEO Framework von Sybre Waaijer | 1.02ms meta | 0.53ms boot -->
<link rel='dns-prefetch' href='//static.klaviyo.com'/>
<link rel='dns-prefetch' href='//www.dwin1.com'/>
<link rel='dns-prefetch' href='//kit.fontawesome.com'/>
<link rel='dns-prefetch' href='//cdn.jsdelivr.net'/>
<link rel='dns-prefetch' href='//fonts.googleapis.com'/>
<link rel='dns-prefetch' href='//s.w.org'/>
<link rel="alternate" type="application/rss+xml" title="PHYSTINE - Natur.Pflege » Feed" href="https://phystine.com/feed/"/>
<link rel="alternate" type="application/rss+xml" title="PHYSTINE - Natur.Pflege » Kommentar-Feed" href="https://phystine.com/comments/feed/"/>
Why is it that the DNS-prefetching is to be found below The SEO Framework description then?? The dwin.1com must not be prefetched according to AWIN.
I have no clue where this prefetching could come from if it is not from TSF like the source code says…
Thank you very much for your support!
Best regards
Clemens
Hi Clemens,
TSF’s output is between these two tags:
<!-- The SEO Framework von Sybre Waaijer -->
TSF's output is here...
<!-- / The SEO Framework von Sybre Waaijer | 1.02ms meta | 0.53ms boot -->
Anything before or after those tags are from other plugins, WordPress, or the theme. With the exception of our Cord extension, which needs to output its analytics scripts at specific points of the page.
Let’s go through the tags you mentioned:
klaviyo: Probably some kind of form generator, probably added by your theme.
dwin1: Some affiliate linking system (inserted by klaviyo’s form generator), probably added by your theme.
fontawesome: A font system to display custom glyphs, like the social icons in your header, probably added by your theme.
jsdelivr: Used to provide scripts for the “Slick” carousel, probably added by your theme.
googleapis: Used to deliver the font you installed via the “DSGVO All in one for WP” plugin.
w: WordPress’s CDN that enables native emoji support on any WordPress site.
The feeds are also generated by WordPress.
I hope this helps! 🙂
Hi Sybre,
I acknowledge that this is not a TSF topic. Excuse my missing knowledge here :).
Thank you very much for your support and explanation & have a good evening 🙂