Making WordPress faster
Making WordPress faster
In SSH, as root, run:
Then install W3TC plugin in WordPress.
Download https://raw.githubusercontent.com/myves ... /W3TC.json as file to your computer.
Import that file in W3TC settings.
Code: Select all
apt update && apt -y install memcached php-memcached php-memcache
Download https://raw.githubusercontent.com/myves ... /W3TC.json as file to your computer.
Import that file in W3TC settings.
Re: Making WordPress faster
Cheers for that.
With various metrix sites throwing a little fit if browser cacheing isn't enabled, what are your thoughts on there maybe being a checkbox option with an input field for the cache expiry value, on NGINX basic options page to add it to (or remove it from) the server section of the conf?
With various metrix sites throwing a little fit if browser cacheing isn't enabled, what are your thoughts on there maybe being a checkbox option with an input field for the cache expiry value, on NGINX basic options page to add it to (or remove it from) the server section of the conf?
Re: Making WordPress faster
If you think on this:
to be honest, I never played with that, so I would leave these default values.
Code: Select all
# File cache settings
open_file_cache max=10000 inactive=30s;
open_file_cache_valid 60s;
open_file_cache_min_uses 2;
open_file_cache_errors off;
Re: Making WordPress faster
I believe those settings are to do with the file cache on the server? I'm meaning something like this to go into the "server" config section of the NGINX conf to set browser cache expiry:
The period is arbitrary and could be set by the user via an input. Easy enough to manually add, but a fairly common thing to enable browser cacheing these days.
Code: Select all
location ~* \.(txt|xml|js|css|flv|ico|pdf|avi|mov|ppt|doc|mp3|wmv|wav|mp4|m4v|ogg|webm|aac|eot|ttf|otf|woff|svg|jpg|jpeg|png|gif|swf|webp)$ {
expires 8d;
}
Re: Making WordPress faster
but it's already 'max' - https://github.com/myvesta/vesta/blob/m ... g.stpl#L15
Code: Select all
expires max;
max
This is the opposite of the “epoch” value. The Expires header will be equal to “31 December 2037 23:59:59 GMT”, and the Cache-Control max-age set to 10 years. This basically means that the HTTP responses are guaranteed to never change, so clients are free to never request the same thing twice and may use their own stored values.
Re: Making WordPress faster
dpeca wrote: ↑Tue Jul 28, 2020 6:10 pmIn SSH, as root, run:Then install W3TC plugin in WordPress.Code: Select all
apt update && apt -y install memcached php-memcached php-memcache
Download https://raw.githubusercontent.com/myves ... /W3TC.json as file to your computer.
Import that file in W3TC settings.

Do you recommend this improvement, on woocommerce sites?
Re: Making WordPress faster
Yes, it will works without any issues.
-
- Posts: 6
- Joined: Wed Oct 21, 2020 4:27 pm
Re: Making WordPress faster
Hello
I have similar issue. VPS with 16 CPU cores and 16G RAM, hardware utilized in 10%. Apache+Nginx+Mysql+PHP-FPM7.4+CloudFlare and TTFB for WP website (good theme, some plugins, nothing special) 1,5-2sec :/ It is for the first load in the browser, then it is much faster...
Played with some options, but no luck so far. Any tips welcome
I have similar issue. VPS with 16 CPU cores and 16G RAM, hardware utilized in 10%. Apache+Nginx+Mysql+PHP-FPM7.4+CloudFlare and TTFB for WP website (good theme, some plugins, nothing special) 1,5-2sec :/ It is for the first load in the browser, then it is much faster...
Played with some options, but no luck so far. Any tips welcome
