I take my example page offline again. It was probably not that urgent.

Yes – but that is sometimes difficult to realize. A child-theme header.php or footer.php is often easier to manage.
You only need to check after updates if there are significant changes in their parent themes files. Therefore, changes should be well documented (possibly by comments inside).

There is one small catch – both Nikko’s and my solution. Masonries that load further elements with the More Link are not affected by this. You would then have to add attributes, e.g. with MutationObserver, at the moment of entry into the DOM.

f.e. ( in this case for all links in a Masonry )

function open_masonry_entries_in_new_tab(){
?>
<script>
(function($) {
  MutationObserver = window.MutationObserver || window.WebKitMutationObserver;
  var observer = new MutationObserver(function() {
    $("a.av-masonry-entry").attr("target", "_blank");
  });
  observer.observe(document, {
    subtree: true,
    childList: true
  });
})(jQuery);
</script>
<?php
}
add_action('wp_footer', 'open_masonry_entries_in_new_tab');

have a look if you got a child-theme header.php.
This file in particular has undergone major changes over time. In this case, you should remember why you created a child theme header.php. You should then apply these steps to an up-to-date header.php and upload it instead.

Es gibt einen hook, in den du ein Bild oder eventuell besser noch ein svg setzen könntest: wp_body_open
Es sollte nicht schwer sein das Bild so mit einem z-index zu belegen, der dann den eigentlichen Inhalt überdeckt. Eine getimete Animation der Transformation sollte dann auch möglich sein.

Also für die child-theme functions.php:

add_action('wp_body_open', function() {
if(is_front_page()){
  echo '<div class="body-overlay"></div>';
}
});

für das Quick css:

.body-overlay {
  position: fixed;
  display: block;
  width: 100vw;
  height: 100vh;
  top: 0;
  left: 0;
  z-index: 5000;
  animation: transformUp 3s ease 2s forwards;  /** for shortform see: https://www.w3schools.com/cssref/css3_pr_animation.php ***/
}

.body-overlay {
  background-image: url(/wp-content/uploads/test-london.jpg);
  background-repeat: no-repeat;
  background-size: cover;
}

@keyframes transformUp {
   0% {
       transform: translate(0px, 0px);
   }
   100% {
       transform: translate(0px, -102vh);
   }
}

see: https://webers-testseite.de/

yes this works for me too!
even on sortable toggles : https://webers-testseite.de/accordion/

so this bug is my fault – one should always check first if something set has to be removed – before adding a new code.
II have tested it, but not stress tested. Means very lush content and fast clicking the toggle headings.
So – although the internet is full of suggestions about this Chrome bug regarding clearing – deleting the floating property is the solution.

I did not see on your page why the toggles looses their focus – on click all moves to the top. – this is not standard behavior!

Can you try to deactivte the total cache – refresh all cachings and merging of enfold.

wow das ging schnell:
ist online – ps habt ihr das noch schnell eingebaut! wahnsinn

fixed: CSS for chrome bug accordion toggles do not close properly and leave white space

if you download the font from google there is the variable font inside too. The static fonts are in an extra folder. Did you upload the whole zip to enfold?

In this static folder there are condensed styles too!
_______
But one piece of advice from me is: don’t install too many fonts. The performance of the website will suffer.
As I mentioned in another topic, you should think carefully about whether you should include italic font styles at all. Especially with sans-serif fonts, the slanting of the font on the browser side is often almost identical to the italic font style.

If you can do without the support of older browsers, then the variable font might be the better alternative anyway. There, all font styles would be included, and the memory usage is much lower. ( 1,1Mb versus 4,8MB ) .

Next offer modern font style types as woff2. The Google download do offer only ttf. You can upload it with the zip too – but the woff2 will be loaded.

Try this zip ( with only light, regular and bold style (woff2 and ttf) ) – this would be a good way for the most of the websites:
https://webers-webdesign.de/Open-Sans.zip

Delete your uploaded font and use it instead.
think of to use them – these uploaded fonts are at the end of the dropdown list on font setting options

can you try

#top .av_toggle_section {
    clear:both
}

thats indeed a chrome thing only!

ok – as mentioned above – that is much easier because this element got an option to tell the frontend what opens first on load.
i have never seen the sorting option here – sorry.
if you like to get rid of the separator aswell – add to mikes code the first tag-separator:
( first-child will work too )

.togglecontainer .taglist a:first-of-type,
.togglecontainer .taglist .tag-seperator:first-of-type {
  display: none;
}

Sorry, I did not see that you were talking about the accordion. But we are talking about which folding element? the accordion has by default an option to choose the opening tab. There are no sorting options. You mentioned partner logos. On this element we do not have sort options. So my suggestion is that you are talking about Masonry or Portfolio Grid. So please clarify your request.

hast du mal versucht in der Google Search Console zu schauen was die melden:

Anmelden und nachschauen für die Domains.
Ich melde dort alle Seiten die ich verwalte manuell an. Hinterlege dann dort die Sitemap. Und stoße die erste Indexierung dann manuell an.

_________

Have you tried looking in Google Search Console to see what they are reporting?
Login and lookup for the domains.
I manually register all the pages I manage there. Then I store the sitemap there. And then manually trigger the first indexing.

https://search.google.com/search-console

PS : du darfst nicht erwarten das die Bots direkt nach erstellung einer Webseite drübergehen. – daher ist oft Geduld nötig.
Wenn du SEO mäßig gut aufgestellt bist und die Seite performant ist, sollte es nicht allzulange dauern bis die Ergebnisse da sind. – wie gesagt sitemap hinterlegen und index anstoßen hilf hier natürlich.

________

PS: you must not expect the bots to go over immediately after creating a web page. – Patience is therefore often necessary.
If you are well positioned in terms of SEO and the page is performant, it should not take too long until the results are there. – As I said, storing a sitemap and initiating an index helps here, of course.