On phones, OptiMonk loads only what the visitor's device needs, and never holds up your page.
What it is
Most shoppers browse on their phones, often on a slow connection. Every script a store loads competes with your products for that connection. A popup tool that slows the page down can cost you more than the popup earns.
OptiMonk starts with a small loader script, about 5 KB, or under 2 KB compressed. The loader starts the main script as a JavaScript module, so the browser doesn't stop drawing your page to wait for it.
The main script is split into parts that download only when they're needed. On a phone, the code for mobile exit intent loads only if one of your campaigns actually uses it. Code for features a page doesn't use is never fetched.
OptiMonk also recognizes the device. On a phone, it only watches the triggers you've set for Mobile, and every popup has its own mobile version, laid out for a small screen. There's nothing to switch on: this is how OptiMonk loads on every store.
When to use it
When most visits come from phones, a light script is what keeps a popup from slowing down every page.
Set a campaign's triggers to Desktop only, and phones skip it: OptiMonk doesn't watch those triggers on mobile at all.
A phone has no mouse to leave the page with. OptiMonk reads other signals, like switching tabs, scrolling fast to the top or tapping Back, and loads that code only when a mobile exit-intent campaign needs it.
Each popup has a separate mobile version. Check and adjust it in the editor's mobile view without touching the desktop one.
Key benefits
The loader is small and starts the main script as a module, so your store keeps loading while OptiMonk gets ready.
Code for features a page doesn't use, like mobile exit intent on a store that has no such campaign, is never fetched.
Every popup has its own mobile layout, and only the triggers you set for Mobile run on phones.
How it works
Your store loads OptiMonk's small loader, which starts the main script without blocking the page.
OptiMonk checks whether the visitor is on a phone and keeps only the triggers set for that device.
When a trigger fires, the visitor sees the popup's mobile version. Extra code, like mobile exit intent, loads only if the campaign needs it.
Settings & limits
This is how OptiMonk always loads. There are no speed settings to configure.
Under On devices, each trigger can run on Desktop, Mobile or both.
It relies on signals like switching tabs, scrolling fast to the top or tapping Back. Some browsers don't support every signal.
On phones too, a time delay starts once the page has fully loaded.
Step-by-step setup lives in the Help Center guide.
It's built not to. The loader is small, it doesn't block your page from rendering, and extra code loads only when a campaign needs it.
The loader is about 5 KB, under 2 KB compressed. The main script follows it, in parts, as they're needed.
Yes. Every popup has a desktop and a mobile version.
Under On devices in the trigger, turn Desktop off and leave Mobile on.
Yes. It uses signals like switching tabs, scrolling fast to the top or tapping Back. Some browsers don't support every signal.
From the browser's user agent and the screen width.
No. This is how OptiMonk loads on every store.