When can a website be over 1mb?
When a new website is released for a popular or high profile brand there are two stages of reaction. The first is praise: “it’s responsive!”, “it’s gorgeous!”. The second is criticism: “don’t work in IE9!”, “it’s over 1MB!”. As is internet traditional, opinion must be bipolar and unconditional.
Initial reaction to the new Majora’s Mask 3DS website has been no different.
Granted, it’s rather chunky. Fullscreen on my 1920 × 1080 monitor I downloaded 2.5MB of images alone. The whole thing is over 3MB, not counting the video content that starts to preload (60+ MB before I stopped it).
I’m not trying to argue that the Majora’s Mask website is well developed. I haven’t looked under the hood. The point I want to make is that it might, just might, be acceptable to build a website over 1MB. There seems to be a prevailing rhetoric within our industry that if a website exceeds this magic number, it’s a failure.
There’s plenty of research data to show how deadly slow loading can be. To no one’s surprise, users don’t like to wait.
The thing is, generalising data can be misleading. Not all websites are created on equal footing. In this particular case, users will not “go elsewhere”. For new and old customers interested in a new (re)release in the Nintendo / Zelda universe, there’s no alternative and they don’t come often.
Is that an excuse? I realise I’m often forced to endure poorly developed websites because there’s no alternative (public sector services come to mind)…
However, I do not agree that size is inherently bad.
It’s impossible to deliver the kind of visual fidelity Majora’s Mask offers without fat content. How do you spark the imagination — rekindle childhood memories — with some boring “flat design” bollocks?
The load is worth it.
It’s the same reason Apple.com gets away with pages in the several megabyte territory. Customers wait in lines for hours when they have the option to walk next door and buy a Windows phone.
Websites with this privilege are few and far between. Regardless, they would always benefit from detecting slow connections and delivering a lightweight experience to make info accessible. But when the bandwidth is there, it’s not wrong to use it.
Anyway, if you load critical content and style first, late-load the rich stuff once the user can access the basics, the final megabyte count is a poor indicator. Stop using it to blindly judge the quality of development!
I want to restate: statistics can be misleading and wrongly applied. Browser usage is a common one; the global average means nothing to an individual website, yet I see the numbers quoted often.
I may regret writing this article when I have to tell a future client they’re nothing special and a fullscreen carousel won’t increase the bottom line.
I failed to complete Majora’s Mask on the 64. Anyone who says they enjoyed it is lying!