Problem with Cache Lite Speed plugin after deployment of GCP
- Thread starter Locksmith Unit
- Start date
This WordPress from GCP deployment, i said that in the title.
it's the must simple installation of WordPress with open lite speed comes as a one click installation:
https://docs.litespeedtech.com/cloud/images/wordpress/
it's the must simple installation of WordPress with open lite speed comes as a one click installation:
https://docs.litespeedtech.com/cloud/images/wordpress/
where?!?!?!?!???!!!?!?!?
you decide "deployment of GCP" full describe your problem and enviroyment?
problem with LSCache discussed here: https://www.litespeedtech.com/support/forum/#cache-acceleration-solutions.36
with Wordpress LSCache plugin here: https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/
you decide "deployment of GCP" full describe your problem and enviroyment?
problem with LSCache discussed here: https://www.litespeedtech.com/support/forum/#cache-acceleration-solutions.36
with Wordpress LSCache plugin here: https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/
I suspect it's the deployment, even when i turn off the LSCACHE plugin the error persist in Google Pagespeed.
I have 2 websites on GCP with openlitespeed-wordpress deployment:
https://docs.litespeedtech.com/cloud/images/wordpress/
Both of them get the same error. (even if i turn off the LSCACHE Plugin)
From the other hand, i have another client, i built for him 10 websites on cPanel server with the same "THEME" on WordPress
and they not do this issue on Google page speed test (have sites they identical to what i open with Lite Speed deployment)
So i pretty sure it's the deployment himself (openlitespeed server).
BTW,
both of the clients sitting on the same machine (e2 – micro from Google Cloud)
they just not the same deployments. (one of the client is openlitespeed-wordpress, and the other client is cPanel server + WordPress open via cPanel interface)
I have 2 websites on GCP with openlitespeed-wordpress deployment:
https://docs.litespeedtech.com/cloud/images/wordpress/
Both of them get the same error. (even if i turn off the LSCACHE Plugin)
From the other hand, i have another client, i built for him 10 websites on cPanel server with the same "THEME" on WordPress
and they not do this issue on Google page speed test (have sites they identical to what i open with Lite Speed deployment)
So i pretty sure it's the deployment himself (openlitespeed server).
BTW,
both of the clients sitting on the same machine (e2 – micro from Google Cloud)
they just not the same deployments. (one of the client is openlitespeed-wordpress, and the other client is cPanel server + WordPress open via cPanel interface)
and ??????
GCP always use only Wordpress images?
1.
2. how your manage views?
because
pagespeed use
- for Mobile:
Unthrottled CPU/Memory Power: 1167 CPU throttling: 4x slowdown (Simulated) Screen emulation: 412x823, DPR 1.75 Axe version: 4.7.0
Slow 4G throttling
- for Desktop:
Unthrottled CPU/Memory Power: 1395 CPU throttling: 1x slowdown (Simulated) Screen emulation: 1350x940, DPR 1 Axe version: 4.7.0
if you use incorrect settings of LSCache for Mobile view then pagespeed can use lscache from Desktop view.
even if you turn off LSCACHE plugin but NOT Purge lscache then system still can use cached pages
GCP always use only Wordpress images?
1.
2. how your manage views?
because
pagespeed use
- for Mobile:
Unthrottled CPU/Memory Power: 1167 CPU throttling: 4x slowdown (Simulated) Screen emulation: 412x823, DPR 1.75 Axe version: 4.7.0
Slow 4G throttling
- for Desktop:
Unthrottled CPU/Memory Power: 1395 CPU throttling: 1x slowdown (Simulated) Screen emulation: 1350x940, DPR 1 Axe version: 4.7.0
if you use incorrect settings of LSCache for Mobile view then pagespeed can use lscache from Desktop view.
even if you turn off LSCACHE plugin but NOT Purge lscache then system still can use cached pages
Last edited:
@Locksmith Unit
It seems like an issue from the Lighthouse side, see https://github.com/GoogleChrome/lighthouse/issues/15075
It seems like an issue from the Lighthouse side, see https://github.com/GoogleChrome/lighthouse/issues/15075