New Toledo Blade Website - May 2016

Still testing as of May 25, 2016 at:

http://beta.toledoblade.com

I assume that responsively-designed website will replace the current http://toledoblade.com and the mobile site at http://m.toledoblade.com .

The beta sight is heavy with images in a tile format on the homepage. 

On the article page, the site uses an infinite scroll. Once at the bottom of an article, the site loads another article. I have never liked this clunky user experience that I have experienced on other sites.



h3. Speed Testing

http://beta.toledoblade.com/Featured-Editorial-Home/2016/05/25/An-old-fashioned-word.html

http://www.webpagetest.org/result/160525_S5_252G/

Web Page Performance Test for
beta.toledoblade.com/Featured-Editorial-Home/2016/05/25/An-old-fashioned-word.html
From: Dulles, VA - Chrome - Cable
5/25/2016, 12:39:52 PM

First View - Fully Loaded:

* Time: 60.379 seconds
* Requests: 1,317
* Bytes In: 6,225 KB


hr.

http://www.toledoblade.com/Featured-Editorial-Home/2016/05/25/An-old-fashioned-word.html

Not much difference between the two.

The new version of the site is slow and bloated like the old one.


hr.


Stats for the body part of that editorial (excluding title, byline, date, etc.)

* Word count: 435
* Bytes: 2538

The editorial contains no images. 

I used my simple, static blog app, Wren, to create an HTML page that used the body text from that editorial. The byte size of the minimal HTML page wound up being 6,152 bytes. Wren uses a small chunk of CSS. The HTML tags would contribute to the byte size increase. The editorial contains a lot of short sentences that are paragraphs, requiring para tags.

Still, it's only 6K. But the Blade forces a user to download 4 to 6 megabytes of info.

 #toledo #design #media