Changeset 3273051
- Timestamp:
- 04/15/2025 07:27:35 AM (12 months ago)
- Location:
- ergonet-varnish-cache
- Files:
-
- 2 edited
-
tags/1.0.11/readme.txt (modified) (4 diffs)
-
trunk/readme.txt (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
ergonet-varnish-cache/tags/1.0.11/readme.txt
r3273044 r3273051 11 11 Ergonet Cache for WordPress is a free plugin developed by Ergonet srl, an Italian hosting company, to drastically improve the performance of a WordPress website by using a server-side page caching system (NGINX Cache or Varnish Cache). 12 12 13 BENEFITS 13 == BENEFITS == 14 14 15 15 Using a server-side caching system increases your WordPress site's performance by a minimum of 30% and up to 70%. Keep in mind that the actual improvement will also depend on your overall website optimization strategy. 16 16 17 WHAT IS PAGE CACHE AND HOW DOES IT WORK? 17 == WHAT IS PAGE CACHE AND HOW DOES IT WORK? == 18 18 19 19 Page cache speeds up your website by storing the entire HTML of web pages directly on the web server, instantly serving them to visitors without needing to query the PHP server or the database again. Depending on your hosting plan, you can enable NGINX page cache (Equilibrio plan) or advanced RAM-based Varnish page cache (Progresso and Successo plans). 20 20 21 COMPATIBILITY 21 == COMPATIBILITY== 22 22 23 23 The Ergonet Cache plugin is compatible with all other website caching and optimization plugins, such as WP Rocket, W3 Total Cache, WO Optimize, etc. … … 25 25 A fundamental requirement for the plugin to work is enabling the caching system from the WebPanel (Ergonet client area available at https://webpanel.ergonet.it) by the user who purchased the shared or dedicated cloud hosting service. 26 26 27 HOW THE PLUGIN WORKS 27 == HOW THE PLUGIN WORKS== 28 28 29 Once the caching system is enabled from the Ergonet WebPanel and the Ergonet Cache plugin is installed and activated, it will work without any additional configuration. 29 30 Cache resource updates … … 34 35 On websites with a large amount of content, a full cache purge could also cause significant slowdowns due to WordPress needing to regenerate all requested pages or articles from scratch. 35 36 36 WHAT IS NOT CACHED 37 == WHAT IS NOT CACHED == 37 38 To ensure the plugin works efficiently, some resources and specific HTTP calls are never cached. These include: 38 39 39 Any page, article/resource visited by a logged-in user.40 Any page, article/resource where a no-cache header or similar is set.41 All requests made to the WordPress backend.42 All data submission requests (e.g., registration forms, contact forms, comments, etc.)40 * Any page, article/resource visited by a logged-in user. 41 * Any page, article/resource where a no-cache header or similar is set. 42 * All requests made to the WordPress backend. 43 * All data submission requests (e.g., registration forms, contact forms, comments, etc.) 43 44 44 HOW TO CHECK IF CACHING IS WORKING 45 == HOW TO CHECK IF CACHING IS WORKING == 45 46 The server-side cache system sets specific HTTP headers indicating whether the requested resource (link) is cached or not. To verify if your website is using the cache correctly, you must check for these HTTP headers. 46 47 It's essential to ensure you are logged out of the WordPress site you're checking, as well as from any other WordPress site open in other browser tabs. The first step is therefore to log out from the WordPress admin area. 47 48 Open the developer tools based on your browser: 48 For Firefox:49 49 50 Menu → Browser Tools → Browser Console50 For Firefox: Menu → Browser Tools → Browser Console 51 51 52 For Chrome: 53 54 View → Developer Options → Developer Tools 52 For Chrome: View → Developer Options → Developer Tools 55 53 56 54 Once the developer tools are open: … … 62 60 63 61 In the right-hand column, you'll see the response headers. The last header refers to the cache: 64 VARNISH CACHE HEADER 62 63 == VARNISH CACHE HEADER == 65 64 X-VC-Cache: HIT = the resource (page) is present in cache and was served from the Varnish cache system. This means the caching system is working properly. 66 65 X-VC-Cache: MISS = the resource (page) is NOT in cache and was generated by the WordPress application. This means the cache system was instructed by headers or custom rules not to serve the cached content to the visitor. 67 NGINX CACHE HEADER 66 67 == NGINX CACHE HEADER == 68 68 x-cache-status: HIT or STALE = the resource (page) is present in cache and was served from the NGINX cache system. This means the caching system is working properly. 69 69 x-cache-status: MISS = the resource (page) is NOT in cache and was generated by the WordPress application. This means the cache system was instructed by headers or custom rules not to serve the cached content to the visitor. 70 ENABLING THE CACHING SYSTEM FROM THE WEBPANEL 70 71 == ENABLING THE CACHING SYSTEM FROM THE WEBPANEL == 72 71 73 The NGINX caching system is enabled by default and doesn’t require any specific settings. 72 74 To enable the Varnish caching system, we recommend checking the dedicated guide: https://docs.ergonet.it/gestione-hosting/impostazioni-cache-server/cache-varnish 75 73 76 == Installation == 74 77 -
ergonet-varnish-cache/trunk/readme.txt
r3273044 r3273051 11 11 Ergonet Cache for WordPress is a free plugin developed by Ergonet srl, an Italian hosting company, to drastically improve the performance of a WordPress website by using a server-side page caching system (NGINX Cache or Varnish Cache). 12 12 13 BENEFITS 13 == BENEFITS == 14 14 15 15 Using a server-side caching system increases your WordPress site's performance by a minimum of 30% and up to 70%. Keep in mind that the actual improvement will also depend on your overall website optimization strategy. 16 16 17 WHAT IS PAGE CACHE AND HOW DOES IT WORK? 17 == WHAT IS PAGE CACHE AND HOW DOES IT WORK? == 18 18 19 19 Page cache speeds up your website by storing the entire HTML of web pages directly on the web server, instantly serving them to visitors without needing to query the PHP server or the database again. Depending on your hosting plan, you can enable NGINX page cache (Equilibrio plan) or advanced RAM-based Varnish page cache (Progresso and Successo plans). 20 20 21 COMPATIBILITY 21 == COMPATIBILITY== 22 22 23 23 The Ergonet Cache plugin is compatible with all other website caching and optimization plugins, such as WP Rocket, W3 Total Cache, WO Optimize, etc. … … 25 25 A fundamental requirement for the plugin to work is enabling the caching system from the WebPanel (Ergonet client area available at https://webpanel.ergonet.it) by the user who purchased the shared or dedicated cloud hosting service. 26 26 27 HOW THE PLUGIN WORKS 27 == HOW THE PLUGIN WORKS== 28 28 29 Once the caching system is enabled from the Ergonet WebPanel and the Ergonet Cache plugin is installed and activated, it will work without any additional configuration. 29 30 Cache resource updates … … 34 35 On websites with a large amount of content, a full cache purge could also cause significant slowdowns due to WordPress needing to regenerate all requested pages or articles from scratch. 35 36 36 WHAT IS NOT CACHED 37 == WHAT IS NOT CACHED == 37 38 To ensure the plugin works efficiently, some resources and specific HTTP calls are never cached. These include: 38 39 39 Any page, article/resource visited by a logged-in user.40 Any page, article/resource where a no-cache header or similar is set.41 All requests made to the WordPress backend.42 All data submission requests (e.g., registration forms, contact forms, comments, etc.)40 * Any page, article/resource visited by a logged-in user. 41 * Any page, article/resource where a no-cache header or similar is set. 42 * All requests made to the WordPress backend. 43 * All data submission requests (e.g., registration forms, contact forms, comments, etc.) 43 44 44 HOW TO CHECK IF CACHING IS WORKING 45 == HOW TO CHECK IF CACHING IS WORKING == 45 46 The server-side cache system sets specific HTTP headers indicating whether the requested resource (link) is cached or not. To verify if your website is using the cache correctly, you must check for these HTTP headers. 46 47 It's essential to ensure you are logged out of the WordPress site you're checking, as well as from any other WordPress site open in other browser tabs. The first step is therefore to log out from the WordPress admin area. 47 48 Open the developer tools based on your browser: 48 For Firefox:49 49 50 Menu → Browser Tools → Browser Console50 For Firefox: Menu → Browser Tools → Browser Console 51 51 52 For Chrome: 53 54 View → Developer Options → Developer Tools 52 For Chrome: View → Developer Options → Developer Tools 55 53 56 54 Once the developer tools are open: … … 62 60 63 61 In the right-hand column, you'll see the response headers. The last header refers to the cache: 64 VARNISH CACHE HEADER 62 63 == VARNISH CACHE HEADER == 65 64 X-VC-Cache: HIT = the resource (page) is present in cache and was served from the Varnish cache system. This means the caching system is working properly. 66 65 X-VC-Cache: MISS = the resource (page) is NOT in cache and was generated by the WordPress application. This means the cache system was instructed by headers or custom rules not to serve the cached content to the visitor. 67 NGINX CACHE HEADER 66 67 == NGINX CACHE HEADER == 68 68 x-cache-status: HIT or STALE = the resource (page) is present in cache and was served from the NGINX cache system. This means the caching system is working properly. 69 69 x-cache-status: MISS = the resource (page) is NOT in cache and was generated by the WordPress application. This means the cache system was instructed by headers or custom rules not to serve the cached content to the visitor. 70 ENABLING THE CACHING SYSTEM FROM THE WEBPANEL 70 71 == ENABLING THE CACHING SYSTEM FROM THE WEBPANEL == 72 71 73 The NGINX caching system is enabled by default and doesn’t require any specific settings. 72 74 To enable the Varnish caching system, we recommend checking the dedicated guide: https://docs.ergonet.it/gestione-hosting/impostazioni-cache-server/cache-varnish 75 73 76 == Installation == 74 77
Note: See TracChangeset
for help on using the changeset viewer.