goosbumps

thanks very much for your time... the fix involved removing the overlay effects, noise for the big go button & the liquid effect for the large black virus image

thanks for your time..... the fix involved removing the overlay effects, noise for the big go button & the liquid effect for the large black virus image 

There is script in there. That's not CSS. Move that to Code Injection before you try to evaluate any CSS issues.

What are you trying to achieve with the custom css? It looks there are rules in there to hide the social icon svgs and you're trying to replace them with background image pngs?

Hi @goosbumps,
I've got your DM asking for some help.  I've had a look at your site and it just looks like you are missing a closing </style> tag at the end of your CSS in your Footer.  Without this, your SQSP code is breaking the SVG's on your site. You could move your CSS to your Custom CSS area so you don't need opening and closing style tags and just leave your Scripts in your Footer.
FYI - To reduce your code, you could do most of what your custom code is doing with SquareKicker then you won't have to worry about broken code messing up your site:  ie SquareKicker can hide your Social Icons in you overlay menu per screen size, has a built in Back to Top Button, hover animations, etc.
 

thanks very much for your time... the fix involved removing the overlay effects, noise for the big go button & the liquid effect for the large black virus image

I'm not sure about this as a solution, you would need to swap out your section ID to this:
[data-section-id="65bafafd6a3a794ff88a3b38"]
But the padding top won't be correct for your website, and I'm not convinced that this would solve it either way.

This can happen with images set to 'Fill,' since they grow to fit the space available. However, many mobile devices browsers change the available space due to the address bar being shown or not while you scroll. Try switching from 'Fill' to 'Fit' for the affected images. 

I'm not sure what would be causing that, custom code (from the other thread you have lots!) could be the problem, but also setup might be an issue. REally hard to say as I can't replicate it.