cache plugin site

Hi,

Our plugin is used to resize/crop images to the corresponding dimensions and then generate correct html/css for responsive images technic. Displaying of the correct image sized version is done natively by a browser according to the generated HTML and css media queries. There are no any javascript inside. And once page is generated it can be cached without any issues, because all display issues is done by a browser.

Thanks for the answer.

But I did not understand. Your plugin generates new image sizes according to the user’s browser resolution. And if the topic is adaptive and you need to generate 3-4 images for different screens?

You prepare a configuration file, which describes which image resolutions should be shown on different screens.
For example, you can specify to resize an image to 200×100 for screens less than 414 width, resize image to 800×600 for screens less than 1024 width and resize to 1200×800 for bigger screens.

During page load – plugin resizes all 3 images and save them. Then it generates <picture> tag (if you used rwd_image_attachment function) which explain browser which one to take based on screen size. Then browser defines what to show based on instructions provided in HTML. If you cache the page – you cache it with these instructions and images are generated already.

Thanks for the answer.
In general, it is clear. Tell me, does the <picture> tag work better than the <srcset> tag adopted in wordpress?

They work a bit different from each other.
When you use srcset browser “guesses” which image is the best and choose it depends on their algorythms. So in different browsers you can see different image loaded.
With picture tag you set strict rules how to show an image.

srcset in WordPress editor is the only way to keep back compatibility and implement some kind of responsiveness. Furthermore, it set all image sizes you have registered in srcset, and this generates huge html and is not optimatl.

The main feature of our plugin is the ability to replace image with another attachment on some resolution (for example in portrait mobile mode).

Thank you for the detailed answer.

You contribute a lot of useful knowledge.
One more question. Does your plugin remove all traces and images it creates after removal?

No, it use standard WP editor resizer, so it keeps all the same thumbs as usual. WP doesn’t have any removal features to cleanup resized images.

Clear.
So you need to make backUp file system of the site.

Thank you very much.

I will try to install your plugin today on one of the small projects.

You, as I see it, have a big project to support website optimization.

I was glad to help you.

On github there is more detailed docs, so please read them on plugin usage. It’s not trivial for a non-professional developers.

Would be great if you rate our plugin afterwards ??

Tell me please. And it’s better to delete the additional image sizes created by wordpress?

By recall – required. As far as use.

• This reply was modified 5 years, 10 months ago by korfiati_a.

By default, WP has 4 sizes: thumbnail, medium, medium-large (optional), large.
They can’t be deleted. You should set correct dimensions for them in a plugin config file.

Read github. In general, everything is clear.

The main thing is to set the size.
The rest except the main image is generated as the page loads. How much does it load the server? You can configure cron and how to generate images for those pages that have already been created?

I correctly, your plugin besides everything makes on-the-fly replacement of the native for WP <srcset> on <picture>?

Just to clarify – it resized the image on a FIRST page load or if you updated the config file for particular image size key. Next time the image won’t be generated and will be taken from disk.

Anyway, when you post content you usually check it on a site. This means that editor, who validates the content will generate all necessary sizes, so usual user won’t see any speed issues.

Server load depends on your configuration. If there are too much sizes for specific key – then you can have some delays on first page visit.
If you don’t use our plugin and have a lot of image sizes registered in WP – you wait this time on image upload and it can take much longer, because WP by default generate all registered sizes. But all images don’t need all available sizes to be saved on image upload.

Thanks for clarifying.
I understand this. I dkmayu what to do with the old records. It is also necessary to generate new images there. And this is a large amount.

I still check the performance of the <picture> tag on different devices.

Good day.
Sorry, another question.

How to specify the used image size for some pages of the site, where the images are placed in two columns. For example, for the desktop version I have two columns, and in the mobile one. How in this case the plugin will post images?