Took a look at the page. My first inkling is that we have probably exceeded the max payload size limit for a single message on the engine, given that the page has a lot of images.
I'll confirm if that is the case tomorrow.

I will file a separate bug to track the empty page issue. This one is requesting more logs so that we can understand what happened in the future. Logs can include success and failure case. More for debugging purpose.

Filed crbug/597009 to track empty cnn.com case.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7d0ee4cc3bd5d7ab207467fa17e82fa3bb05126e

commit 7d0ee4cc3bd5d7ab207467fa17e82fa3bb05126e
Author: khushalsagar <khushalsagar@chromium.org>
Date: Fri Apr 01 03:39:23 2016

blimp: Add logging for compositor and render widget feature.

Add some logging for debugging to the compositor and render widget
features.
BUG= 596797 
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Review URL: https://codereview.chromium.org/1840843005

Cr-Commit-Position: refs/heads/master@{#384477}

[modify] https://crrev.com/7d0ee4cc3bd5d7ab207467fa17e82fa3bb05126e/blimp/client/app/blimp_startup.cc
[modify] https://crrev.com/7d0ee4cc3bd5d7ab207467fa17e82fa3bb05126e/blimp/client/feature/compositor/blimp_compositor.cc
[modify] https://crrev.com/7d0ee4cc3bd5d7ab207467fa17e82fa3bb05126e/blimp/client/feature/compositor/blimp_compositor_manager.cc
[modify] https://crrev.com/7d0ee4cc3bd5d7ab207467fa17e82fa3bb05126e/blimp/common/logging.cc
[modify] https://crrev.com/7d0ee4cc3bd5d7ab207467fa17e82fa3bb05126e/blimp/common/logging_unittest.cc
[modify] https://crrev.com/7d0ee4cc3bd5d7ab207467fa17e82fa3bb05126e/blimp/engine/app/blimp_content_main_delegate.cc
[modify] https://crrev.com/7d0ee4cc3bd5d7ab207467fa17e82fa3bb05126e/cc/trees/remote_channel_impl.cc
[modify] https://crrev.com/7d0ee4cc3bd5d7ab207467fa17e82fa3bb05126e/cc/trees/remote_channel_main.cc