Before we start with the speed up of WP, we will show you how to measure the speed of loading the first byte of web or TTFB (time to first byte) + page response time. This happent at the clienta��s end after the request is processed at your server and the first content is sent. Thata��s the reason why this value is so important without the actual web content.
We useA�three ways how to measure TTFB + page response time
% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 1270 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 HTTP/1.1 200 OK real 0m0.270s user 0m0.031s sys 0m0.011s
3) Using the developer tools in your browser
With these three options you can measure the speed of your WP website anytime during the speed optimization.
1. Choose the good web hosting provider or build your own simple server infrastructure
Definitely dona��t choose the cheap hosting. Those hostings are usually overexposed and use the older infrastructures. So rather try to build up your own infrastructure.
Or we recommend to use the hosting optimized for WordPress:
2. DB Optimizing and caching
Optimization of the database is another key element in speeding up the website. For example backup of all article revisions may fill up the thousands of rows in the database and slow it down. We recommend to use the free wp-optimize plugin to optimize the database.
a�� and the next most important step is to turn on the caching. Page cache module can speed up your page response timeA�more than 200%. We recommend this free plugin:
3. Using a CDN
Use of CDN will not even shorten the load time of your website for all countries but will protect the server against the DDoS attacks, minify your CSS, JS, HTML files and save you up to 60% of your traffic. Ideally use it together in combination with caching plugin w3 total cache. This plugin can also connect the MaxCDN service with your WordPress back-end
We recommend these worldwide largest CDN services:
Below is the screenshot from our measurement of one our project using the pingdom service. Time to first response of the page was 1400ms a went down to 350ms.