4 ms·
Not directly related to the content, but as a frontend engineer, I'm always curious about the decisions that go into making a complicated web page. In this cas
by otras 8y ago
Not directly related to the content, but as a frontend engineer, I'm always curious about the decisions that go into making a complicated web page.
In this case, my devtools reports the following as I load the page with uBlock on with good internet:
> 60 requests | 71.3 MB transferred | Finish: 13.63s | DOMContentLoaded: 1.33 s
Sorting by size shows that it's largely the background images taking up most of the load, with the background header/mountain picture [0] making up 11.8MB of the load. On a similar note, clicking into the tab from a different tab makes Chrome freeze for ~1s on my 2017 MacbookPro. Not quite the most user-friendly experience!
[0] https://www.subtchallenge.com/img/header/SubT_Header_Mountain2.png https://www.subtchallenge.com/img/header/SubT_Header_Mountai...
- microcolonel 8y agoYeah, nearly 12MB for a single hero image is kinda silly. Added: One trick I have used for large photographic cutouts is to use svg for the mask, and either embed or reference the lossy image (jpg) from there (gzip settings to undo the expansion factor of base64 are not too slow, so sometimes embedding is okay).