- Sep 26, 2018
- 241
- 374
3D-LOAD.NET ... Down??
- Thread starter Esens424
- Start date
- Sep 26, 2018
- 241
- 374
yeah, it was too slow, i'll find a solution... but first I waiting the server resetting
- May 23, 2019
- 628
- 412
Ok, i'm fixing the latest problems, I had to backup the website manually, that's why it take me so long, also i'm not an expert... I hope this time it goes fast, I installed nginx + apache + varnish 
Last edited:
I believe I can help you with that. I can see there are two large optimisations you can make.
First is the bandwidth usage - You're displaying full-sized images on the index pages that are scaled down within the HTML. This requires each visitor to download large images even if they are not interested in visiting the detailed page. You should consider having properly resized images for the index pages, and gain a drastic reduction in bandwidth usage.
Second is that you are accessing the database for every page. There is a limit (one you may be able to increase) to how many concurrent open connections to the database. A "temporary" solution to this would be to increase this limit if you can, and if you have enough RAM that would allow it to happen smoothly. The more ideal solution would be to have Static HTML pages created for each product detail page (not access the database at all).
Thank you for the useful tips, i'm actually using Smush image plugin, i through to convert all image from jpg to webp. for the second tip I just using redis, that should help to reduce database connection, I think the real problem is the poor image optimization...
- Dec 6, 2019
- 2
- 0
The image thing is definitely a huge problem. You're probably averaging about a meg per image on the index page. Those could fairly easily be reduced to 10% of their size (for the index page thumbnails, you should keep the high res image for the details page) with little loss to visual quality. Don't worry about webp. No one uses it. Just reduce the dimensions and compression on the jpegs and you'll be fine.
Last edited:
I put again the website in maintenance mode because I scale down all images, it will take a while...
That looks like it ought to work wonders.
Another potential solution to the image problem is to just offload that problem to a third-party image hosting site.
I tried them all, I'm about to give up... I don't understand why it's still slow...
I'm using w3 total cache with redis integration(memory cache) that cache, "object cache", "database cache" and "page cache" never had problem with that...