Do you have any quantifiable evidence that the page is slowed by using the cropper? Any request processed by ImageProcessor is cached in the browser and the server.
I was trying to find the recommendation in Google PageSpeed Insights but I think they have removed it now (it certainly used to be there when PageSpeed was a Chrome plugin)...
It used to be that some caching proxy servers did not cache static resources with querystrings, so not really related to speed.
Image Cropper makes the page slow
Hi,
On my page there are a log of images (appr. 100-120), and I'm using the Image cropper.
According to google pagespeed and gmetrix the biggest problem is: "Remove query strings from static resources".
Any suggestions?
Thanks, Levente
Hello,
It's not possible with ImageProcessor and it's questionable as to if this is really a worthwhile endeavour anyhow.
Have a read of this thread on StackOverfow discussing the recommendation
Jeavon
Do you have any quantifiable evidence that the page is slowed by using the cropper? Any request processed by ImageProcessor is cached in the browser and the server.
Hi,
No, I don't have evidence that the cropper is the problem. Just the tools said the url is the problem. It's slow, but can be other problem.
I was trying to find the recommendation in Google PageSpeed Insights but I think they have removed it now (it certainly used to be there when PageSpeed was a Chrome plugin)...
It used to be that some caching proxy servers did not cache static resources with querystrings, so not really related to speed.
is working on a reply...