but that’s already complaining on a very high level, isn’t it? Gtmetrix values of nearby 100% ;)
A TTBF at 83ms – that are top values – so what ?
As I said, I would rather worry about the compliant GDPR implementation.

for example now – my results on top are nice too – but why does it wait so long after everything is loaded to load the last 30kb of the favicon? a good 200-300ms pass before loading the last file. And this caused a “bad” TTLB value.

@cocoagroup : did you test the SVGator Plugin ?

sadly no way to go that quick and dirty solution.

• This reply was modified 2 years, 7 months ago by Guenni007.

these are not identical the same fonts:

memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTSumu1aB.woff2
memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-muw.woff2

if you upload those files to : https://wakamaifondue.com/beta/
you see that the first one is a open sans regular (45kb) – the second one is too a open sans regular but with different localisation:
Catalan, Marshallese, Macedonian, Romanian; Moldova, Navajo, Romanian, Serbian, Undetermined; North American Phonetic Alphabet and Undetermined; International Phonetic Alphabet.
It only has special cyrilic characters:

Why there is that additional character set loaded – i could not imagine.

Next – i will look now to kriesi.at – but i guess that these three fonts are the font-weights light, regular and bold.

where do you exactly see that f.e. kriesi.at or your experimentkrewerd.nl does load Open+Sans twice
there is once the script that decides if the font could be loaded – if there is a consent.
so – if (cookie_check && !silent_accept_cookie) … and inside a lot of if clauses that has allow_continue = false next – only if (allow_continue) = true then load font.
the next line in head it loading the font itself.

So what you could say is that kriesi and your site do not respect the cookie consent setting. Or you have set them incorrectly. Or when I look at Krisie.at, no value is placed on GDPR. Because without having rejected or agreed to anything, a huge list is displayed which are all not GDPR-compliant.

_________

The safest way to deal with the font issue in terms of the GDPR is to host it yourself.
And that’s exactly what this code from Ismael or the alternative filter from me is for. It prevents the embedded handling of Enfold with Google Fonts.
Then you had to upload via Enfold Font Manager your Open Sans Font – and choose that font ( selfhosted Fonts are at the end of the fontlist ) in Enfold Font Options dialog.

first: can you remove this from ismael – i used that code long time to do the same thing – but i recognised on some pages that i update to the latest php Versions that it might come into conflict.

function my_output_google_webfonts_script( $activate ){
  return false;
}
add_filter( 'avf_output_google_webfonts_script', 'my_output_google_webfonts_script', 10, 1 );

instead of:

function enfold_customization_switch_fonts() {
    global $avia;
    $avia->style->print_extra_output = false;
}
add_action( 'init', 'enfold_customization_switch_fonts' );

_________
of topic for the one public link:
second: – besides the page link (i do not see as participant) where your fonts are loaded : i see on the other page that there is no Consent to any of your features you use for that page.

third: i can not see any @font-face rule in your css – did you upload the open sans font to the font-manager of Enfold ?

next: the google maps could not cause that font-loading with open sans. Google Map loads “Roboto” and “Google Sans Text”
maybe one of your other Google Things ( Analytics etc. )
if you want to hamper loading of these fonts for maps :
add_filter( 'avf_gmaps_no_google_fonts', '__return_true' );

$(window).load(function() { is outdated since jQuery 3

function inline_popup_enabler(){
?>
<script>
(function($){
	$(window).on('load', function(){
		$('.inline_popup').magnificPopup({
			type:'inline',
			midClick: true,
			disableOn: 100,
		});
	});
})(jQuery);
</script>
<?php
}
add_action('wp_footer', 'inline_popup_enabler');

is there a link to your gallery – or is there a page of the demo that is similar to your gallery? https://kriesi.at/themes/enfold-shop/

looking to your svg – there are a lot of script inline. if you insert your svg code via codeblock to enfold – the animation will work.
on an img file – i guess the script part will not work as expected.
as background-image – this will be lost too. On Svgator you can export your animation to gif – maybe that is an alternative vor you.
By the way : next Enfold will offer lottie file support. These are svg / json “images” you can insert to Enfold.

have a look if you got a css rule in your css like:

#footer {
  background-color: var(--enfold-header-color-bg);
}

maybe a mod knows why on some animations the “trick” will not work.
it sometimes only removes not all classes from all ( each ) observed element.

function refresh_enfold_keyframe_animations() {
?>
<script type="text/javascript">	
	const hiddenElements = document.querySelectorAll('.av-animated-generic');
	const observer = new IntersectionObserver((entries) => {
	    entries.forEach((entry) => {
	        if (!entry.isIntersecting) {
				entry.target.classList.remove('avia_start_animation', 'avia_start_delayed_animation');
	        }
	        else {
	        	return;
	        }
	    })
	})
	hiddenElements.forEach((element) => observer.observe(element));
</script>
<?php
}
add_action('wp_footer', 'refresh_enfold_keyframe_animations', 9999);

see: https://enfold.webers-webdesign.de/category-header/

on to it is not even half n-dash it is just nearby the stroke width.

do you really believe that there is a whitespace ?
This seems to be normal typographic behavior – for example : Carmen Sans ( not the same font but nearby ) – see first two lines without whitespace after break
and at the end with a whitespace:
( i just activated those lines that you can see the alignment better )

You see that a blank space in typography is a quarter square. ( half n-dash space )
this is like fonts in that the baseline of curves is always slightly below the straight lines of a font.

try:

#top .post-entry.post-entry-8977 * {
  font-family: "dkbeuclid", Helvetica, Arial, sans-serif !important;
}

the other sections – and footer etc are untouched on that rule – otherwise take #top.page-id-8977

Die Body Schrift wird im Allgemeinen über die Schriftart, die du in Enfold gewählt hast definiert.
Die Schrift, die du bei : Allgemeines Styling – Schriften gewählt hast geht als z.B
body.roboto … in das css child.css ein:

body.roboto {
  font-family: 'roboto';
}

Wenn du es also global ändern möchtest – Dort würde ich es setzen – ohne es mit css zu versuchen.
____________________

Solltest du jetzt auf einer bestimmten Seite nur diese globale Setzung überschreiben wollen, so musst du dort diese Anweisung überschreiben. Also entweder die andere Schrift auf !important dort setzen oder eine höhere Spezfität der Regel haben.
Wizigerweise würde es denk ich reichen, wenn du statt body #top nimmst also:

#top.page-id-123.roboto {
  font-family: “gineso-condensed”, sans-serif;
}

oder einfacher, weil es wohl ausreicht :

#top.page-id-123 {
  font-family: “gineso-condensed”, sans-serif;
}