i can see that enfold uses this font ( register-backend-styles.php ) if you are working on general styling by predefined color schemes ( black or blue/yellow)
but if you do not have this in a css or in enfold / advanced styling – this should not be loaded.
Anyway – if all of your fonts are loaded over an own server ( manually socalled) and not by google – you can do this into functions.php of your child-theme:

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

on class-style-generator.php you can see the function print_extra_output and that it is for google font loading (line 355)

to realy get rid of the last rest you can use this plugin: remove-google-fonts-references
this works still with newest enfold

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

and if you see gtmetrix results :
click to enlarge

you see that the results are not so bad

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

And once again – for your background-image in the right cell !
on mobile this is nearly gone. if you like to show something ( the image ) you can setup a min-height – or do a whitespace hr in it with a given height

well you can have a different landing page for that indeed:
just do this to your functions.php of your child-theme:

add_action( 'wp_head', 'landingpage_for_mobile', 10 );
function landingpage_for_mobile() {
?>    
<script>
	if (window.location.pathname == '/' && jQuery(window).width() <= 480) {
	   window.location = "/impressum/";
	}
</script>
<?php
}

Übrigens: solange du an dem Layout rumschraubst, würde ich das merging abstellen.
Das verhindert zusätzlich zu den Browsercache das Überprüfen der Änderungen.
So muss man immer wieder die Teile neu anlegen lassen.

test it yourself – nothing can go wrong with it

by the way – a container can have more than one background-image:
https://webers-testseite.de/multiple-background-images/

by the way :lol
be creative: http://elrumordelaluz.github.io/draGGradients/

#top .av-siteloader-wrap {
    background: radial-gradient(circle at 89.99% 7.99%, #7e75ff, transparent 67%),radial-gradient(circle at 49.9% 49.64%, #73ffab, transparent 61%),radial-gradient(circle at 8.98% 17.50%, #ffff4a, transparent 58%),radial-gradient(circle at 3.98% 90.04%, #ff94fb, transparent 67%),radial-gradient(circle at 93.01% 92.01%, #ff722b, transparent 61%),radial-gradient(circle at 50% 50%, #ffffff, #ffffff 100%)
}

ein link zu dem Kalender wäre schön.
Wenn dieser im Private Content ist, musst du auf einen Mod hier warten.

display:none elements are not in the render tree at all.
visibility:hidden is a different thing!

display:none Elemente sind zwar im DOM und im CSSOM vorhanden, die Zeit die für die Performance allerdings wichtig ist, ist das Rendering der Seite. Diese Elemente werden aber dann nicht gerendert.
Schau mal hier : https://developers.google.com/web/fundamentals/performance/critical-rendering-path/render-tree-construction?hl=de
und folgende Seiten.

Really friendly – thank you for the answer; unfortunately it is not usual here that a positive approach to a solution is answered quickly.
Your welcome!

PS : this was the solution for the first (left grid cell – .flex_cell.avia-builder-el-first ) –
you could transfer this solution to the right one yourself ? ( .flex_cell.avia-builder-el-last )
but then it will be better to have a unique class for those grid-row element
maybe ( special-grid-row-left and special-grid-row-right) etc. –

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

the thing is that the tooltip window (hotspot image on the bottom of my link) only arises when hovering the tooltip
it does not exist in the DOM till hovering – so my code here: Link has no influence on it.
Even the DOMNodeInserted function does not work here

so we can force the links inside the inner_tooltip to open in lightbox by this snippet in functions.php of the child-theme:

add_action( 'wp_footer', 'ava_tooltip_script' );
function ava_tooltip_script() {
	?>
	<script type="text/javascript">
	(function($) {
		function b() {
			$(".inner_tooltip a").magnificPopup({
	    		type: 'iframe',
	    		mainClass: 'avia-popup mfp-zoom-in',
	       	});
		}
		$(window).load(function() {
			b();
		});
	})(jQuery);
	</script>
	<?php
}

so now see page: https://webers-testseite.de/image-with-hotspost-linking-to-youtube-in-iframes/

zunächst sind das ja nur beispiele – ich denke du wirst keine Seite 6, 42, oder 54 haben.
Aber was ich oben schrieb – der fehler ist: ohne if kein elseif.
wenn du es dahingehend änderst wird WordPress nicht mehr meckern:

add_filter('avf_logo','av_change_logo');
function av_change_logo($logo){
    if ( is_page( array( 6, 42, 54 ) ) ) {
    	$logo = "http://www.domain.com/wp-content/uploads/logoforpage22.jpg"; 
    }
    return $logo;
}

hast du denn einen if in deinem Code drin?
Ein elseif macht nur sinn, wenn ein if vorhanden ist.

Du kannst es pro Seite entscheiden- wobei es für dich gut wäre die Page-id zu kennen:

Dieses hier in die functions.php deines Child-themas:

Es soll dir verdeutlichen wie es gehen kann mit den if clauses. – wobei du Seiten auch als array nutzen kannst
also da zB Seite 6, 42 und 54 erhalten dann ein logo –
du kannst alles was WordPress an conditional tags bereit hält nutzen: Link

add_filter('avf_logo','av_change_logo');
function av_change_logo($logo){
    if( is_page(21) ) {
    	$logo = "http://www.domain.com/wp-content/uploads/logoforpage21.jpg"; 
    }
  
    elseif ( is_page( array( 6, 42, 54 ) ) ) {
    	$logo = "http://www.domain.com/wp-content/uploads/logoforpage22.jpg"; 
    }

    elseif ( is_page() && !is_page(1307) )  {
    	$logo = "http://www.domain.com/wp-content/uploads/logoforpage23.jpg";  
    }
    return $logo;
}

wenn man wiedersprüchliche Aussagen hat wie jetzt die da unten – muss man sehen ( da würden alle Seiten außer Seite 1307 das logo 23 bekommen)