{"id":21447,"date":"2023-09-17T12:03:37","date_gmt":"2023-09-17T10:03:37","guid":{"rendered":"https:\/\/wpbeveiligen.nl\/?p=21447"},"modified":"2023-07-12T12:07:00","modified_gmt":"2023-07-12T10:07:00","slug":"the-big-caching-test-the-preparation","status":"publish","type":"post","link":"https:\/\/wpbeveiligen.nl\/en\/the-big-caching-test-the-preparation\/","title":{"rendered":"The big caching test – The preparation"},"content":{"rendered":"

In this article we will do everything we can to make a new WordPress website as slow as possible. Going against all our principles we turn on as many plugins as possible to get a load time of 5 seconds with as much executing Javascript, PHP & CSS processes.<\/strong><\/p>\n

This experiment serves to ultimate test the cache plugins and see which one works best under great pressure!<\/p>\n

The start<\/h2>\n

1 smooth server, 8 gig ram\u00a0Intel(R) Xeon(R) CPU E5-2683 v3 @ 2.00GHz (Several sites are currently running)<\/p>\n

1 new WordPress installation with the default WordPress 2017 theme<\/p>\n

Test method used:
\n– Google Developer Tools (Network view)
\n– Reload without browser cache!<\/p>\n

These tests did not use Pingdom<\/a> or GTmetrix <\/a> since they have various factors that cause incorrect information to be displayed.<\/p><\/blockquote>\n

Speed after fresh installation:
\n800 ms (milliseconds, also known as 0.8 seconds)<\/strong><\/p>\n

Now we all know that no WordPress website runs without plugins.
\nFrom previous tests we learned that each plugin adds 0.3 to 1 seconds to the loading time.<\/p>\n

Below the report of the plugins we have used, and the loading times that have been added.<\/p>\n

WooCommerce<\/em> +0.3 seconds<\/strong> (still without displaying products etc)
\nWordFence<\/em>+0.2 seconds
\n<\/strong>Count per day<\/em>\u00a0+0.1 seconds<\/strong>
\n<\/strong>
\nWe put the shopping cart and hit counter on the test page, but the site is not slow to get.
\nKnowing that most websites take between 3 and 9 seconds to load, we still have a long destructive way to test the caching plugin properly.<\/p>\n

We’re going to use some more plugins and data!<\/p>\n

We’re increasing the size to 432KB with a nice image of the sun that’s good for 110KB.
\n\"speed\"<\/p>\n

 <\/p>\n

 <\/p>\n

Then add a contact form (Contact form 7<\/em>)\u00a0+0.1 seconds<\/strong><\/p>\n

Then add Yoast SEO, which adds a few requests, but still no exciting loading time with: 1.65 seconds<\/strong>.<\/p>\n

\"wordpress<\/a>
\nNo visitor will drop out on this and Google pagespeed insights<\/a> also thinks it’s okay.<\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Conclusion so far, 5 plugins on a WordPress website are no problem at all.<\/p>\n

We’re going to increase the pressure!<\/p>\n

It’s time for the big guns, a Nextgen gallery<\/em> with 10 images. Nextgen makes 10 neat thumbs of that and only loads the images after clicking with a lightbox. Kudos to Nextgen \ud83d\ude09<\/p>\n

\"snelheid<\/a><\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

You can see that the website has shot up to 887KB in terms of data, but the server still loads the website much too fast for this test, 1.82 seconds.<\/strong><\/p>\n

For this test we just add a nice text of 442 words via Lorum Ipsum<\/a>.<\/p>\n

A text of 400 words has 3 kB, which means almost no delay.<\/p>\n

A page of 2 meters<\/h2>\n

We now have a page of 2 meters with a contact form, a large photo, a slideshow. Not to mention a 400 word story.<\/p>\n

The website loads within 2 seconds.<\/p>\n

<\/h2>\n

Why are those caching plugins so necessary?<\/h2>\n

Many websites use 30-40 plugins without shame. Or the images are not compressed.<\/p>\n

Anyway, you’ve come here for the big caching test… so we’ll have to keep going!<\/p>\n

From 2 to 5 seconds loading time?<\/h2>\n

We throw in another Youtube video (iFrame embedded) and are at a 2.15 seconds<\/strong><\/p>\n

\"youtube<\/a><\/p>\n

 <\/p>\n

 <\/p>\n

And.. A Polls<\/em>plugin, Cookie popup<\/em>,\u00a0\u00a0Tawk to live chat, Slider WD<\/em><\/p>\n

We are still at a fairly fast loading time of 3 seconds!<\/p>\n

We did reach 100 requests (Requests \/ objects to be loaded) that slow down the website.
\nIn a neat way we do not slow down the website, now we are going to activate another 10 plugins that we show on the page through widgets and [shortcodes].<\/p>\n

 <\/p>\n

122 requests, load 4.58 seconds\u00a0<\/strong>(Don’t mind the finish time, it is still increasing due to the slider at the time of reading<\/em>)<\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

As far as we’re concerned, it’s “Time” to test the cache plugins!<\/p>\n

The caching plugins,\u00a0 what do we test them for?<\/h2>\n

What are we going to pay attention to?
\nThe speed<\/strong> is self-evident, but we will mainly pay attention to the number of requests<\/strong>.
\nThat is what a caching plugin does: Merge and pre-calculate scripts so that you get the calculated data on your screen as quickly as possible with as little server load\/server requests as possible.<\/p>\n

And of course,<\/p>\n

Do the plugins<\/strong> still work? Is the website still loading properly<\/strong>? And, what about all those Javascript & CSS files being merged? Doesn’t that break up the styling<\/strong>?<\/p>\n

Part 2 will discuss this further.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

In this article we will do everything we can to make a new WordPress website as slow as possible. Going against all our principles we turn on as many plugins as possible to get a load time of 5 seconds with as much executing Javascript, PHP & CSS processes. This experiment serves to ultimate test […]<\/p>\n","protected":false},"author":4,"featured_media":9828,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[212],"tags":[],"_links":{"self":[{"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/posts\/21447"}],"collection":[{"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/comments?post=21447"}],"version-history":[{"count":0,"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/posts\/21447\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/media\/9828"}],"wp:attachment":[{"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/media?parent=21447"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/categories?post=21447"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/tags?post=21447"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}