To help, I thought I'd share some of the tools I use for this.Īs a general rule run lossy optimizers first, then lossless.
Where possible, it's best to try automating image optimization so that it's a first-class citizen in your build chain. The solution to worrying about JS lib/framework size: include one less. As a reminder, here's a quote from Adam Sontag who suggested "One less JPG" as a solution to our bickering about framework sizes back in 2012: The page cost of using images on the web is however not a new problem but we're at least moving beyond blaming scripts as the main culprit. Thankfully Blink, WebKit and soon FF will have it. My hope is that srcset will help us improve this long-term.
Images are a non-trivial problem to solve because they occasionally need to be high-res, but at the same time small enough to not kill your users mobile data cap. LADIES AND GENTLEMEN: I present to you a website that weighs 85.9MB. Just think of this on mobile: slower data, CPU, GPU.and it's just ONE page. There have been plenty of well documented cases of page weight being heavy, with the Oakley site Brad Frost mentioned in April clocking in at ~ 25MB worth of images alone.
#Tools better than imagealpha archive#
It's a harsh reminder that many of our pages on the web are still quite fat, a big concern for slower mobile data connections.īigQuery calculated medians for a HTTP Archive run thanks to Ilya Grigorik Tools for image optimization Home GitHub Press Biography LinkedIn Twitter Subscribe Shop Blog Tools for image optimization September 26, 2013Īs we saw a few weeks ago, the weight of an average web page is now almost 1.5MB (median ~1MB), with > 50% of this being images.
0 kommentar(er)
