I seem not to be able to access the site tomdhu (403 forbidden), so I can only give generic guidelines to avoid conflicts: first of all in W3TC you would want to disable all CSS/ JS optimizations as to avoid conflicts. Also in Asset Cleanup if you have CSS/ JS minification turn that off as well.
Now re. “will there be any benefit”; can’t say for sure given the “access forbidden” but esp. the “inline & defer CSS” option which allows one to ensure the CSS is not render-blocking is (afaik) not available in W3TC/ AC, so it might very well be worth to give it a try?
hope this helps,
frank
Thread Starter
tomdhu
(@tomdhu)
I cant see how you are getting through to tomdhu.com. That was put on divert to http://www.trapbarn.com 6 months ago. Please visit https://www.trapbarn.com.
-
This reply was modified 5 years, 4 months ago by
tomdhu.
I wasn’t, but I was getting blocked on trapbarn.com which seems to work now. As I wrote; I do think AO can help you improve esp. with regards to the CSS being render-blocking now, so why not give it a try? 🙂
Thread Starter
tomdhu
(@tomdhu)
Digging ion a bit deeper, I found that the 403 Forbidden was probably being triggered because clicking on the image activated a connection to the site’s upload folder in an attempt to load the image, if that makes sense.
It probably didnt trigger for me because our permissions granted to my IP address and so it would load the image directly on a black background.
I deleted all the images on the home page and the product images in Woo. I guess WP reconstructed a range of sizes of these images and so it alleviated the problem.
May I ask if this issue is resolved at your end.
Thanks
yes, I now can see the site 🙂
Thread Starter
tomdhu
(@tomdhu)
Phew, that’s a relief.
Many thanks.
