Well, it's kind of what I've come to expect from e-Commerce sites... unfortunately, that's not a good thing.
Painfully slow loading times (over 45 seconds here), illegible color contrasts (white on light blue, gray on dark gray), illegible fixed metric (px) fonts with fixed width design concepts -- that's the trifecta of /FAIL/ at web design right there. Handshakes ALONE on first-load is going to measure anywhere from 10 seconds to two minutes regardless of filesizes and connection speeds! More if the user is connection choked like on a shared public connection, or even at home in the age of torrents, netflix, hulu, wireless overhead...
... and given the slow loading time and broken attempt at a responsive layout, do I smell bootstrap AND jQuery before I even look at the code?
Well look at that, bootstrap and jQuery... well there's your problem.
DOZENS of separate files for nothing, endless pointless scripting not actually doing anything useful to end users... It's 102 separate files in THREE MEGABYTES -- and only a third of that is actually CONTENT IMAGES. There is no polite way to put this, that's developer ineptitude right there.
313k of CSS in 11 style sheets? FOR WHAT?!? There isn't a site out there that needs more than 48k of CSS with a limit of 2 sheets PER MEDIA TARGET, and looking at the code, the question becomes "WHAT MEDIA TARGETS?!?" Only four of the eleven stylesheets even bothers, and that's an incomplete "screen" only.
1.2 MEGABYTES of Javascript? FOR THAT? No. Even if you were knee deep in ajax for the shopping cart, there's no excuse for more than 48k of scripting, and frankly 24k would probably more like it.
... and then there's the main document itself -- 101k of CSS to deliver less than 3k of plaintext and maybe three dozen content images? No. that's anywhere from six to ten times the HTML that should have been used -- much of that can be blamed on that oh so wonderful crutch for lame developers known as bootstrap. If you don't know what's wrong with vomiting up markup like this:
<body class="fs14 page-home none active">
<div id="page-container">
<header id="header">
<div class="pav-topbar">
<div class="container">
<div class="row-fluid">
<div class="span3 rowleft">
<div id="logo" class="span4" style="top: 0px;width: 400px;">
You probably shouldn't be making websites. Why do I say this? because 99% of the time there's no reason for that on a layout as simple as that page to be more than:
<body>
<div id="top" class="widthWrapper">
<h1>
That's how bad even that simple little bit of code is... and that's some of the BETTER parts of this. Endless pointless DIV for nothing, gibberish use of numbered headings (what few of them are there), incomplete forms...
I mean look at this nonsense:
<form action="http://www.digitaltrade.eu/index.php?route=module/language" method="post" enctype="multipart/form-data">
<!-- Language<br /> -->
<img src="image/flags/gb.png" alt="English" title="English" onclick="$('input[name=\'language_code\']').attr('value', 'en'); $(this).parent().submit();" />
<img src="image/flags/ee.png" alt="Estonian" title="Estonian" onclick="$('input[name=\'language_code\']').attr('value', 'et'); $(this).parent().submit();" />
<input type="hidden" name="language_code" value="" />
<input type="hidden" name="redirect" value="http://www.digitaltrade.eu/" />
</form>
Does whoever wrote that even know what a form is? Wait, let me rephrase that, does that developer even know what HTML is, or how to 'enhance not supplant'? Let me put it this way:
<form action="index.php?route=module/language" method="post">
<fieldset>
<button type="submit" name="language_code" value="en">
<img src="image/flags/gb.png" alt="English" />
</button>
<button type="submit" name="language_code" value="et">
<img src="image/flags/ee.png" alt="Estonian" />
</button>
<input type="hidden" name="redirect" value="http://www.digitaltrade.eu/" />
</fieldset>
</form>
A bit of CSS to strip background, border and padding off BUTTON, and bang, NO JAVASCRIPT NEEDED for the same functionality.
... and if you could sneak by on "get" (don't see why not, but there is a GET parameter already in 'route') and were to extract where to redirect to using $_SERVER['HTTP_REFERER'], that could be gutted down to:
<a href="index.php?route=module/language&language_code=en">
<img src="image/flags/gb.png" alt="English" />
</a>
<a href="index.php?route=module/language&language_code=et">
<img src="image/flags/ee.png" alt="Estonian" />
</a>
That's a PERFECT example of what I mean when ranting and raving about "JavaScript for NOTHING." and people using JavaScript to replicate functionality that HTML can do WITHOUT JS! Waste of bandwidth, waste of time, and does nothing but illustrate the ignorance of the person who wrote it.
I'm sorry if this is going to upset you, but the truth hurts, and truth is that's such an ineptly developed train wreck of "how not to build a website" it's shocking it works at all; well over two thirds of the code being sent client side should be thrown away completely as pointless, redundant, and pretty much reeking of "HTML? What's that?" - and to be frank if the front end code is that bad, I don't even want to THINK about the disaster server-side...
...which is NOT a good thing when talking e-commerce.
