| QUOTE (GeePa @ November 24, 2013 02:50 am) |
| However, it looks like there are over 3500 image references in the file. |
Yikes Image may be NSFW.
Clik here to view.
- thanks for noticing this - something of a sleeper! Image may be NSFW.Clik here to view.
Photo images for logs are returned when logs are fetched via the api and to keep the display to a minimum they do not show by default (you need to click on the link to see them)
However, the real problem here is that the actual images are being fetched by the browser in the background. The images have links and the browser is fetching the data for these images (regardless if the image is currently showing or not). So all those images are being fetched even though few (if any) will actually be viewed by the user.
So we can do better here. That is, I will look at changing the javascript in the links so that the images will only be fetched on demand (when you click to view them) rather than in the background.
This should achieve quite a few things:
1. Make the page finish loading much quicker when there are many logs that have pictures
2. Stop the memory bloat
3. Save a lot of bandwidth! Image may be NSFW.
Clik here to view.
I will change this in the next build.
