{"id":14396,"date":"2017-09-16T09:31:55","date_gmt":"2017-09-16T08:31:55","guid":{"rendered":"https:\/\/www.milcraft.nl\/?p=14396"},"modified":"2018-09-07T11:25:45","modified_gmt":"2018-09-07T10:25:45","slug":"the-importance-of-cache-in-wordpress","status":"publish","type":"post","link":"https:\/\/www.milcraft.nl\/en\/het-belang-van-cache-bij-wordpress\/","title":{"rendered":"The importance of cache in WordPress"},"content":{"rendered":"
\"Milcraft

Loading time and optimisation of milcraft.co.uk at Pingdom<\/p><\/div>\n

Load time is one of the 200 points looked at for Google when it comes to how high a website is displayed. Along with search terms in the text, title, headers, regular new content, mobile version and SSL, it is one of the more important points out of these 200.
\nSo definitely an important point to do something with and optimise your WordPress website!<\/p>\n

How to improve WordPress load time?<\/h3>\n

Hosting<\/strong>
\nA good load time starts with picking the right hosting party. Many hosting parties put too many websites on one server, which causes longer load times.
\nThere is also a difference between the type of disks on which the website runs. This can be HHD (spinning parts, less fast) or SSD (no spinning parts, fast). So in principle, a website running on SSD will already run a lot faster. Of course, we only offer SSD hosting and ensure a good distribution of websites across our servers.<\/p>\n

Cache \/ caching<\/strong>
\nNow WordPress, like other CMS systems, has the disadvantage (compared to websites, which do not have a CMS<\/a> have) that loading time is higher on average.
\nOn each visit, all plugins are called to generate the page.
\nUsing fewer plugins can help, but really spectacular improvements will come about thanks to caching (temporary memory).
\nBy cache means repository and allows you to store things you often need when loading pages.<\/p>\n

Types of cache \/ caching<\/h3>\n

Pagecache<\/strong>
\nWith WordPress, each visit generates a new page from the various components. Over and over again.
\nIn a nutshell, using cache turns WordPress pages into a static page. The first visitor after turning on the cache loads the page and it is then added to the cache.
\nSecond and subsequent visitors will have a faster load time. This can save seconds, up to 90% of the original load time.
\nYou can get this done with a (mostly free) plugin like W3 Total Cache<\/a> or Fastest Cache<\/a>.<\/p>\n

Browser cache<\/strong>
\nThe browser cache is in the visitor's browser. You therefore have limited influence here. However, a max-age can be sent with the Leverage Browser Cache so that the browser knows how long certain elements should be kept in the cache.<\/p>\n

Database caching<\/strong>
\nThis ensures that, for example, frequently requested queries on the website can be loaded from the cache. The outcome of such a query then does not have to be compiled every time.<\/p>\n

HTTP reverse proxy caching<\/strong>
\nHere, as a site owner, you usually have no influence, and is arranged even before the web server. Example of caching HTTP reverse proxy is Varnish<\/a>.
\nIt receives queries (requests) from the clients and tries to answer them from the cache.<\/p>\n

Still important to know<\/h3>\n