This happens a lot when a form or booking tool loads its own CSS file from an external server.That file is blocking the browser from painting the page, which is why Lighthouse shows it as a ‘render-blocking resource’. And yes you don’t need to be a developer to fix it.
You just need to load that CSS in a smarter way.
Here how you can fix this
Add this inside your Project Settings - Custom Code - inside .
And this way
the file still loads normally so nothing breaks
but the browser doesn’t pause the page while waiting for that file
your LCP score improves without touching the CSS itself
Load it only where needed
If the CRM styles are only used on a contact page, don’t add it site wide.
Add the snippet above to that page’s head Page Settings - Custom Code so other pages don’t pay the cost.
Last resort load after first paint
If the CSS is purely decorative (not needed for initial layout), append it after load:
This removes render-blocking entirely, but there may be a brief unstyled moment for those form elements—test visually.
If you ever want someone to take an overall look and fix multiple performance blockers across your whole site, You can take a look into the Website Speedy App as well. It specializes in improving speed without changing your design.
