did you copy&paste that code? because if it is your page ( and your nick is very informative ) than a code like:

@media only screen and (max-width: 1023px) {
  #top #header .av-main-nav > li.menu-item  {
    display: none!important;
  }
  #top #header .av-burger-menu-main {
    cursor: pointer;
    display: block!important;
  }
  .responsive #top #header .av-main-nav #menu-item-search {
    display: block !important;
  }
  .responsive #top #header .av-main-nav #menu-item-search  > a {
    font-size: 24px;
  }
}

will work in dev tools. So if you realy entered the correct code – then it might be a caching issue that you can not see the changings. So refresh all caches of such tools – and refresh on Enfold on Performance Tab just at the bottom: “Delete Old CSS And JS Files?”

1023px seems to be a good value – because on the ipad Pro 12.9 inch – (1024px) the text menu is still visible and is not above the logo.

PS: i added the code to show the search icon aswell on burger active and with a little bigger icon.

to make sure that you have used the correct characters everywhere, please post the code in the code tag.

Next: what should the code do? isn’t it possible to remove all flags by the plugin itself? WPML – Languages – Menu language switcher

Where did you get this code snippet?

add_filter( 'wp_nav_menu_items', [ new avia_WPML, 'handler_append_lang_flags' ], 9999, 2 );

even if i write it this way :

add_filter( 'wp_nav_menu_items', array(new avia_WPML(), 'handler_append_lang_flags') , 9999, 2 );

it quits with errors.

i try to create now a better automator script – just wait a few minutes! …

based on: https://stackoverflow.com/questions/10924236/mac-zip-compress-without-macosx-folder/#answer-47880361

https://webers-testseite.de/zip-it.zip

Unfortunately OSX reports that the origin of the programme cannot be verified. This is due to the SIP of OSX.
( System Integrity Protection (SIP) in macOS ). For those who have confidence in me, you can declare the exception in the system settings – privacy and security – at the bottom of the list.

For those who do not …
i had to describe now how you will get that for your desktop: …

i can see that too! So must be a caching problem.

By the way: if you do not need bigger menu-items in hamburger menu – you can make that overlay smaller ( goto Main Menu – Burger/Mobile Styliing : “Flyout Width”) try 200px

maybe it will be the easiest way to not show the sub-menu on different pages ;)

#top:not(.page-id-41084) .sort.menu-item .sub-menu {
  display: none !important;
}

you can do that via font-size and either padding or min-width:

.avia_ajax_form .button {
  padding: 16px 50px;
  font-size: 1.4em;
  min-width: 200px;
}

But this works only for: non-ALB generated Posts / even Portfolios are untouched.

what i can see on that page is the layer-slider setting – and on my iPhone this is still there (the layerslider).

here is a css solution – but not with sort option in navigation – that is – as ismael mentioned a lot of work
PS: maybe the sticky option is too much.

https://webers-testseite.de/masonry-blog/

and to have no influence on other masonry pages – it might be good to stay site-specific.

i could not imagine that a logo is the reason for bad LCP Values. (maybe if you use a svg Logo with embedded image gradients (like Instagram now did) ) a svg with 10MB 🙂‍↔️ (https://about.meta.com/brand/resources/instagram/instagram-brand/)

if you got for example a bigger advanced slider – that could cause it
on pagespeed insights – go to the diagnostic part and open the LCP part to see what is responsible for that.

this seems to work:

function avf_custom_masonry_loop_prepare( $key, $entries ) {
	if($key['post_type'] !=  'attachment') {
		$separator = ' / ';
		$updated_date = get_the_modified_date( get_option('date_format') , $key['ID'] );
		$output .= '<span class="updated-date meta-color av-masonry-date">'.$separator.'Updated on: ' . esc_html( $updated_date ) . '</span>';
		$key['text_after'] .= trim( $output, $separator  );
	}
    return $key;
}
add_filter( 'avf_masonry_loop_prepare', 'avf_custom_masonry_loop_prepare', 10, 2 );

i do not know why the positiv check does not work ( case post or portfolio)

Edit :
i thought that this

if($key['post_type'] ==  'post' || $key['post_type'] ==  'portfolio') {
// could be shortend to:
if($key['post_type'] ==  ('post' || 'portfolio')) {

first one works – shortform not

Yes – but Masonry Galleries are influenced too. I do not want image galleries to be part of that additional info.
Only Masonry Entries should be doing that. I tried $context == 'av_masonry_entries' but again with no success.
https://webers-testseite.de/image-masonry/

did you enter this in the functions.php of the parent theme? (unfortunately all this would be lost again after the next update).
this is possible – but my recommendation is to use a child theme.

Next Question: did you set the fonts on General Styling – Fonts : ( on uploaded Fonts) ?

https://kriesi.at/support/topic/menu-on-one-page-is-bolder/
???
der variable font den du jetzt hast arbeitet doch korrekt!

War es damit nicht gelöst?
Du hattest wohl offensichtlich bei der Erstellung des Templates die Schrift mit ausgewählt. Mein Rat war es dort auf default (nutze die Themenschrift) zu lassen. Durch das Nachladen der Montserrat Schrift nur auf dieser Seite (und dort wurde der bold font mitgeladen) erschien dann nur dort auf der Seite die Schrift im Menü bold. Auf den anderen Seiten wurde diese Schrift nicht nachgeladen, weshalb nur die Montserrat light zur Verfügung stand.

Meine Empfehlung deshalb war: im Plugin die Standard Schrift nutzen ( welche dann eine sauber konfigurierte Montserrat des Systemes wäre )
Und die Montserrat vernünftig zippen, und hochladen.

_____________

Wasn’t that the solution?
You had obviously selected the font when you created the template. My advice was to leave it at default (use the theme font). By reloading the Montserrat font only on this page (and the bold font was also loaded there), the font then only appeared there on the page in the bold menu. This font was not loaded on the other pages, which is why only the Montserrat light font was available.

My recommendation was therefore: use the standard font in the plugin (which would then be a cleanly configured Montserrat of the system)
And zip the Montserrat properly and upload it.