{"id":4469,"date":"2020-10-30T22:09:32","date_gmt":"2020-10-30T21:09:32","guid":{"rendered":"https:\/\/webhosting.de\/?p=4469"},"modified":"2024-02-15T14:15:05","modified_gmt":"2024-02-15T13:15:05","slug":"so-reach-you-100-100-points-at-google-pagespeed-for-your-wordpress-website","status":"publish","type":"post","link":"https:\/\/webhosting.de\/en\/so-erreichst-du-100-100-punkte-bei-google-pagespeed-fuer-deine-wordpress-website\/","title":{"rendered":"How to achieve 100\/100 points at Google Pagespeed for your WordPress website"},"content":{"rendered":"

Google Pagespeed Insights<\/a> is the well-known website tool with which you can check and optimize all parameters relevant for the search engine. You can click on the link above, or you can see a daily updated value of your site in the administration system.<\/p>\n

In this manual we show you how easy it is to use the page speed score<\/strong> from 100\/100<\/strong> to reach. You can do it too.<\/p>\n

For our example we used a demo website with all kinds of content and a well-known theme, which also includes the usual plugins. So it's exactly the same thing you use to create good websites.<\/p>\n

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

We're here for the theme The7<\/strong> decided. But it doesn't really matter which theme you use. The main thing is that it is up-to-date and offers a few setting options for the creation of the website.<\/p>\n

You need that for a fast website.<\/h2>\n
    \n
  1. a fast webhoster<\/strong> by experience<\/li>\n
  2. a clean current WordPress<\/a><\/li>\n
  3. the correct settings for the web server<\/li>\n
  4. a tool for optimization and caching<\/li>\n<\/ol>\n

    In this example we use WP Rocket<\/strong>. These tools all do the same thing. They compress text files, merge the code and, if necessary, create a static page as a copy.<\/p>\n

    This enables the visitor to call up the page quickly.<\/p>\n

    Static pages are reminiscent of html code from back then. Websites that consist of simple html code and images are still the fastest. But not dynamic. With these plugins the cache is rebuilt again and again as soon as something changes on the page.<\/p>\n

    Tip: Deactivate the WordPress Cronjob<\/strong>. It is not really a cronjob in the real sense, but it is always called when a visitor comes to the page. We will show you how this works in another article.<\/p>\n

    Google Pagespeed Insights<\/h2>\n

    Enter your current website on google and see the performance.<\/p>\n

    Normally you will get values in the yellow range up to 85 if the webhoster has a good server.<\/p>\n

    In our standard installation PSI showed us 85\/100 in the desktop view.<\/p>\n

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

    Somewhat misleading, however, is the statement that the server responded slowly. Here the time to the first byte is meant, which is transmitted.<\/p>\n

    There are very many factors that play together here. Often you will reduce the so-called TTFB (Time to first Byte) if you fix all other points.<\/p>\n

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

    Google conveniently offers the optimized code for many points for download. But I recommend to use only optimized images in the website.<\/p>\n

    This can even be done free of charge e.g. with the Tinypng Panda<\/a> ...to take care of it.<\/p>\n

    \"tinypng<\/a>
    Tinypng.com Panda eats the superfluous bytes.<\/figcaption><\/figure>\n

    However, most themes also create their own images in different sizes, so that there is always a need for new optimization.<\/p>\n

    It is therefore recommended to occasionally simply re-optimize and overwrite all image files on the web server.<\/p>\n

    Pingdom, GTMetrix and Co.<\/h2>\n

    There are of course other check pages as well. However, here there is often the problem that the retrieval is made from abroad and therefore not meaningful enough to simulate the usual visitor from Germany. It is also important to know that some test programs cannot handle http\/2 and exactly ignore the advantage of http\/s, i.e. the parallel transmission of data over a connection, and interpret this negatively.<\/p>\n

    \"gtmetrix\"<\/a>
    GTMetrix Performance Report<\/figcaption><\/figure>\n

    TTFB or total charging time?<\/h2>\n

    Basically the result of the total loading time is what counts. The first byte depends on many factors which are difficult to influence. A page that is not compressed usually has a very low TTFB value than a perfectly compressed page. But the total load time with compression is of course faster for a page with a lot of content. How google rates this in the end is nebulous. We even have pages that load slowly because the software is outdated and a PSI value of 68, but with 28K organic keywords we get about 1000 visitors per day. But with comparable sites the site with the better values will surely be listed higher.<\/p>\n

    CDN and acceleration modules<\/h2>\n

    There are also modules that store static data on other servers and deliver it depending on the location of the visitor. This reduces the number of connections to the server and thus also reduces the so-called TTFB. Here caches from akamai, cloudflare or incapsula can be used which also offer compression and optimization depending on the booked service. A small (D)Dos protection is also included, as long as the connection is made completely via these providers.<\/p>\n

    \"cloudflare<\/a>
    Cloudflare Trafficanalysis<\/figcaption><\/figure>\n

    Speedkit for Plesk<\/h2>\n

    There are e.g. for Plesk<\/a> a plugin that can make the website faster with a few clicks. In my test, however, exactly the opposite was the case. The main problem with such plugins is the fact that the cache only starts when the visitor looks at the page a second time, or first establishes a connection to the system.<\/p>\n

    The advantage is that you can easily activate it without making any changes to your system. But the disadvantage is the missing speed for 1 View visitors. For this reason you don't see any change with the usual check programs, because they always visit the site without caching like a completely new user.<\/p>\n

    \"speedkit-website<\/a>
    Speedkit for Plesk is designed to make websites faster. But it doesn't always work.<\/figcaption><\/figure>\n

    Since most visitors often only come to the page via a link of a search engine, it brings no speed advantage for these visitors. With on-board tools you can manage quite well without external caches. Also in terms of data protection, especially DSGVO and the upcoming ePrivacy Regulation, the use of such services is not suitable. It already lacks a Contract<\/a> to the order data processing when ordering these services.<\/p>\n

    This way you make the website faster.<\/h2>\n

    The most important point: The right web host.<\/p>\n

    Seen from the outside, everyone web hosting provider<\/strong> the same. But the difference is so often hidden.<\/p>\n

    There are web hosters who advertise with cores and dedicated resources, but then all this only runs on very weak hardware. A small AMD core from a 10 year old server is not the same as a core on an Intel Platinum Xeon of the latest version.<\/p>\n

    \"vmware_cluster\"<\/a>
    A VMWare Cluster Example<\/figcaption><\/figure>\n

    Most providers today also virtualize their entire infrastructure. Often on strange structures like container systems where the cores booked by the customer were also booked by 20 other customers. Good and because of the software license costs expensive providers use real virtualization systems like vmware or KVM, usually called cloud.<\/p>\n

    \"kvm_cluster\"<\/a>
    A small KVM cluster<\/figcaption><\/figure>\n

    Often shared hosting is sufficient. We ourselves have built websites with thousands of visitors per month. These also run in a small hosting account, because web hosting machines are usually already very large dimensioned by the provider, so that they can serve hundreds of websites.<\/p>\n

    \"virtuozzo_cluster\"<\/a>
    View of a Virtuozzo 7 node<\/figcaption><\/figure>\n

    However, most websites will not need the power they have booked, so there is always plenty of power left.<\/p>\n

    When choosing a webhoster, simply look for a test account and upload your website there without obligation. You can usually reach it via a subdomain and test the speed. If it's nothing, just switch to another provider.<\/p>\n

    In this example the demo page is located on a SEO server<\/a> the webhoster.de AG where you get a Plesk Reseller Account with 10 IP addresses for your projects.<\/p>\n

    The hardware used is a Dell R740 server with MLC server SSDs as raid array.<\/p>\n

    The administration interface is Plesk Onyx<\/a> in the current version.<\/p>\n

    A standard WordPress with the following active plugins has been installed:<\/p>\n