WPO
-
In my case I have deactivated the bell, but in each request that external resource is requested
https://bot.webpushr.com/prompt/bellAnd if I have already accepted the notification I do not understand why it continues loading https://cdn.webpushr.com/app.min.js
Thanks
-
The bell request (simple request, think of it as a ping) is run to check if the bell is active or not. Example: if you activate the subscription bell from our web console, the ping will tell your browser that the bell has been activated and it will show it.
The JS (just 4.5KB in size – the smallest size amongst all push vendors) is loaded because it performs multiple background tasks. For example: when the old subscription endpoint expires and a new one is issued, the JS sends the updated endpoint to our server.
Related additional info: The browser stores the JS file in local cache and does not make new requests to fetch on every page load. So technically, it is only fetched once from our CDN.
We apologize if we were not clear in our previous response. The subscription bell request is not cached/stored in the browser because: “The bell request (simple request, think of it as a ping) is run to check if the bell is active or not. Example: if you activate the subscription bell from our web console, the ping will tell your browser that the bell has been activated and it will show it.” Caching/storing it in the browser will 1- add more cookies (browser cookies, browser internal storage), 2- bloat our JS file, and 3- can create disconnect between your subscription bell settings and actual behavior on your site. We are open to suggestions/better-ideas here. Let us know if you have a more elegant solution in mind.
Related info: Subscription bell request is only run for users who have either accepted or denied push notifications through the native browser prompt. It does not run for users who merely dismiss the custom lightbox prompt.
The screenshot you sent shows a similar sized request (<1KB) being made by CloudFlare (one of the best CDNs out there) with similar latency. 100-200ms is within our design parameters. the occasional spike could be caused by a variety of reasons such as your internet connection speed that are out of our control.
- The topic ‘WPO’ is closed to new replies.
