This section contains a rule based manager for splitting traffic between main servers (apache, lighttpd, NGINX). A concept new most likely for web server panels, this tool lets you use all those servers in parallel for the same domain, so you can can optimize your serving strategy.
NGINX has a very smart cache system which can dramatically boost the loading speed. You will literally change your opinion of what a fast site means if you’ve never seen a similar config in action which takes us to STEP 2.
When you use caching, you must be careful what you cache though. Some things need to remain dynamic.
With WordPress, 3 important things may cover most of the setups:
Don’t cache admin and pages for logged in users (dynamic personalized data for each user may be visible on those page) – WordPress maintains a cookie which is an indicator of this state – wordpress_logged_in
For a few more technical details for the people that want to understand the technology more in depth, how this will work is that WordPress cache eligible requests will be sent to NGINX OSS which if it doesn’t have a cached page available or what it had is expired, it will just query apache for an updated page version.
If you want to create your more advanced configuration, it is totally possible. You can enable custom configs, click generate on the one you need and get the lines you can then edit.
After enabling NGINX OSS cache, it should already be a major improvement for your website speed. Depending on your theme design, you may still gain an extra boost of speed if you concatenate your css and js files. Concatenation means combining the resources in one file (one css file and one js file).