elleremo

I understand that the cart page is excluded from the cache. But my original question and my problem is different.

Above, in the message with screenshots, you can see how two identical sites behave differently. The plugin is enabled on the main site, and disabled on the test site.

When I was talking about shopping cart and adding products, I meant that as long as you have products in the cart on the main site, the cache also does not work on other pages (and this is normal and so intended).

I’m talking about the fact that when you log in or you have something in the trash, the presence of the w3 total cache plugin slows down page loading – i.e. the plugin disables its caching for all pages when the user is logged in or when he has something in the trash.

And such pages start loading slower than when the plugin is completely disabled.

That is, if you disable it, they will load faster. Because on a s test site without a plugin, pages are not cached and load faster.

In the screenshots (which were above in the messages) – it can be seen that when the plugin is enabled, the user for whom caching is disabled (because he logged in or put something in the cart) – then this user waits a very long time before he sees the page.

And on a website without a plugin, the page is visible as soon as it is loaded, after which the “content download” already goes

• This reply was modified 1 year, 4 months ago by elleremo.
• This reply was modified 1 year, 4 months ago by elleremo.

Just to confirm, you are referring to Logged in users when you say “authorized users”

Yes, that’s right.

Caching is disabled for logged-in users on the main site (and for those who have added something to the cart). So you could add something to the cart to see what I described above and see the differences with the test site.

once again, I note that even if disable all the caching settings of the plugin, but leave the plugin itself active, then the problem remains.

I was a little stupid. Of course, you saw a cached copy of the page. I took screenshots for authorized users for the main site and for the test site.

Main Site (authorized)

View post on imgur.com

Test Site

View post on imgur.com

The screenshots show that the server response time with the W3 total cache plugin is large, but without it it is small.

And yes, the total loading time in both cases is comparable, but the feeling of speed is definitely higher on the test site. Apparently the reason is that when the plugin is enabled, the page is not displayed until it is fully ready. And on the test site, the content is visible as soon as the server responds.

If you have time, look at the same page after logging in (caching is disabled for authorized users) to see the same as me. I hope I’m not asking for too much.

https://nikifilini.com/my-account/?lang=en

Login: petrozavodsky
pass: uWW-BNL-U3m-p7J

As for the environment, here are the basic data.

PHP: 8.0.30
Mysql: 8.0.34
Nginx: 1.18.0

WooCommerce: 8.8.1
WordPress: 6.3.1
W3 Total Cache: 2.4.1

To the production server:

CPU 24 core,
8Gb RAM
120Gb nvme

Test Server:
CPU 8 Core
8Gb Ram
60Gb nvme

I am ready to provide any other data, including access to the admin panel of the test site. But I do not know how to transfer the data to you without displaying it here.

• This reply was modified 1 year, 5 months ago by elleremo.

This is a link to one of the pages of the main site:
https://nikifilini.com/product-category/new-ru/

This is a link to the same page of the test site:
https://83.222.8.176/product-category/new-ru/

This problem has been observed for the last year, it seems to me.

I meant that I have been observing this problem since I started working on the site (maybe the reason is me, haha). Plugin updates and Woo/Wordpress did not save the site from this problem – maybe the problem is really in the server configuration or in the database.

Perhaps by updating the pages on both links several times, you will see differences in the features of their loading and will be able to understand where to move me to solve the problem. Thanks!