I say cruft because I'm reading on mobile. I've got a Galaxy Note 2, and I'm using Chrome. It's hardly a slouch of a machine.
First, after clicking the link, I have to watch your spinner for a ~5 seconds. I'm on 65Mbps ADSL - just how much content are you sending me?
Second, the sheer weight of the JavaScript slows everything down. My browser is perfectly capable of scrolling through a page - yet because you've overloaded that, the scrolling is slow, jumpy, and the text renders poorly.
Thirdly, the Note has a huge screen, so I don't mind your static header. If I had a small screen it would piss me off.
Finally, when I switch from Portrait to Landscape, your page jumps all over the place.
Now, compare that to the Mobile NYT page. Yours looks more beautiful, but the NYT is quicker, easier to read, and doesn't get in my way.
You have great content - and an interesting product - but it needs to go on a diet and be user tested on a wider range of devices. I dread to think how it performs on low end phones.
I say cruft because I'm reading on mobile. I've got a Galaxy Note 2, and I'm using Chrome. It's hardly a slouch of a machine.
First, after clicking the link, I have to watch your spinner for a ~5 seconds. I'm on 65Mbps ADSL - just how much content are you sending me?
Second, the sheer weight of the JavaScript slows everything down. My browser is perfectly capable of scrolling through a page - yet because you've overloaded that, the scrolling is slow, jumpy, and the text renders poorly.
Thirdly, the Note has a huge screen, so I don't mind your static header. If I had a small screen it would piss me off.
Finally, when I switch from Portrait to Landscape, your page jumps all over the place.
Now, compare that to the Mobile NYT page. Yours looks more beautiful, but the NYT is quicker, easier to read, and doesn't get in my way.
You have great content - and an interesting product - but it needs to go on a diet and be user tested on a wider range of devices. I dread to think how it performs on low end phones.
T