Have you ever wondered if there was a way to make your WordPress site much faster when loading your "static" pages?
You will tell me that there is the excellent w3 total cache (which we use for Beldy) and that does wonders side optimization of content cache. However, in my research, I got in the lead that it was possible to do better, that it was possible to make this whole process much more effective if we changed approach.
Skip this game if you are already familiar with w3 total cache.
W3 total cache will put a "tag" expiration on each static element of the site, if for example a visitor will want to open beldy.tk, the server that will send him the entire content is going to tell him if such or such resource is static and therefore will not be subject to a change. The logo of the site for example is a simpl
e static. PNG image, so your browser will save it in its cache so as not to have to re-download the server freeing up the bandwidth and sparing your connection of an unnecessary H
TTP request. If we decide to change this file, your browser will be notified using a return code in the heade
r that this resource has been changed and will reload it from the server. Then imagine the drastic gain in loading performance.
W3 total cache does not stop there, it also allows you to create a cache of the site database. If you visit an article, the SQL query that was used to retrieve the article is cached in a file thus facilitating its reading and then reducing the number of SQL queries sent to the database.
These techniques are very useful and can save valuable resources for both the server and the client.
Yes, but really static pushes the concept a little further. When you visit a dynamic page, it is initially in. php, the ser
ver processes it, transforms it into. html
and sends it to you. Until then, I don't teach you anything new. Imagine that this HT
ML page is saved on the server in such a way that it is served to you instead of the. p
hp page until there has been a change.
The server will only serve you a simple static page until there has been a concrete change in the content. More SQL queries, more processing of pages. php, j
ust HTML that transited from the server to the client.
This plugin proves to be very useful if you have a very large site under WordPress and you find that w3 total cache is not enough for your needs.
Hoping that this little discovery is useful to you!
The cookie settings on this site are set to "accept cookies" to provide you with the best browsing experience possible. If you continue to use this site without changing your cookie settings or if you click "accept" below, you consent to this.