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.

ok – try:
for quick css:

.all_sort_button, .all_sort_button + .text-sep {
  display: none !important;
}

for child-theme functions.php:

function open_second_sort_option(){
?>
<script>
window.addEventListener("DOMContentLoaded", function () { 
(function($) {
    setTimeout(function() {
        $('.avia_show_sort:nth-of-type(2)').trigger('click');
    }, 300);
})(jQuery);
});
</script>
<?php
}
add_action('wp_footer', 'open_second_sort_option');

maybe you have to increase the time to wait til click is triggered

If you need that only on specific pages or specific masonries etc. give a custom class to the element and use it in the selector.

on that php you mentioned – the if-clause:
if( strpos( $link[1], '@' ) !== false
eachtime for $link[0] == 'manually'
we had 3 times that check.

and maybe it is better to replace it to:
return 'mailto:' . antispambot($link[1],1);
because i do not see any difference in the DOM when applying it without. Or does even the sourcecode show then transformed html entities
with the 1 i see:

the shortcode i have for emails inside text blocks :

function obfuscate_emails($atts, $content = null) {
    if (!is_email($content)) {
        return;
    }
    return '<a href="mailto:' . antispambot($content,1) . '">' . antispambot($content) . '</a>';
}
add_shortcode('email', 'obfuscate_emails');

i had to use then as [email] (Email address hidden if logged out) [/email]

can you try:

.responsive #top #wrap_all {
    background: #000 !important;
}

and i think this is set on default to #fff – that can cause the issue.

for the moment of starting transition this might be visible. Give it a try
Or if you are using curtain effect footer and try to force scroll on at the end of the page – that bg will be seen.
hamburger slide out etc. pp

PS: sometimes ( f.e. with fixed header ) the background of #main is visible

so try:

.responsive #top #wrap_all {
  background: #000 !important;
}
.responsive #top #main {
  background: transparent !important;
}

a good multilang plugin should set those links in the head section. WPML does in this way ( depending on your choice – how to handle the multilang sites – as addendum – as subdomain or maybe as extra domains )
f.e.:

<link rel="alternate" hreflang="en-us" href="https://your-domain.com">
<link rel="alternate" hreflang="de-de" href="https://your-domain.com/?lang=de">

so inspect your head section if those entries are made.

but there are 3times settings for '@'
do you think it is best to replace all of them ;)

but this is only for manually inserted Links in ALB Elements?
Have you tested that ?

open for example: https://www.colorzilla.com/gradient-editor/
copy the given gradient code from my code: linear-gradient(to bottom, rgba(0,0,0,0.8) 10%,rgba(0,0,0,0.1) 30%);
under the preset gradient there is a “button” import css –
enter the code and click “import”
now you can play with the settings.

the “to bottom” means the linear gradient is from top to bottom – so the left value is the top color.
the rgba value is the color with an opacity e.g.: rgba(0,0,0,0.8). is a black with 80% opacity
the value after the rgba is the position : here 10% ( top to bottom) from the top.

yes – but the custom-class is then on the section container ( that is in the DOM Tree higher than the avia-slideshow class)
f.e. dark-overlay-on-section

.dark-overlay-on-section .avia-slideshow .av-video-slide .mejs-mediaelement:after {
  content: "";
  position: absolute !important;
  width: 100%;
  height: 100%;
  top: 0;
  left: 0;
  background: linear-gradient(to bottom, rgba(0,0,0,0.75) 25%,rgba(0,0,0,0.1) 70%);
  background-size: cover;
  background-repeat: no-repeat;
}

But he wrote that even css code does not work correctly. So – my guess is that there is a generall installation error.
the code he quoted above corresponds to what Google itself outputs as embed code. Therefore, this error can be excluded.

It depends a bit on what kind of header you have and what you want to achieve.
Is it a fixed header on desktop view? Where is your navigation etc.?
the header_meta should stay fixed in mobile view – and not scroll away…

or – have a look into the docu : https://kriesi.at/documentation/enfold/icon/#download-fontello-or-flaticon-icons-included-in-enfold-demos

is wp-block-heading a class ? Where’s the dot before?
next – you only want to change h1 headings with that custom class and all h2 ?