4 ms·
I'm not a React dev, so I can't comment on the project itself. Something I noticed on the blog post, though: The image at the top of the page is served uncompre
by gothink 3y ago
I'm not a React dev, so I can't comment on the project itself. Something I noticed on the blog post, though:
The image at the top of the page is served uncompressed at a whopping 18.5MB (9751px * 6132px)! Seems a bit extreme for what amounts to a simple logo and some text.
- quickthrower2 3y agoLooks like a job for pure css, or if you are feeling brave, svg!
- aidenyb 3y agoHoly crap you're right, that was a VERY large image, fixed: 18.5MB -> 21KB
- Hrun0 3y agoNothing a couple of rocket emojis won't fix :D
- ricardobeat 3y agoOuch. It’s also downloaded twice (in Safari at least), putting the total page weight at almost 40MB.
- cnasc 3y agohttps://idlewords.com/talks/website_obesity.htm https://idlewords.com/talks/website_obesity.htm
- lifthrasiir 3y agoAnd the file has a very, very faint gradient background with heavy dithering, so lossless compression won't actually help that much (ECT was only able to shave 13% of the file after minutes). In fact it is one of the worst imaginable cases for raster image formats.
- blackoil 3y ago18 MB may be odd, but most pages now have multiple images making each page 10s of MB. That makes all discussions about some framework few hundred kb smaller funny.
- paulddraper 3y agoYeah for all the complaints about an extra 500Kb of JS, the real offenders are often images.
- quickthrower2 3y agoBut don’t forget you need to download and parse the JS and load that into memory. Plus depending on what it does it may be battery intensive.