Help centre › Website widget › Adding the widget on popular platforms

Troubleshooting an embedded widget

If the widget will not show on your site, looks wrong once it is there, or loads slowly, the cause is almost always something on your own site rather than something in Make a Rezzy. This article runs through the common causes in roughly the order to check them.

The widget does not appear at all

Pasted into a rich-text block instead of an HTML block

If the snippet shows up as visible text starting with <div, it has been pasted into a rich-text editor that escaped the angle brackets. Find the right kind of block on your platform — Custom HTML, Embed Code, Code, or Custom Liquid — and paste the snippet again. The platform-specific articles cover the exact name for each builder:

Page caching is serving the old version

Caching plug-ins (WP Rocket, W3 Total Cache), CDNs (Cloudflare, Fastly), and the built-in caches on Squarespace, Wix, and Shopify can hold an older version of the page that does not yet contain the snippet. After pasting:

  • Purge the cache for the page in your caching plug-in or CDN.
  • Open the live URL in a private browser tab so your own browser cache does not get in the way.
  • If you have just published, give the platform a minute. Some builders take a short while to push the change to their CDN edges.

A Content Security Policy is blocking the script

If your site sets a strict Content Security Policy (CSP) — common on sites behind Cloudflare with custom rules, or on agency-built sites that hardened CSP for security — the browser will refuse to load the widget's loader script. Open the browser console (F12, then the Console tab) and look for messages mentioning "Content Security Policy" or "Refused to load script". You will need to allow makearezzy.com as a script source in your CSP rules.

A security plug-in is blocking third-party scripts

On WordPress, plug-ins like Wordfence and iThemes Security can block third-party scripts by default. Check the plug-in's logs for blocked scripts and allow makearezzy.com.

The widget shows in the editor preview but not on the live page (or vice versa)

Most site builders do not run third-party scripts inside their editor preview — so the widget often only appears once you publish and visit the live URL. The opposite (live works, editor does not) is normal and not a bug. Always test in a fresh private browser tab on the live URL.

The widget shows but looks wrong

Fonts look off (especially on Wix)

Wix wraps embeds in an iframe, which isolates them from the surrounding page's CSS — so the widget does not inherit your site's fonts. Pick a specific font family in the widget configurator's Brand section instead of relying on System. See Customising the widget.

Inputs are squashed together on mobile

For the inline widget variant, tick Stack on mobile in the configurator so the date, guests, and time inputs stack vertically on narrow screens. Always check the live page on a phone or in a narrow browser window after pasting.

The widget is sized too small

On platforms that put the embed inside a fixed-size container (Wix is the main culprit), drag the container to give the widget enough room. The button variant needs about 240×64 pixels; the inline variant needs the full page width and 360 pixels of height minimum. See Adding the widget on Wix for sizing rules of thumb.

The widget loads slowly

The loader is a tiny script that fetches the latest widget code on demand — under a hundred kilobytes in total — and should not add noticeable load time. If a page that used to be fast feels slow after pasting, look for:

  • An aggressive ad-blocker or privacy extension on the visiting browser. These can stall third-party requests for several seconds before letting them through. Try a clean browser profile to confirm.
  • Multiple loader scripts on the same page. If you pasted the whole snippet several times, you have several loader scripts. Keep one loader, but as many <div data-makearezzy-widget="…"> placeholders as you need.
  • A misconfigured CSP that delays the loader until the rest of the page has rendered. The widget defers gracefully — this is rarely the actual problem, but worth a glance if nothing else fits.

When to ask for help

If you have worked through the checks above and the widget still will not behave, email support@makearezzy.com with:

  • A link to the page where the widget should appear.
  • A screenshot of any messages in the browser console (F12 → Console).
  • The name of the platform your site is built on (WordPress, Squarespace, etc.).

We usually reply within 5 working days. Most embed problems turn out to be a setting on the host platform rather than something in Make a Rezzy — and we can usually point you at the right setting once we have seen the page.

Where to go next