3 ms·
That doesn't change anything. Images are easy to handle while JS/CSS are usually blocking assets that require parsing. A small but complex JS file can have a b
by manigandham 11y ago
That doesn't change anything. Images are easy to handle while JS/CSS are usually blocking assets that require parsing.
A small but complex JS file can have a bigger effect on latency and page interactivity/performance than many large images.
- douche 11y agoI was thinking along the lines of slow/data-limited networks and bandwidth usage. I can download the complete works of Shakespeare from Project Gutenberg as plain-text with less bandwidth than one of the full-resolution JPEGs my digital camera takes.
- stan_rogers 11y agoAnd that image can be displayed full-screen on a 5K monitor (which is overkill) with no visible artifacts using a JPEG file smaller than 1MB if it's properly compressed and only has the copyright and contact as EXIF data. Asset preparation is part of the process, and it's not even difficult.