Hi Alejandro, the xajax still appears to be showing up on page loads despite turning off the ajax pagination. The main thing I can see that is causing the bulk of the size is from the module calling all the theme images/files etcwhen IMO it really does not need to do so. When you take into consideration the 16116 bytes of the main theme css file and the remaining other files (images etc) weigh in at 37102 bytes being able to configure the module more easily would make a huge difference - for instance in my case I do not need most of the theme css images to load, simply the stars and the editor rating icon, no doubt others would want to eye-candy theirs up a little so there is a flipside.
What would make more sense is a less centralised theme so that in the module template an individual css can be created based on the individual requirement of the module in question, removing 53kb+ from loading on a frontpage could make the difference between being able to use Jreviews to its full potential or using a stripped down version of what was planned.
I must say though, I have huge respect for the work you have put in to this component and I love it! I would like to see it keep improving though so I hope these suggestions are of some use.
cheers
leigh
