Video Ad Units on a Text-Heavy Blog

I write long posts that people read on phones and older laptops. My pages are mostly text, a few images, and a plain layout. When I tested video ad units, the first thing I noticed was not revenue. It was the way the page felt slower and noisier.

Autoplay was the main friction. A muted clip that starts by itself can be fine on a video site, but on an article it competes with reading. Readers scroll to a paragraph, hear motion at the edge of the screen, and stop. Some hunt for the pause button. Others leave. I turned autoplay off for most placements and kept only click-to-play options. That reduced the annoyance, though fill and rates changed too.

Page weight mattered just as much. Video players pull scripts, styles, and media files. On a good connection it is easy to miss. On a weak mobile signal it shows up as a longer wait before the text settles. I started checking page speed with and without the unit on the same post. A small difference is tolerable; a large one is not worth it for me.

I did not launch the format sitewide. I picked a subset of posts: a few older tutorials with steady traffic and a few new essays with lower traffic. Say a post gets 4,000 views a month. I compared bounce rate, time on page, and comments against similar posts without video. I ran it for two weeks, then paused it for two weeks. I noted the dates and kept the layout unchanged otherwise.

My checklist before adding any unit:

• Test one placement at a time.
• Turn autoplay off unless the page is built for video.
• Measure load time on a throttled connection.
• Compare bounce against matched posts, not the whole site.

The link below is a reference I used when reading about publisher ad options: best ad networks for publishers. I still check each provider’s current terms myself.

So far, video works best for me as a small, click-to-play unit on posts where readers already expect media. On pure text pages, I watch bounce first and revenue second.

— Daniel Hayes