BRands

Hello, after editing a markdown the bold function doesn't seem to work anymore. The page now shows double asterisks before and after **text-here**. The website uses 7.0 markdown blocks. Older markdowns with bold still works fine. But if we edit this markdown we also lose the bold function. Does anyone know how to fix this? Thanks

Same problem with our website https://happydrops.nl/. Cookie banner is not showing up. The settings are in place as you can see below. Any thoughts?

You're a genius!! Thanks a lot for sharing your knowledge!

Hi @paul2009, your CSS solution to restore the asterisk didn't work on our website. Have you got an alternative solution to change (required) on our form? https://happydrops.nl/offerte Thx in advance.

Hi, Is there someone who could help me figure out how to rename the word "Back" to "Terug" in the mobile navigation menu of the Brine template? https://happydrops.nl/systeem

Thanks Paul. Seems to be working as you told. Great! Leaves us with with loading performance (LCP) and visual stability (CLS). Are these problems beyond our control? Looks like it if we look at the 2 top issues GT metrix shows. Is it up to the SS developers team to finds solutions to save time with the eliminate render blocking resources and improves the efficient cache policy? Or can we optimise this ourselves?

LCP and CLS issues are the reason why Google shows a lightning bolt icon (first screenshot) behind our page results. And by clicking the pagelink Google shows the Google AMP-viewer (second screenshot) instead of our Squarespace site. This is killing for the lead experience. And leads even have to click ones more on the Google AMP-viewer before entering our Squarespace site. Bad Web Vitals are not only negatively influencing our organic search results (-30% m/m) but also killing the experience. We have followed all the guidelines for fast loading of content. GT metrix show the following 2 top issues in all off their reports (third screenshot): • Eliminate render-blocking resources • Serve static assets with an efficient cache policy There is nothing we can do about these issues. How can we move SS team to optimise the Web Vitals?