mPulse conserves the limited parallel connections available to a mobile (or any other type of) client and has a far–future header that spreads out its necessary requests over time. Our Boomerang implementation is designed with the smallest possible footprint, whether Boomerang is loaded into a mobile browser or into some other browser type.
Your Parallel Connections Are Preserved
Through many cycles of internal testing, Boomerang loading has always completed before the other page resources have completed loaded. The mPulse Boomerang captures the amount of time it takes to load up before it is usable—and its median load time is approximately 150 milliseconds (ms)—measured across millions of requests.
Our iframe Won't Impact Your Host Page
mPulse will also never make more than 1 concurrent connection out of Boomerang (combined), and will never make more than 1 connection in total before a page completes loading (there will be at most 2 requests sent sequentially over this single TCP connection since we have our keep-alive set accordingly).