1. 13
  1.  

  2. 6

    Smaller, Faster Websites took Almost 3 seconds to do 74 requests and download 1.4MB of “small, fast content.” Listen folks, “Mobile Friendly” CSS does not mean 8 round trips, and 1.4MB of JS and Rubbish to give you a horrible useless version of the full site so the developer didn’t have to write a mobile version from scratch. Web developers are piling on more and more rubbish with fonts and slow fade click animations that add absolutely zero to the usability of a site, while putting an enormous burden on our computers. Last night my laptop went from a load of 0.34 to well over 7 from starting chrome… Stop lying to people about making a small fast website that is insanely large and ridiculously bloated and still doesn’t function well.

    BTW, I just put together a web stack that is 65kb for the javascript, html and css and it looks and functions reasonably well. Before I took the time to build this stack, the same application was 250 requests, 2.3MB of data and a long time to load. Ultimately, they look and behave exactly the same.

    1. 1

      Your gripe is confusing to me. What exactly is your complaint about? You start off by commenting about a site ( I’m guessing you’re referring to Bocoup’s site ) taking three seconds to load, then complain about mobile friendly sites being useless versions of a full width site and then about how developers pile on rubbish that add on cost to resource requests. While I’ll agree with you that sites tend to be bloated with libraries, frameworks, and other assets; this is part of the web development… at least in a world of client work. It’s very common for developers to fight clients and creative/UI/UX designers, to focus on performance and functionality, over aesthetics and overly complicated behavior. The fact is we’re never going to win all of those battles. In my experience, we as developers should advocate for the best solution, but ultimately we have to give the client what they want. We have to work with designers to bring their vision to life, because their work matters too. It’s a balance of many things.

      You’re leaving these comments under an article and talk by Mat Marquis, but don’t specifically comment on anything that’s being covered by him. Do you feel that anything from his talk is inaccurate or just flat-out doesn’t work? In my opinion, it’s a good talk about the state of performance and what we as developers can do to improve it. He talks about the tools that we should be using and development techniques we should be knowledgeable about, because most responsive sites are not accomplishing the goal of reduced resource cost. I’m sure you’re already familiar with Marquis' ( and Bocoup’s ) contributions to the web. Marquis has been championing new methods to handle image loading for the past couple of years. He’s help write the spec for picture element and has been a huge advocate for developing for all people, regardless of device or network connection. This is huge considering that images are the biggest culprit for slow loading time.

      I see your point and agree with some of what you said, but if you have specific complaints about what we’re doing wrong and what we should be doing, then you need to be more detailed about what you’re calling out. You should provide alternatives, as well as working examples. Otherwise, you’re just bitching to bitch.

      Do you have a link to your stack? Please share your codes.