3 ms·

Wow, this is due to them including more than 50 or so base64 encoded inline images. They should really change this. The page took more than 8s to load (with ca

by aselzer 12y ago

Wow, this is due to them including more than 50 or so base64 encoded inline images. They should really change this. The page took more than 8s to load (with cached images).

Mahn 12y ago
Huh. Why would anyone think that was a good idea.
- snsr 12y ago
  It results in fewer HTTP requests.
  - nknighthb 12y ago
    It also results in a 33% byte overhead on top of the additional CPU and memory usage involved in actually pulling out and decoding base64 on the client side, and it screws up caching. What should be a quick reload of this page results in the transfer of that 8MB all over again, and takes very nearly as long as the original load. There is no universe in which this was wise.
    - snsr 12y ago
      All good points; I wasn't advocating, just observing :)