Having the slideshow load only two or three slides ahead is indeed an option, but I’ve intentionally chosen not to go with this behaviour as it would ruin your SEO. Search engines are very big on finding images.
I’ve thought about adding in a setting to allow you to make this consideration on your own, but responsiveness had more priority over this feature.
The best I can do in the next major update is to optimize image resolutions by using the best fitting cropped version of the original image. Depending on what time there’s left, I may be able to add in your request. The next major update will be the one of version 2.3.0.
The best I can do in the next major update is to optimize image resolutions by using the best fitting cropped version of the original image.
Hi, there is no need to do this, as we can simply choose the size based on the area we setup the slideshow, which I’ve already done. The advantage in this plugin is that it uses the largest file, and isn’t affected by $content-width.
The issue with the slideshow is that it’s up the top of my page, even before any text. Until all slides load, no other images load, eg stuff I have in footer widgets.
An option would be load 1 image, then have something in the footer that triggers loading the rest of the stuff to start. At least the whole page looks loaded, rather than having the loading icon run for 30s.
In fact according to http://tools.pingdom.com/ even the light-arrows.png can’t load until the slideshow finished.
Loading the optimal resolution of images into the slides is something that has been requested by multiple users, it will be the main point of focus in version 2.3.0. Of course, if there’s no size that fits without having to stretch it, the original will be fetched.
I’ll add in your request into version 2.3.0 of the slideshow. This will indeed get the first couple of images, so that the rest of the site can load after that.
Yes, the elements that pose as the buttons are placed below the slides in the source code. I may need to change that.
