Jump to content

Serving Scaled Images - Speeding Up Display Question


Recommended Posts

After running Webpagetest.org performance testing many times, i notice that the images for "Featured Products" and other product images are all being scaled by html.

 

Since we are only allowed to upload one size image for each file (which is usually a large image 800x800px) I expect that prestashop will autoscale and optimize the images in the backed.

 

But i find that for featured products which is displayed on the homepage the images are not scaled?

 

It seems tat all the images are re sized in html or css...

 

what this does is unnecessary increase overhead and downloads the larger image.

 

Anyway have a solution to this or experiencing the same problem?

 

Ricky

 

See From Webpage Test

 

>>>The following images are resized in HTML or CSS. Serving scaled images could save 211.3KiB (78% reduction).

Link to comment
Share on other sites

Prestashop does scale them to the needed size, but every theme calls for a different size. Are you using the default them or a custom theme? 

 

Edit: At the same time if you are using a responsive theme, that is how they work, by scaling images. 

Link to comment
Share on other sites

hi, firstly i really like your blog.

 

I am using a custom theme, however he (the developer)  informs me that the preferences images have not been changed from the default theme, and the featured products / new products / or product listing images should not be changed from prestashop default theme.

 

But when run through the webpagetest i find that somewhere along the line the images are being changed in html.. i will need to look in to this further and perhaps try to regen again.

 

based on what you said this should not happen, so it could be my theme faults.

 

Also i dont know many people who use the current default theme without making significant aesthetic changes.

 

I like your blog, and i am pressing hard to get my site to load in 2.5 seconds, i am stuck on 5 right now.

 

One thing i noticed is that why do so many js calls get loaded in header.tpl. ??

 

Thanks

RICKY

Link to comment
Share on other sites

Thanks, I try my best.

 

See like this site here, in the home featured it uses the home-default image size. http://screencast.com/t/dGtn8LNBO8Yi  It is properly scaled. You see in the image url it says home-default, that is how you can tell which image set is being used for an image. Now some themes will scale the image down on the front page and use the home-default in the category pages full size, so you have to check there before you alter the image size. If that is not the case, you can go to Preferences -> images in your back office and change the size of the home-default image to the size it needs to be. Then go further down the page and regenerate the products -> home-default images. That will fix your issue.

 

About the js files, do you have ccc enabled in your performance tab? 

Link to comment
Share on other sites

Hi, I will try that,

 

For the js files, yes i have all the optimizations enabled. See point 3 below.

 

 

All tests with yslow and webpagetest.org tell me to 

 

1) Combine Images in to sprites, which we are working on

2) Serve Scaled Images <-- this i am currently working on

3) Defer parsing of Javascript

 

http://www.webpagetest.org/pagespeed.php?test=140109_F1_92P&run=1&cached=0

 

Does enabling CCC defer parsing of JS? can i put a async tag or something to speed it up.  
 

Does the default theme have a lot of js in the header? what are my options? 

Thanks.

Link to comment
Share on other sites

Its strange that i get a page speed score of 93/100 but i get a F for first byte time, but in the summary first byte is 1.178s which is pretty good isn't  it?

 

I showed this to my host and they are also quite confused as to why i would get a F but the time is 1.178s

 

Thanks for looking over this.

 

Server is based in Singapore and testing is being doing from Singapore.

Link to comment
Share on other sites

It must be 3rd party module's js files. It is a pain, but they can be condensed into one js file by hand. 

 

As for the async tag, it is not that easy. What they are wanting is for the main loaded scripts be moved to the bottom of the page and the non essential scripts to be written after the page load. A technique that pretty much does not work on e-commerce sites. 

 

As for the time, that is not a good time to first byte. You want somewhere in the area of .2 seconds or under. 

Link to comment
Share on other sites

×
×
  • Create New...