In fact, you could do it with a hook as well. – but i would use a wordpress hook on that.
The main navigation menu theme_location is avia.
( you see that you can use that hook also to other menu locations :
avia(main-menu), avia2( top-menu), avia3(footer-menu) )

function add_cart_icon_to_main_menu( $items, $args ){
  if ($args->theme_location == 'avia'){
    $cartLink = '<li class="menu-item menu-item-cart menu-item-avia-special" role="menuitem"><a aria-label="Cart" href="#" rel="nofollow" aria-hidden="false" data-av_icon="" data-av_iconfont="entypo-fontello" alt="Cart" ><span class="avia_hidden_link_text avia-menu-text">Cart</span></a></li>';
    $items =  $items . $cartLink;
  }
  return $items;
}
add_filter( 'wp_nav_menu_items', 'add_cart_icon_to_main_menu', 9999, 2 );

replace that “#” in the snippet with your prefered link

this will insert a new menu-item to the main nav. But: it will be the very last menu-item even behind the search icon and even behind the hamburger icon itself.
Same here moving it to the right position is easy with that extra class from snippet ( menu-item-cart)

function move_cart_icon_before_burger() { 
?>
<script>
(function($){
  $('li.menu-item-cart').insertBefore($('li.av-burger-menu-main'));
})(jQuery);
</script>
<?php
}
add_action('wp_footer', 'move_cart_icon_before_burger');

to see that solution used : https://webers-testseite.de/

yes – and please – the update on 5.6.8. does not have that fixed.

test if the other selectors had to be set too!

.avia-image-container.av-hover-grow.av-hide-overflow, 
.avia-image-container.av-hover-grow.av-hide-overflow .avia-image-container-inner, 
.avia-image-container.av-hover-grow.av-hide-overflow .avia-image-overlay-wrap a.avia_image {
  overflow: hidden;
}

Did you try to embed the layerslider with its shortcode (on Project List hover the preview – click on the 3 dots on the top right – embed) ?

But you use justification there, don’t you?
With justified text, that’s exactly what often happens, that there are unsightly word spacing. You will have the same problem in Word. In Word, a more or less intelligent word separation is set.

so you have to decide now what to do if you set a text-block to justify.
By the way – how did you set this? because Tiny Editor does not offer – justified test.

you can use hyphens or word-spacing f.e.:

p {
    text-align: justify;
    -webkit-hyphens: auto;
    hyphens: auto;
}

some css properties ( text-justify; word-spacing ) are not well supported by all browsers. see: https://css-tricks.com/almanac/properties/t/text-justify/

f.e.:

p {
  text-align: justify !important;
  -webkit-hyphens: auto;
  hyphens: auto !important;
  text-justify: distribute;
  word-spacing: -0.05em !important;
  text-align-last: left;
}

but i would not use everywhere a justification. So it is much better if you set a custom class to those texts that should be justified.
and use the custom class to specified text.

btw – with the extra long words, which are separated unsightly, also a manually set “should break points” could be useful.
You can use for that the html entity: ­
this is short for softhyphenation – in Word this is called conditional line break
and there is a nonbreakinghyphen entity too Link. for words like “on-page”, “off-page”

as far as I understood it, only the one link should open in a new tab. The others should open on the same page.

so maybe use instead:

function open_custodiapestcontrol_links(){
?>
<script type="text/javascript">
window.addEventListener("DOMContentLoaded", function () { 
    (function($) {     
        $('.av-masonry-entry[href*="custodiapestcontrol"]').attr('target', '_blank');
    })(jQuery);
});
</script>
<?php
}
add_action('wp_footer', 'open_custodiapestcontrol_links');

or – if you like to open all external links ( links that have a different domain ) in a new tab ( with some exceptions like mailto etc. )
use:

function open_external_links_in_newtab(){
?>
<script type="text/javascript">
window.addEventListener("DOMContentLoaded", function () { 
    (function($) {
      var url = window.location.origin;
      $('a').not('a[href*="'+url+'"], a[href*="mailto:"], a[href^="#"], a[href*="tel:"], a[href*="javascript:;"] ').attr({
        'target':'_blank',
        'rel': 'noopener',
      })
    })(jQuery);
});
</script>
<?php
}
add_action('wp_footer', 'open_external_links_in_newtab');

(remove rel attribute if you do not like to set)

Das sollte man noch ein wenig verfeinern, und auch browser übergreifend – zumindest mit -webkit prefix machen.
Das animation timing – eventuell mit bezier Kurve animieren.

to this topic possibly one more. I have made the experience that plugins like : Post Types Order could interfere here.

it would be nice to participate as a participant ;)

i think ismaels code should work.
on looking for this from docu:

click on your CPT on dashboard and look to the url window on top – what post-type you see there

f.e. on portfolio ( which is a CPT too ). you see: edit.php?post_type=portfolio

try a shortform – then with the info you get from that url window

add_filter("avia_post_slide_query", function($query) {
    unset($query["post_type"]["vacature"]);
    return $query;
}, 10, 1);

i’m so sorry – i tested it on my own toggles – and there it worked like a charm –

try this instead ( or in addition)

#top .single_toggle {
    clear:both; 
}

but loosing the focus away to top is still on your page a problem – because if you open a toggle – you like to read it – and not to move to the top!

Well with your Alias name and a little search i found your page ;)
and on FAQ everything works fine here in OSX Chrome

Edit : . You are right. I see – if you open the 5th or 6th toggle there are again this behavior.
Can you please remove the interims solution with toggle_wrap set to display: none
and refresh all cachings and merging please after that.

I had to inspect where we can correct this. – on the enfold page https://kriesi.at/themes/enfold-2017/elements/accordion/ it works as i said as expected.

i think – yes you can shorten it – and maybe you use the css rule google offers – for those wanted font styles:

function avia_add_content_font($fonts){
    $fonts['Assistant'] = 'Assistant:wght@300;400;700&display=swap';
    return $fonts;
}
add_filter( 'avf_google_heading_font',  'avia_add_content_font');
add_filter( 'avf_available_google_fonts',  'avia_add_content_font');

the css definition will be :

font-family: 'Assistant', sans-serif;

nicht dafür ;)

Thanks for info.
It sometimes happens that errors creep in when saving to the database. These can be very persistent. Therefore, it often helps to simply create a new page with the same content. For the home page, it doesn’t matter what the original page is called – the addendum will be removed from the permalink anyway. For other pages, you will need to delete the broken page completely in order to give the new page the same permalink.