A lot of times when I'm browsing on a mobile device in an area with low reception, pages will seemingly load forever and then appear all at once. I've since learned to tell my mobile browser to stop loading the page, because often what I need (page content) has been fetched but is not being rendered. The reason it's not being rendered is because an ad on the site haa not finished loading.
I understand that you would want to show the ad to generate ad views+revenue but why should an ad be allowed to delay the user's access?
Answer
This is more than likely due to the fact that ads are served by third party services, which require additional network requests. These additional requests introduce latency which delays the page load. Because a web page is more or less a single thread, any delay by any portion of the page rendering causes the whole process to pause until that request is done.
The experience you are describing is an artifact of the technology behind it, rather than an intentional effort on the part of the site owners. Despite CDNs and whatnot for serving third party ads, latency is part of the equation (especially on mobile).
Some things could be done to load ads after the page has been rendered using Javascript, perhaps, but all of this really is implementation details that aren't really on topic for this SE.
No comments:
Post a Comment