This article is also available in:

What you need to know about Poool script performance

Script performance and loading times are a key concern for every online publisher. They are a priority for us too: Poool is built to display your walls quickly without weighing down your readers’ experience. Here is a summary of what you need to know.

An infrastructure built for speed

Our scripts run on a fast, reliable infrastructure:

Solid hosting: the Poool script is hosted on Google’s infrastructure, and our DNS and cache are managed by Cloudflare, one of the fastest networks in the world.
Efficient caching: the first load of the script depends on the reader’s connection. After that, the script is cached by their browser, so later visits are much faster. Your wall appearances are also cached after the first visit.
Lightweight scripts: our scripts only load what they need to work. Images in your appearances are automatically converted to the lighter WebP format.
Isolated integration: the wall is displayed in an iframe, so it doesn’t interfere with your site’s code or design.
Maximum availability: our average uptime is 99.99%.

Two scripts, two roles

Poool runs on two separate scripts, each with its own purpose:

Access: displays the wall and tracks everything that happens on it.
Audit: tracks how readers interact with your site (visits, conversions), independently of the wall. It powers your reader segmentation and your statistics.

Loading Poool within a page

Once the script is available, how fast the wall appears also depends on the page it sits on. Three factors matter most:

Where the script sits in your code: for a fast wall display, we recommend calling Poool among the first scripts on the page and loading it asynchronously so it doesn’t slow down the rest of the page.
How many scripts run on the page: when a reader lands on the page, the browser has to work through a queue of scripts. The longer the queue, the later the wall may appear.
What the other scripts load: ads, videos and audience measurement tools can be heavy and slow down the whole page, wall included.

Loading Poool through Google Tag Manager? The wall then waits for GTM to load first. Make sure you give the Poool tag a high firing priority.

Want to go further? A few simple optimizations, such as preparing the connection to Poool as soon as the page starts loading, are covered in our article Web performance optimization: our recommendations.

What if the network fails?

Even in the rare cases where the connection is disrupted, your readers’ experience stays under control. If the wall gets no response from your Dashboard within 10 seconds, a default wall automatically takes over. You can choose this fallback wall (subscription, free article…) and style it to match your brand.

How to set up the behavior in case of error?

You can follow the status of our services in real time on status.poool.fr and sign up for email alerts in case of an incident.

If you have any questions, our team is here to help 🙂

Updated on: 22/10/2026

Was this article helpful?

Thank you!