BookLibary Component Support

Hello,
After using booklibrary pro with much success the component seems to slowing down. I'm thinking that's because I added many books but I know that a lot of users can add much more books without a problem.

The slow down doesn't affect all the website the home page is slow and also all pages where a component from booklibrary can be found.

here's the url : les-pingouins.com/

Thank you for the support

Hello,

Please try use "YSlow" extension for fireFox and Google Speed lab - for check site speed and for check what need optimize

Any way big number books will do site slow.

Thanks,
OrdaSoft team

Hello,
It seems that Yslow finds a problem with javascript ("This page has 15 external Javascript scripts. Try combining them into one." ) and ETags ("There are 55 components with misconfigured ETags" )

It seems there are something like 3000 books and furthermore only the front end is slowing. All the pages in the administrator's view are really fast.

I'm really confuse about this and I searching for others solutions with some plugins that can optimize joomla website.

If you have some advice about that it would be great.

Thank You for all the work on this component

Hello,

admin part work quickly, because it hasn't any not "useful" special effects.

for site optimization, need spend many effort and time and every time will possible do some thing more best.

May be need remove some special effects or some features.

Please try use "Google lab advices"

You may order from us site optimization, but that will not cheap.

Thanks,
OrdaSoft team

thank you for the answer.

I will investigate some more but maybe the order for "optimization" is not a bad idea. I keep that in a corner of my head

I will contact my web hosting too, maybe they can find where the problem is.

Hello (again)

I have some informations from my hosting

It seems that some SQL queries are perhaps not quite optimized and lead to overconsumption of resources on the MySQL server.
 
In this case, the server indicates 933,449 seconds for only 113 queries. The execution time seems excessive and causes can be :
 
- Missing one or more indexes on the tables used in the / the request / s
- The application is poorly written and examines a number of lines incoherent / indecent / unreasonable
- The type of the fields in the tables are inappropriate (varchar instead of int, etc.)
- Etc.