Part is page caching. This is certainly the most important function provided by w3tc. In addition to enabling page caching, if you do nothing, you will see a significant improvement in site performance. Thankfully, the setup is easy. The w3tc can use a variety of caching methods to cache static copies of website pages and posts (generally referred to as pages in the w3tc). In most cases, the default choice should be disk: advanced method. However, if the shared server user complains that the host is over using resources, or finds that the server is incompatible with the enhanced disk cache in the compatibility check test, disk:basic can be used instead. The
Private or virtual private server users can choose an opcode caching method. If you manage the server directly, you can install the preferred opcode caching method. If the server is a Windows system, opcode:wincache should be used. Memcache is designed for multi server managed environments. As a result, it can also be used when using cloud based hosting and some shared hosting providers. Used when available in a managed environment. Select the preferred page caching method (most disks: Advanced) – select save all changes. The
General settings: zoom out note: zooming out of CSS and JavaScript can also be done with hummingbird. If using hummingbird for scaling, make sure that w3tc disables this option. Folding JavaScript and CSS can cause site disruption, whether using w3tc or other plug-ins. Therefore, be careful when enabling the minify module. Automatic option combines and collapses all JavaScript and CSS resources. However, if this option is selected, each resource in the collapse menu cannot be used alone. The only way to learn is to try to automate, fine tune the settings from the drop-down menu, and determine how the site is loaded. If the site is damaged, please switch manually. If you are using shared hosting, select the disk caching method. Otherwise, select the same caching method as you selected for the page caching method. General setting: if the database cache site is on a shared server, set the database cache to disabled. Database caching is a resource intensive process. If the server is not strong enough to handle and store the load, the database cache will actually slow down rather than speed up the site. Database cache settings are simple. You simply select activate and match the method to the cache method you used earlier. To understand the reason why database caching will slow down the website, we must consider the bottleneck phenomenon that may affect the website performance. If the database query process slows down the site, you can reduce the number of database queries through the database cache to improve the site speed. However, if the site slows down due to insufficient server memory, the server caches the database, which will perform more operations on the overloaded server and further slow down the speed. So, how do you know if you should enable database caching? If the site is hosted by a shared server, it is better to disable database caching. If your site has dedicated resources (such as VPS or dedicated servers), enable them in the general settings menu. Then, test the site with and without database caching, and go to the settings for better results. General settings: object cache object cache is embedded in the word press core. Object cache
The module reduces the number of complex database queries executed by the server by caching objects in the object caching API. As with database caching, object caching is easy to set up, but may or may not actually contribute to site performance. Male object caching has the greatest potential to help very dynamic websites such as buddypress website and bbpress website hosted in personal environment. If you are running a blog or business site on a shared server, you can try, but you can almost certainly put it in a disabled state. To enable object caching, select the enable check box and match the caching method to the method used previously. General settings: Note browser caching: browser caching can also be performed using hummingbird. If using hummingbird in the browser cache, make sure that w3tc disables this option. Enabling browser caching is as simple as selecting a single check box and clicking save all changes. When browser caching is enabled, the site visitor browser will cache site resources. This allows you to load the page from the browser cache the second time you view the page. General settings: if CDN CDN (content transmission network) is used, CDN services can be integrated with w3tc. In this way, you can mirror files cached as CDNs on the web server and enjoy all the benefits of caching and distributed content delivery. To enable CDN integration, select the enable checkbox, select a CDN service provider from the CDN type list, and then click save all settings. Before the integration between w3tc and CDN is completed, you must access the CDN menu to add CDN credentials to w3tc. Cloudflare is not in the CDN service list. To use cloudflare with w3tc, please access the extension menu, activate the cloudflare extension, and then return to the general settings menu to complete the cloudflare integration. General settings: reverse proxy this option requires that varnish be installed on the server and that several advanced server configuration steps be taken. This operation can only be performed when hosted in a personal environment that has access to the server root. If you are interested in setting up Barney to work with w3tc, you can find a guide on tuts plus to guide you through the process. General settings: monitoring new real server monitoring can be integrated with w3tc. To use this service, you must install new realc on the server and register a new realc account. New realic must be installed on the server, so it is incompatible with shared hosting. If new realc is installed on the server and you have a new realc account, enter account credentials in this section to add server statistics to the w3tc dashboard. General settings: the first option in other sections of other general settings is used to activate the Google pagespeed part in the w3tc dashboard. To do this, you must first set the API key. In most cases, all other settings of other parts remain unchanged. Ensure that the override rule is selected by default. To prevent problems with w3tc notification rewrite rules, deselect. Forget it. File lock activation is disabled by default. File locking is not compatible with most shared hosting. However, if it is hosted in a personal environment, you can activate it to ensure improved site performance. Disk enhancement page optimization and disk cache minimization for NFS are disabled by default. This is an option that provides some performance improvements. Test the options as enabled and excluded to determine whether they should be enabled. Edge mode activation is production
In general, it is not recommended to provide CSS and JS files for logged in users that are different from logged out users. Minimize error notification should at least be set to administrator notification. This will send a notification to the site administrator when a collapse error occurs. The next section collapses, merges, and moves page components. This may damage your site’s presentation. You should continue to follow your site while you enable preview mode and make changes to avoid interfering with your site presentation. Collapse: the HTML and XML sections of the HTML and XML collapse menu are simple. A check box is provided to enable folding, inline CSS, and JavaScript, omit seeds from folding, and enable the removal of newlines. Male. Deselecting all these options will increase the site speed, except for the do not shrink seed option, which must remain unselected. The ignored comment line text area is used to identify HTML comments that should not be removed when html is folded. By default, a specific comment bar is located in this field and comments related to Google AdWords and screen readers are not deleted. If the HTML contains additional comments that you want to keep as a collapsed version of the HTML, add a comment line to the box to prevent it from being removed. Collapse: if the automatic method is enabled in the JS general settings menu to collapse JavaScript and CSS, only all JavaScript resources can be used at one time. The displayed menu is a simplified version of the following image. If you selected the manual method, you must scroll to the top of the zoom out menu again and select the help Wizard button. A list of JavaScript and CSS files detected by w3tc is displayed. Select an option, select all check boxes for JavaScript and CSS files, and then click apply and close. JavaScript and CSS files are added to the collapse menu for manual work. In the male area, confirm the box marked as a job. In this box, you can combine the JavaScript resources with the collapsed and scripted collapse options or control whether to merge. The include type drop-down menu provides options for loading JavaScript resources. Block each device until you find an option that doesn’t interfere with the site presentation If you can try the option, but it doesn’t work, stick to the default (masked) value. If you select the manual collapse method from the general settings menu, you can assign it to a single template or all templates and move it under the title, body, or body element to process each file separately for fine-grained control. The location and loading method of each file in the HTML document. If some files depend on previous files (for example, the jQuery file of jquery.js must be loaded before loading), you can also drag and drop files to reorder the loading order. The best setting is to move the file out of the header without blocking Load as one of the options. However, this is likely to cause the site to render badly. There is no way to view one file at a time, test in another location, and ensure that the site is loaded correctly. Zoom out: there are four CSS zoom out settings available. Activate: open the folding and combination of CSS files. Merge only: merges CSS files without collapsing. Delete reserved comments: delete comments from the merged CSS file Remove line breaks: removes line breaks from the merged CSS file. Select and enable all options except merge. If the site displays an interruption, deselect delete reserved comments and delete line breaks. If the site is still unmodified, switch from using to merging only@ In the import processing drop-down menu, select process. Generally speaking
. The first two fields of the menu, the default lifetime and garbage collection interval of cache objects, are used to set the lifetime of cache objects and the frequency of deleting expired cache objects. Excessive object caching can shorten object life or garbage collection time. Alternatively, if you want to increase the load on the server and don’t mind a larger object cache, you can increase both values In most cases, the default values are fine The next field, global groups is used to identify object groups that are shared between sites when a WordPress installation is a multisite network The idea is that some of those objects can be cached and reused across the network Male leave the global groups alone less you’re an experienced WordPress developer and are family with how these groups work Finally, the non persistent groups field is used to identify object fields that should never be cached in the object cache Once again, unless you are family with object groups leave this field alone Browser cache note: hummingbird can be used to enable browser caching and gzip compression In addition, hummingbird is easy to use and provides a nicer experience overall (even if we do say so ourselves) This menu has four sections to fine tune browser caching: general, CSS & JS, HTML & XML, media & other files The fields presented in each section are nearly identical As you adjust settings in the general section, those same settings will be applied to all subsequence sections Then you can override specific settings in the later sections after you’ve finished configuring the general section Because of this behavior, configure the general section first, and then, if necessary, proceeded to fine tune each subsequence section Browser cache: general the first four options in the general section are all similar to each other In essence, all four do the same thing: make sure that the data stored in the cache is still valid However, each does so in a different way Both the last modified header and Etag are stored by a browser and then used later to ask the server if new versions of the stored documents
Make a huge difference Best practice would be to select it, but doing so may cause some plugins to generate a bunch of 404s If that happens you’ll need to manually add the URLs for the offering resources to the field labeled 404 error exception list Browser cache: CSS & JS, HTML & XML, media each of these sections will inherit the values added to the general section However, you can use each of these sections to fine tune how each type of resources is handled in the browser cache User agent groups the user agent groups menu lets you handle users based on the user agent (device) they are using The most common use of this module is to redirect mobile device users to a mobile optimized version of a site The first section of the user agent groups menu is a self explanatory button you can use to create a group of users You can create multiple groups If you do, make sure to put them in order with the most important group at the top and the least important group at the bottom Users will be sorted into groups based on this order By default, both groups are pre populated. This group aims to group mobile users into two groups: smart phones (high group) and other Internet using mobile devices (low group). To activate the male group, select the use check box. If you installed a second topic that must be used for a specific user group, you can choose from the topic drop-down menu. If you have completely different sites that require mobile user redirection, add the URL to the field. To adjust the list of devices associated with a group, simply add it manually to the user agent text area. The error group referrer group menu is used to specify how users referenced from a specific source are handled. Users referenced from a particular source can get different topics or redirect to different URLs. Create a different cache for each referrer group to ensure that users in that group do not display cache resources that are not related to that group. A set will be pre populated at installation, including five major search engines. You can confirm that they are registered in the text field displayed as a recommender. To activate the male group, select the activate check box. The CDN CDN menu is used to mirror cached resources from the server to the CDN. Before accessing this menu, you must select the CDN to use from the general settings menu. Then go to the CDN menu and set the connection between w3tc and the selected CDN. If you use cloudflare, the process is slightly different. For more information, go to the extended menu. Scroll to the configuration section of the CDN menu to set the connection between w3tc and CDN. The specific details of the configuration section vary depending on the CDN service. After the connection is successfully established, you can continue to set the remaining CDN menus. There are several buttons at the top of the CDN menu
An information menu provides a brief, high-level overview of what the w3tc can do. The most interesting part of this page is a list of people who provide code, ideas, and experience for plug-in development. Close out and next step, that’s all: introduce the 16 w3tc menus in detail. If you have this tutorial and w3tc FAQs and installation menus, you can set up w3tc on all word press websites. The next post in this series will introduce the common problems and troubles encountered by word press users when setting up w3tc. Therefore, if there is a problem with w3tc settings, we will pay close attention to this post to help you solve the problem. What problems did you encounter when setting up w3tc? Do you have any questions about w3tc not discussed in this post? Please tell me your opinion. Labels: cache W3 total cache
