Essential Image Optimization: my new eBook on image best practices! 

Read online:https://images.guide
-
-
Replying to @addyosmani @fivetanley
It seems better to spend time reduces a few hundred bytes of JS, I've heard.
1 reply 0 retweets 7 likes -
there are lot of huge bottlenecks in javascript! And some of that is/are an image(s). So, don´t spend your time only in reducing of
#javascript !1 reply 1 retweet 1 like -
All important. Median JS p/page =240KB but can spend seconds in parse/compile/pegging main thread. Images often more network + decode heavy
1 reply 0 retweets 1 like -
So you're saying don't worry about images, JS matters way more per byte? That's what I've heard before anyway.
1 reply 0 retweets 1 like -
I'll say JS optimization is where most modern apps could see largest improvements to UX. After that, byte savings isn't a bad next focus.
1 reply 0 retweets 10 likes -
At what point do you think it makes sense to switch from trying to reduce JS to trying to reduce bytes? Is there an amount of JS? 10k? 100k?
2 replies 0 retweets 1 like -
I've seen plenty of pages where a small time investment (30m) could shave MBs off in image bloat, but JS dominates main thread usage.
1 reply 0 retweets 2 likes -
So if you're using a library that runs for more than 5s on target mobile hardware, switch to vanilla.js before worrying about images?
1 reply 0 retweets 1 like -
Everyone should identify their largest bottlenecks, stack rank based on importance to users and focus on what matters. In many cases, its JS
4 replies 1 retweet 7 likes
I'd think features might sometimes matter more than reducing JS time.
-
-
Replying to @wycats @addyosmani and
It seems like optimizing images could be treated like JS minification, since you can do it w/o changing architecture.
0 replies 0 retweets 2 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.