Hast du mal den Link zu deiner Seite ?

zunächst ist ja auch das “bring to front” im svg divider – wenn das aktiviert ist, bekommt das svg bzw. der wrapper einen z-index von 100.
mach diesen haken mal raus.

PS gut das im Screenshot dein Tel gut zu sehen war ;) die Seite zu inspizieren ist nämlich leichter als Vermutungen anzustellen.

the SVG separators are not tricky and you even have a nice preview of what the settings will do.

click to see full resolution:

Is there a page where normal users can also look at the matter?

If there is a section that is above the section where you want the divider, you can set up a bottom divider for that section.
Another option would be to give the color section a custom class, and all of these will have the top divider mirrored up.
See here – my snippet for a divider between a slider and the next color section. Since the slider doesn’t have this option, we need this trick here.
https://webers-testseite.de/divider-on-sliders/

you are concerning to the svg dividers ? or have you done it with the slant option? – i would always prefer the svg dividers.

i can not see how you have set the gradient for the first button – it is not via quick css – it shows it is an inline style – so you have to look where this rule is:

.avia-cookie-consent-button-1{
	/* Permalink - use to edit and share this gradient: https://colorzilla.com/gradient-editor/#8fc800+0,63aa00+100 */
background: #8fc800 !important; /* Old browsers */
background: -moz-linear-gradient(45deg,  #8fc800 0%, #63aa00 100%) !important; /* FF3.6-15 */
background: -webkit-linear-gradient(45deg,  #8fc800 0%,#63aa00 100%) !important; /* Chrome10-25,Safari5.1-6 */
background: linear-gradient(45deg,  #8fc800 0%,#63aa00 100%) !important; /* W3C, IE10+, FF16+, Chrome26+, Opera12+, Safari7+ */
filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#8fc800', endColorstr='#63aa00',GradientType=1 ); /* IE6-9 fallback on horizontal gradient */
border: none !important;
	color: #ffffff !important;
}

delete the rule for the button-2 and add the selectors for the other button to that rule above:

.avia-cookie-consent-button-1,
.avia-cookie-consent-button-2,
.avia-cookie-consent-button-3 {
	/* Permalink - use to edit and share this gradient: https://colorzilla.com/gradient-editor/#8fc800+0,63aa00+100 */
background: #8fc800 !important; /* Old browsers */
background: -moz-linear-gradient(45deg,  #8fc800 0%, #63aa00 100%) !important; /* FF3.6-15 */
background: -webkit-linear-gradient(45deg,  #8fc800 0%,#63aa00 100%) !important; /* Chrome10-25,Safari5.1-6 */
background: linear-gradient(45deg,  #8fc800 0%,#63aa00 100%) !important; /* W3C, IE10+, FF16+, Chrome26+, Opera12+, Safari7+ */
filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#8fc800', endColorstr='#63aa00',GradientType=1 ); /* IE6-9 fallback on horizontal gradient */
border: none !important;
	color: #ffffff !important;
}

Was ich mir vorstellen könnte, ist das du die Besucher deiner Seite bittest aktiv ihre Herkunft offen zu legen; indem du das entsprechende Bundesland abfragst.
Ich denke aber es wird wahrscheinlich leichter sein, die Telefonanlage dementsprechend zu programmieren, das eine auf deiner Seite angegebene Zentrale Nummer – je nach Vorwahl des Anrufers zu der entsprechenden Stelle weitergeleitet wird. Hier ist eine Herkunft leichte zu bestimmen.

Es über die Besucher IP ( Geolocation IP etc. pp ) zu machen ist höchst wahrscheinlich nicht DSGVO konform.

a very nice and GDPR ( DSGVO on german spoken Countries ) konform Tool / Plugin is the Shariff Wrapper
Placed links only will do the job if you click on them! – contrary to the practice that seems to be common otherwise ( facebook pixel et. al. ) to send information when page is opening.
On options dialog of the plugin you can decide if you like to show on default after/before every post/portfolio your general set social links.
But i like the shortcode solution because on the help tab of the options you can see how to influence the shortcode what and how to show – f.e.:

[shariff services=facebook|twitter theme=wcag borderradius=10 buttonsize=medium]

And btw. from GDPR ( DSGVO ) reasons it is better to remove all font loading from third party plugins.
Maybe there is an option too on the plugin to hamper this. ( as on the embedded Layerslider Plugin )

PPS : es hätte gereicht nur diese unsägliche Regel aus dieser css zu löschen !

What do you mean by: can’t find in the post slider.
the place in postslider.php is set as : __( 'Read more', 'avia_framework' )
and this indicates that the string is translatable via lang files.
All translations are in the lang files (po/mo) in enfold/lang/ folder – on German there are two versions one with formal “Sie” the other informal “Du”

I know the WPML is setting the lang attribute on html the correct way. So – if you change the language there is on html the lang mentioned:
lang=”en-US” or lang=”en-GB” – lang=”de-DE” etc.
if these are set – Enfold will use the corresponding lang file from lang folder.

Aha – the method to switch of the css one by one in developer tools. It must be the events-caledar-for-google-public.css

it is this very globaly set rule :

*, *:before, *:after {
  -webkit-box-sizing: inherit;
  -moz-box-sizing: inherit;
  box-sizing: inherit;
}

this is actually an impertinence from whoever is including this css. It has nothing at all specific for eventscalendar in this rule.
It knocks out ( even if not with !important ) for ALL elements a rule that has influence everywhere. Please write to the plugin manufacturer. And remove this rule from that css.
_________________
das ist eigentlich eine Frechheit von demjenigen der diese css mit einschleust. Es hat überhaupt nichts spezifisches für eventscalendar in dieser Regel.
Es haut ( wenn auch nicht mit !important ) für ALLE Elemente eine Regel raus, die überall Einfluss hat. Bitte mal den Pluginhersteller anschreiben. Bitte lösche also diese Regel.

ich kann es nicht finden. Eventuell solltest du mal schauen, erstmal alle plugin zu deaktivieren – in Enfold dann die Cache/Merging geschichten zu resetten.
Dann schauen ob sich das Problem zwischen 768 und 989 px löst. ( denn selbst der Hamburger ist in der Spanne nicht zu sehen)
Falls ja – dann mal ein Plugin nach dem Anderen wieder reaktivieren und schauen ob es an einem der Plugins liegt.

because you haven’t merged the files i checked it allready. There is no error on that.
Did you paste in elsewhere some css code ? Or does a plugin inject a wrong code –

the idea is good but add to your rule above:

#footer .container {
  display: flex;
  align-items: flex-end;
  flex-flow: row wrap;
  justify-content: space-between;
}

BUT you have to proove your settings – because content on the right side is cropped on smaller screens like ipad :

span will work if there is a class specified.
<span class="not-bold"> … </span>

Guess you are working on Mac Devices – and zip files with the system integrated option or a third party app.
First to mention is – compress without those little extra files OSX provides with meta data on desktop etc.
Better Zip f.e. got an option called zip for PC.

But apart from that, if you had prepared the fonts correctly, only one more glyphic font would have been included – (Enfold just tries to interpret these extra files).

Next Info: The naming in that Enfold Font Manger is the name of the folder before zip it. ( green underline )
The font-family name is independent on that – and will be generated by the font-file names ( red underline )

So my assumption is that you did something wrong when preparing the folder and zipping it.