H dual TP? If your site is slow to load, causing you to wave your fist, it may be time for you to cache. Caching is important to quickly load WordPress sites. The optimized page cache can greatly improve the page loading speed of visitors and reduce the server load. There are many options for caching. WordPress Org (there are many, so we made a short list of \
Continue reading or skip using the following link: About everything about cache why fastcgi rule cache policy plug-in possibility (CON) everything is in your cache cowboy article. Check what is static server cache in detail and the reasons for recommending fastcgi (check static server cache fastcgi) Explain how to optimize site speed and user experience by implementing y. Let’s go. To render or import pages or posts in word press, you must send queries back and forth in the database. These posts and most pages will not be updated every day. The
In addition to the server parsing the site code itself, querying the database, returning the HTML document to the customer, and finally loading the page, the static cache also stores the single results of the first two steps and provides them to other people who request the document Static assets such as CSS, JavaScript, and images are stored in the browser cache, so browsers can search for them in the local cache. This is faster than reloading resources from the server on the page. The caching of WordPress has many advantages, including the improvement of speed and performance, the reduction of the load on the managed server, and the better ranking of search engines. As mentioned in the previous optimization article, there are many components that consider speed and performance and are therefore affected by other measurement items. The
There are many types of web servers, such as nginx, Apache, and Litespeed, as well as various cache modules, such as varnish and fastcgi. These modules work with the server to provide excellent caching. Some modules and servers in the cache field. Varnish is a Web Application Accelerator, also known as a cached HTTP reverse proxy. One of the main functions is to configure the language VCL. VCL provides excellent flexibility, and you can create policies for receiving request processing, such as changing the content to be provided, the location of the content to be imported, and the method of request or response. The
Nginx (pronounced engine-x) starts with a simple web server designed for maximum stability and performance. After caching, load balancing, WebSockets, index files and automatic indexing, it has developed into a powerful multi-performance server with the function of handling reverse proxy. Support fastcgi through cache. Nginx is currently the fastest growing open source web server. More than 450million sites rely on this technology, and its stability is incredible. We believe that fastcgi provided by nginx is the core. Please read the reason. Why fastcgi rule fastcgi is an improved version of the previous version of CGI (Common Gateway Interface). It is a binary protocol for interactive programs with the web server interface. The main function is to reduce the overhead related to the web server and CGI program interface, so that the server can process more web page requests per unit time. The
Fastcgi uses a continuous process to process a series of requests instead of creating a new process for each request. Using nginx fastcgi, users can create the same word press page as before
At the time of access, the page has been cached and provided by fastcgi, so the website will not perform the same PHP and database requests again. Therefore, users have faster server response time after initial access. In addition, php-fpm and MariaDB (MySQL) load are reduced and CPU usage is reduced. Finally, the server can handle more traffic with the same specifications, so as to better meet more demanding requirements. The
For visual information on how these elements work together to achieve excellent caching, see the following image. (object caching will be discussed later.) Use fastcgi and memcached object cache to provide browser requests. All word press pages have great advantages when using fast CGI. There are two content types (static and dynamic) to consider when setting the cache policy cache. Static content refers to all files stored on the server, which are the same every time they are sent to users. Dynamic content will vary according to the user’s own factors, such as access time, location, and device. The
Social media pages are a good example of dynamic content. Twitter seeds look completely different from users, who can interact with content to change content (for example, like, forward, or leave a message). E-commerce websites often use a lot of dynamic content. For example, woocommerce allows you to fully cache specific pages, such as home pages, shopping, and individual product pages. The exceptions are shopping carts, payments, and the my account page. Because the latest changes are not displayed, you do not want to fully cache these dynamic pages. The
Dynamic web pages are not saved as static HTML files. On the server side of the generation, it is usually generated through the source server rather than the cache. Dynamic content is difficult to cache because it is not available to multiple users (each is unique). However, as technology evolves, you can cache dynamic content. One way to speed up dynamic web pages is to use dynamic compression. In this way, the content is still provided by the source server rather than cached, but the resulting HTML file is much smaller to reach the client device faster. Object caching works in database queries just as page caching works in HTML page output. Object caching is an ideal solution for caching dynamic content. The
Like other caching components we discussed, there are several persistent object caching competitors in this field, the most famous of which are Memcache, redis and APCU. As long as the cache policy is set, no size is suitable for everyone. However, to some extent, the decision on the appropriate static caching strategy depends on the type of content that makes up the site. For sites that constantly add and approve user comments (usually in 1 minute) or sites with frequent new content as the standard, cache policies should be configured and deleted as frequently as every day or hour. For infrequently updated but regularly updated content, a 30 day cache policy is sufficient. The
For static elements such as logos, images, page fonts, JS and core CSS stylesheets, the maximum lifetime can be extended to 1 year. Although Google also says that there is no best caching strategy, it provides some tips to help you design caching strategies beyond the scope of static assets. These are: please ensure that the consistent URL uses the server provided authentication token (Etag). Determine the resources (such as CDN) that the mediation can cache, and minimize the changes in the cache hierarchy of the site that determine the best life for each resource (for specific parts of resources that are frequently updated (such as JS functions or CSS style sets), provide the code as a separate file)
