Lazy loading delays a resource until a visitor scrolls to it or clicks it, instead of loading everything upfront. It's a useful trick for speeding up a page, but it's the wrong behavior for a tracking pixel, which needs to run on every page and fire in the background right away.

🔧 Why this matters

If lazy loading applies to the Pearl Diver pixel, it can delay or block the pixel from firing, and that data never reaches your Pearl Diver account. Excluding the pixel from lazy loading has no effect on your page speed. It's a background process, not a visible element.

Check for lazy loading

1. Go to the website URL where you loaded the tracking pixel.
2. Right-click and select Inspect, or press F12.
3. In the Elements panel, press Ctrl+F and search for "tag.pearldiver". If it appears, the pixel is likely firing correctly. If you installed the code correctly but can't find it, lazy loading is the likely cause.

✅ Exclude the pixel from lazy loading

These steps cover WP Rocket on WordPress, the most common cause. If your site uses a different caching plugin or a developer-managed setup, the principle is the same: add the pixel's script URL to that tool's list of excluded or deferred scripts.

1. Log in to your WordPress dashboard.
2. Go to WP Rocket → Settings.
3. Click File Optimization (Optimize CSS & JS).
4. Scroll to Excluded JavaScript Files and enter https://tag.pearldiver.io/.
5. Save your changes.

Check the website again once the change is live. If the pixel still isn't firing, book a call with support below.

Need help? Visit the Pearl Diver Help Centre or book a support session with the team.