> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/faq/survey-performance-and-loading-speed.md).

# Survey Performance and Loading Speed

Troubleshoot slow survey loading and optimize survey performance

A fast-loading survey gets more responses. If your survey is slow to appear, here's what to check.

### My survey takes a long time to appear on the page

Survey loading speed can be affected by several factors:

* **Page load time.** Zigpoll loads after your page content, so if your page itself is slow, the survey will be delayed. Optimize your site's overall performance for the best results.
* **Delivery trigger.** If your survey is set to appear after a time delay or a number of page views, it waits on purpose. Check the timing on **Settings → Delivery → Trigger**.
* **Network conditions.** On slower connections, the survey widget may take a moment to load. This is typically only noticeable on very slow mobile connections.

{% content-ref url="/pages/-LrVM-QyPUockueYu4xQ" %}
[Delivery Settings](/polls/visibility-settings.md)
{% endcontent-ref %}

### Does Zigpoll slow down my website?

Not noticeably. The survey script is lightweight, loads in the background, and doesn't block your page from rendering. It loads after your main content, so it shouldn't noticeably affect your page speed or Core Web Vitals.

### My exit-intent survey isn't triggering on mobile

Phones have no cursor, so on mobile Zigpoll opens an exit intent survey when the visitor:

* scrolls up quickly toward the address bar,
* switches to another tab or app, or
* stops scrolling and touching the page for a while (45 seconds by default).

If it still doesn't open, check that:

* **The Exit Intent Timer has passed.** Nothing fires until the visitor has spent that long on your site (10 seconds by default).
* **Device** isn't set to **Desktop Only**, and the page matches the survey's rules on **Settings → Delivery → Locations**.
* **You haven't already completed or closed it** in this browser. Test in a private window.

To make it fire more readily, raise **Sensitivity** on **Settings → Delivery → Trigger**. See [Exit Intent on Mobile](/tutorials/exit-intent-mobile.md).

### My exit-intent survey opens too early

Exit intent can open before someone actually leaves:

* **On mobile, idle time and switching apps count.** A visitor reading a long page without scrolling, or glancing at another app, can trigger it. Lower **Sensitivity** to lengthen the idle time and require a faster upward scroll.
* **The timer is site-wide.** The **Exit Intent Timer** counts from the visitor's first page in this browser session, not from each page load. Someone who has browsed for a minute can trigger it the moment they land on the next page. There's no per-page timer; raise the timer instead.
* **Sensitivity is high.** On desktop, higher sensitivity opens the survey sooner after the cursor leaves the top of the window.

To show a survey after a set time instead of on exit, use an on-site survey with a time-based pattern on **Settings → Delivery → Trigger**.

Exit intent can't run inside Shopify checkout. See [Shopify checkout limits](/installation/shopify-checkout-limits.md).

### My survey shows up but looks broken or incomplete

This can happen if another script on your page is interfering with Zigpoll. Try the following:

* **Check for JavaScript errors** in your browser's developer console.
* **Disable other apps or scripts** temporarily to see if there's a conflict.
* **Clear your browser cache** and reload the page.

### How do I make my survey appear faster?

Zigpoll already caches its assets to load faster. If speed is critical, avoid large images or files in your survey and keep the number of questions short.

{% hint style="info" %}
Experiencing persistent performance issues? Contact us at <support@zigpoll.com> with your site URL and we'll investigate.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zigpoll.com/faq/survey-performance-and-loading-speed.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.