I really shouldn’t be shocked by this anymore, I’ve seen so many examples of how developers always manage to ignore a standard, or a common behaviour of the web resulting in a broken experience.
Today I came across three prime (and repetitive) examples of common mistsakes:
To www or not to www
I saw an ad for Lego Land at the streetcar stop this morning, so while waiting I figured I’d check it out, open my Chrome Mobile, type in legolanddiscoverycentre.ca and I get this:
Javing seen this before, (oh, so many times!) I tried www.legolanddiscoverycentre.ca and I get the correct website!
HTTP vs HTTPS
Next on this shame list, is TransUnion, I typed in “TransUnion” in Google, clicked the first result and landed on the website at http://www.transunion.ca
At first glance, everything looks normal, then I quickly realized there is nothing to click on, and it seems some images are not showing!
Again, having seen this before, I quickly try https://www.transunion.ca and I get the proper page:
Not only was the page under HTTP broken, it’s also COMPLETELY different than the HTTPS page!
Being curious, I try: https://transunion.ca and of course they screwed that up as well:
I give up!
Please stop breaking the web!