Excellent plugin, but has consequences

@leninkster – Appreciate the feedback and you are correct partially. I’m not sure what you mean by “forces a change to the initial render of the site when popup is triggered”. That isn’t actually true in a technical context.

What is actually happening is the scanner is not differentiating normal sites from PWA (progressive web apps) like Facebook or Twitter where content is not loaded initially but only after the page loads. So the scanner continues listening to browser requests for ~30 seconds after the last detected request.

So what that means is even though Popup Maker popups do not actually do anything at all until the page has already loaded completely, once the popup opens and the analytics event is fired they track that as some new content being loaded, when it isn’t that at all.

This isn’t an uncommon issue, anything that makes a request after page load would be susceptible:

– Sliders or image carousels
– Cart widgets that ajax in after page load.
– Google Analytics hits
– Social widgets (like buttons, tweet counts).
– SaaS based forms like Jotform that load after the page finishes.

Really the page scanners should have an option to determine if you your site is a PWA (progressive web app) or not. Most sites are not, yet they scan them all like they are resulting in misleading results and confusion like you dealt with.

That said I’d love to know if you think the flaws in the page scanners results is still worth a deduction in stars for our plugin? Is there something you think we can do better on our end?

• This reply was modified 5 years, 5 months ago by Daniel Iser.