4 ms·

Some constructive feedback to the site owner: Instead of having the webpage spend several minutes slowly loading thousands of barely-compressed 500x500 JPG imag

Some constructive feedback to the site owner: Instead of having the webpage spend several minutes slowly loading thousands of barely-compressed 500x500 JPG images, please consider this advice: 1. Convert the images to WEBP or AVIF or at least run them through something like TinyPNG to compress them better. 2. Save two versions of each images; a 75x75 version that gets used for the 75px thumbnails shown on the page, and a 500x500 version that appears in the lightbox after a thumbnail is clicked. 3. Only load a few dozen thumbnails at first and then load more after the user scrolls down or clicks a "show more" type button.

codingdave 2y ago
I'm not sure optimization is her goal. If you just load the page and let it sit without scrolling down, it slowly counts the number of photos she has taken. That is not the design choice of someone seeking speed. So she might be deliberately allowing it to be slow. That would track with her other works, one of which specifically says she finds beauty in imperfection.
deleted 2y ago
[deleted]
firecall 2y ago
For points 1 and 2: I recommend and use Cloudinary. Cloudinary can take care of all that for you! For point 3: You can add laoding="lazy" to the image tag, and get lazy loading for free, supported by the browser: * https://developer.mozilla.org/en-US/docs/Web/Performance/Lazy_loading https://developer.mozilla.org/en-US/docs/Web/Performance/Laz...
netsharc 2y ago
I'm still dreaming of an image file format where the file begins with the, say, 75x75px image, and then continues with higher and higher resolutions, where the browser can decide when to stop downloading. Ideally they wouldn't be redundant either, e.g. the 2nd block would contain just the data to upscale the 1st block to twice the resolution.. so the "75x75" thumbnail in a hidpi display would just need blocks 1 and 2..
- BugsJustFindMe 2y ago
  Dream no longer. You just described a progressive JPEG.
  - dsego 2y ago
    The future was 30 years ago.
- jfil 2y ago
  Check out DZI (Deep Zoom Images), IIIF API and Zoomify.

codingdave 2y ago

I'm not sure optimization is her goal. If you just load the page and let it sit without scrolling down, it slowly counts the number of photos she has taken. That is not the design choice of someone seeking speed. So she might be deliberately allowing it to be slow. That would track with her other works, one of which specifically says she finds beauty in imperfection.

deleted 2y ago

[deleted]

firecall 2y ago

For points 1 and 2: I recommend and use Cloudinary. Cloudinary can take care of all that for you! For point 3: You can add laoding="lazy" to the image tag, and get lazy loading for free, supported by the browser: * https://developer.mozilla.org/en-US/docs/Web/Performance/Lazy_loading https://developer.mozilla.org/en-US/docs/Web/Performance/Laz...

netsharc 2y ago

I'm still dreaming of an image file format where the file begins with the, say, 75x75px image, and then continues with higher and higher resolutions, where the browser can decide when to stop downloading. Ideally they wouldn't be redundant either, e.g. the 2nd block would contain just the data to upscale the 1st block to twice the resolution.. so the "75x75" thumbnail in a hidpi display would just need blocks 1 and 2..

BugsJustFindMe 2y ago
Dream no longer. You just described a progressive JPEG.
- dsego 2y ago
  The future was 30 years ago.
jfil 2y ago
Check out DZI (Deep Zoom Images), IIIF API and Zoomify.