This is how they tell us to build websites. technically, it’s very well put together. The front page weighs in at less than 1 megabyte and only 26 HTTP requests.
It has one problem though: In it’s eagerness to provide a nice and fast user experience for people on tablets and phones it forgot about the desktop user. You know, the guy with the 13-27″ display, sitting at work, trying to figure out when the next train leaves for Copenhagen.
An up-scaled mobile web app
On desktop, this is essentially an up-scaled mobile web app. On a 27″ cinema display you still get a lousy hamburger menu, and the UI components don’t scale well once you go beyond about 900px wide. It becomes big and clunky and you lose any sense of overview.
A quick comparison …
Here’s the trip planner on dsb.dk in a 1700×1200 browser window.
It takes up 1700x968px. Almost the entire screen. The trip planner on GoEuro, that has the exact same features, takes up 823x171px. DSB’s scaling mess takes up 11.69 times as much space … 1169% ..!
If you compare the mobile versions, it gets a little better, but DSB still has way too much scrolling going on, because everything is too big and takes up too much space.
Don’t get me wrong — I’m not bashing responsive design
Everything I build these days is responsive and, if you read my about page, you know that I prefer to go Mobile First.
I know responsive is the way to go, because when it’s done right, it’s more effective in every aspect (Performance, conversion, retention et cetera). I’m not advising against it, I’m very much advising for it. Go out and build responsive websites, the world will be a better place.
However, when it’s done wrong it can be pretty bad. Often much worse than a non-responsive website. One example I like to pull out, is that Apple, the creators of the damn iPhone, doesn’t even have a responsive website. And it’s not like they don’t have the money to get one, or the developers/designers to build it.