Full page caching stores complete HTML copies of pages so Nginx can serve them directly without running PHP or hitting the database. The presenter shows how to enable it in xCloud and explains why it's faster than plugin caches that still invoke PHP on every request.
Chapters
So let's look at the different types of web caching. First, we're going to look at full page cache. It saves on the server copies of full web pages. It avoids time-consuming page builds and uses more efficient delivery methods. Let me show you what I mean. I'm here in my xCloud admin panel, and you can see I have one site here. Going to click on it, and in the left under WordPress, you'll find Caching, and we have page caching turned on, and we have some options here. These three are WordPress plugins, and they're great, but the option we have turned on right now is a custom web server built just to serve static files, and this does not have to run PHP. All three of these plugins run PHP to do some work. Using Nginx does not. This makes it a lot faster. If your host supports Nginx caching, you should use it. It's great. So what this does is take a web page like this one. Uh, normally this page is built every time you request it. PHP files are run, database queries are run, template parts are put together, It's like a puzzle and that takes time. But if you have full page caching turned on, then it makes a copy of that and serves it instead of having to build the whole thing every time.