An upcoming Google Chrome feature might hurt ad revenue, but it might also give us a new way to fight against ad fraud.
According to a report published by the Search Engine Journal, Google Chrome’s June 9th update is packing what could be a nasty surprise for publishers: native lazy loading.
<img src="cat.jpg" loading="lazy" alt="..." /> <iframe src="video-player.html" loading="lazy"></iframe>
Lazy Loading — Why It’s Awesome…
Lazy loading is a useful feature because it addresses problems with page loading speeds. Unoptimized images are among the most common reasons for bad website performance, including slow loading pages. Users will not wait for too long before they browse away from a website that loads slowly.
There are plenty of studies and surveys that show us just how much of an issue is a slow-loading page. We know, for example, that pages that load in 2.4 seconds have a conversion rate of 1.9%, while pages that load in 5.7 seconds have a conversion rate of only 0.6%.
Similarly, pages that load slowly have significantly higher bounce rates. All of this hurts a business’ bottom line.
With lazy loading, publishers might be able to get some additional loading speed without further compromising the quality of the visuals. With lazy loading enabled, Google Chrome will load the images and iframes only when a user scrolls to them, reducing the initial loading time of the page.
Because Chrome is the number one browser on desktop and mobile, this feature will probably have a significant positive impact on publishers. It’s just too bad that it will also take as it gives.
…And Why It’s Not
There’s something else that won’t load until users scroll to it: an ad that’s below the fold. When anything that’s not on the screen isn’t loaded, all the ads that are only visible after some scrolling will not load, either. And that can hurt the publishers displaying the ads.
When an image doesn’t load, it doesn’t count as an impression. If there are no impressions or thousands of them, publishers don’t get money for displaying ads.
The real problem will happen on mobile. The SEJ report refers to documents that mention how Google might push lazy loading even on elements that don’t have the attribute when Android’s data saver feature is enabled. And it seems like the developers are aware of the potential revenue loss these changes might cause.
But if we know something about the online world in general, and people whose livelihood depends on Google one way or the other, it’s that we’re all very quick to adapt to Google’s whims. Those of us that aren’t usually can’t survive for that long.
How Will Publishers Adapt
One of the ways publishers can deal with lazy loading is by creating engaging content that will make people scroll down the page. The websites whose pages people already view from the top to the bottom will be just fine.
The publishers that can’t be bothered with that will probably revert to other tactics. One is to enforce dynamic scrolling. So instead of giving users the incentive to see what else is on the page, publishers can try to trick both them and the browsers into loading images.
The implication here is that the latter two are the tactics fraudsters are more likely to use.
Creating an honest incentive to go down the page will take some effort to produce high-quality pages. The easier solution will always be to cheat — even though it all but guarantees a lower quality of content.
The ClickGUARD Way of Dealing with Consequences of Native Lazy Loading
The one thing we expect is that ad placement will become a very relevant source criterion. If you see that you’re receiving high frequency of low-quality clicks, more invalid clicks than usual, or clicks coming from multiple above-the-fold ads on a website, you’d be right to suspect that the website in question is of low quality and will deliver low-quality traffic.
That’s why ClickGUARD, includes ad placement as one of the possible click sources. And just like our users can use IP addresses or devices as sources around which they can create specific exclusion rules, they can now do that for placement, too.
So after receiving a certain number of clicks on the same ad placement in a specific time frame, for example, you can set the rule to do a variety of things. You can set it to exclude that placement just as it would block an IP address or a device. In some severe