rfcontreras

I've solved all the new features speed improvements using pagespeed module with Redis, on the high 90% in PageSpeed Insights, GTMetrix and all "A" in webpagetest. It's nice to see all these improvements addressed..
Some suggestions
Create different size avatars instead of using a 200x200 image on a 34x34 placeholder, there are CSS's that dynamically resize the originals, at the expense of bandwidth.
Articles images have the same problem, if I choose a 1000x1000 image, on the record list every article will download the ORIGINAL image and resize it with CSS... huge bandwidth usage.
Reduce the DOM tree...it's huge 
Saludos

I've solved all the new features speed improvements using pagespeed module with Redis, on the high 90% in PageSpeed Insights, GTMetrix and all "A" in webpagetest. It's nice to see all these improvements addressed..
Some suggestions
Create different size avatars instead of using a 200x200 image on a 34x34 placeholder, there are CSS's that dynamically resize the originals, at the expense of bandwidth.
Articles images have the same problem, if I choose a 1000x1000 image, on the record list every article will download the ORIGINAL image and resize it with CSS... huge bandwidth usage.
Reduce the DOM tree...it's huge 
Saludos

I've solved all the new features speed improvements using pagespeed module with Redis, on the high 90% in PageSpeed Insights, GTMetrix and all "A" in webpagetest. It's nice to see all these improvements addressed..
Some suggestions
Create different size avatars instead of using a 200x200 image on a 34x34 placeholder, there are CSS's that dynamically resize the originals, at the expense of bandwidth.
Articles images have the same problem, if I choose a 1000x1000 image, on the record list every article will download the ORIGINAL image and resize it with CSS... huge bandwidth usage.
Reduce the DOM tree...it's huge 
Saludos

I've solved all the new features speed improvements using pagespeed module with Redis, on the high 90% in PageSpeed Insights, GTMetrix and all "A" in webpagetest. It's nice to see all these improvements addressed..
Some suggestions
Create different size avatars instead of using a 200x200 image on a 34x34 placeholder, there are CSS's that dynamically resize the originals, at the expense of bandwidth.
Articles images have the same problem, if I choose a 1000x1000 image, on the record list every article will download the ORIGINAL image and resize it with CSS... huge bandwidth usage.
Reduce the DOM tree...it's huge 
Saludos

Yeah: