https://medium.com/@tubikstudio/ui-animation-microinteractio...
Aside from the fact that it's impressive to make flat-styled animations that big in gif form, I think the people behind medium.com are just as much to blame for not giving feedback to the uploader about the size of the attached images, nor offering a non-destructive optimising pass or serving the gifs reencoded as .WebM for browsers that support it.
Not to mention that their sentiment is unoriginal by a factor of possibly a decade.
Yes, Adblockers to the rescue. But you know, Apple doesn't support Adblockers on an iPhone 5 for whatever stupid reason.
I think we should be complaining about developers and admins who doesn't enable gzipping, we should be angry with the fact some websites don't even bother setting headers to cache static resources. We should not be throwing out hands up in air screaming crisis because our web is becoming more useful.
You're forgetting that mobile devices quickly run out of cache memory. This includes iPads. You might visit a news site once every few days, but quite often the same resources need downloading again and again because your iPad has not kept them in cache memory because it ran out already. Desktop browsers have a lot more capacity to keep web resources cached.
Not only that, but RAM memory is also limited on mobile devices. Forget about expecting multiple websites to remain in memory across numerous tabs. My iPad3 can pretty much handle only one tab open. If I switch tabs to another website, then switch back, the whole page loads again. A less bloated web would help this issue.
And then there's accessibility for low-speed areas. Did you even read the article?
Optimizing images is a pretty huge thing, as is enabling gz compression on the streams... these two alone add up to far more saving than setting cache headers, not that they can't or shouldn't be set.
Also since when exactly did websites have a mandate to economise to the scale of mobile data? It's always been edge case unless you are specifically targeting that.
Trends towards mobile-first have been a thing for a while. Especially in developing countries where mobile users outweigh desktop users.
Targeting desktop is slowly becoming the edge case for anything targeting a mass audience. Look at a lot of the recent high-value tech companies. Do Uber/Snapchat/Whatsapp/Instagram target desktop or mobile first?
Where are users in general spending the majority of their time? On a desktop/laptop, or on a phone/tablet?
Users, regardless of device used, are primarily on wifi and that is what is designed for. In modern countries most users don't really have data restrictions low enough to come into effect through websites so going into the future this will not be a problem.
I'm in the UK and the only network offering unlimited data is so slow you'll struggle to use more than 3GB in a month.
I've since given in and just paying through the nose for 16GB/month, so that I can not have to watch my data usage. (Un?)fortunately, the network is so fast I've found my data usage is already around 9-10GB/month, so I'm going to have to start watching that again soon.
Apart from laziness there is no reason for those websites to be so large.
Sure there's always room for an amount of optimization and good practice but it's insane to rely on that instead of fixing the problem. The growth in page size has been fairly linear and predictable.
The real headline here should be "German and US carriers cannot keep up with natural growth in technology"
You make it sound as if the natural growth in technology is what makes these websites huge. I run a web app, which is uptodate technology-wise. It has a responsive design with @2x images and @3x. It uses JS in a sensible manner. It's fast and easy to use. Top notch technology. Yet, the average request sums up to 200KB. And 60KB of that is a custom font.
This is not about the natural growth in technology, it is about 50-70% of the 2MB are entirely worthless to the user, because they are usually Ads, trackers, wrongly compressed images (ImageOptim does wonders here) and using 10 JS frameworks in parallel.
It's almost as if you're saying: See, img tags now support the width attribute, so let's upload a 10MB photo and just tell the browser to resize it to 100px, because technology.
So I go with a "those in glass houses" approach:
The only reason I can't see the terrible quality of your website's photos on my phone is that all the content is so damn small and zoomed out I can barely make out the text never-mind the picture pixels. I don't really want to zoom in because the shade of lime green you've chosen is so jarring it'll likely give me a migraine if it fills the screen.
See, what this boils down to is this: People use Adblockers, because they're tired of all that shit that's consuming their bandwidth (at least on mobile). Content publishers complain about people using Adblockers. But they're not willing to get the technical side of their content consumption platform right in order to accommodate their very visitors. They cry foul but are part of the problem obviously.
Unfortunately, I don't get to see what links to avoid (size-wise) before I download all the bloat and waste my bandwidth.
The growth of website size has been fairly steady, if anything the growth has flattened over the last year or so. It is up to the infrastructure to keep up with that.
In the last year or two we've had the introduction 4G with 2-4 times the speed of 3G and you expect to have the same usage allowance?
You should expect to have to increase you dataplan every few years (because technology) whether that cost is absorbed by you or your phone company is a conversation to have with them.
Well, the article disagrees that this is always what is going on, for example:
> Here's the PayPal website as it looks today. The biggest element on the page is an icon chastising me that I haven't told PayPal what I look like. Next to that is a useless offer to 'download the app', and then an offer for a credit card. I can no longer control the sort order, there are no filter tools, and you see there are far fewer entries visible without scrolling.
and
> It's like we woke up one morning in 2008 to find that our Lego had all turned to Duplo. Sites that used to show useful data now look like cartoons. Interface elements are big and chunky. Any hint of complexity has been pushed deep into some sub-hamburger.
Of course many things improved, today you can make more with less, a lot more. But all of that can easily be undone by just piling on a bunch of hires stock photographs or even video, 20 ad networks and 5 tracking scripts. And one might also to consider the memory footprint and CPU usage of multiple open tabs, and how leet efficient pages and bloated crap alike get put into the browser cache which is of finite size and flushes out older things to make room. Then multiply that by number of visitors. Crisis or not, it's a LOT of waste if you really think it through.
What functionality do you have in mind when you're talking about the average read-only news-article type of web page?
If a web site is no longer readable because it layouts every 2 seconds to accommodate 145 ads, it does not have more functionality; it has less.
Yes I agree some websites do really need to go on a diet, loading unused css, js and multimedia has to be removed, but 1-2MB is not a reason anyone should be throwing their hands in air screaming CRISIS!! Definitely I would applaud anyone who would spend their time optimising their websites to be as small as they can be, but Jesus Christ 2BM and we have a crisis... no way!
I for one think this is a sign we are making progress a very good thing, we are improving as a community and we are getting more out of our web.