Hosting variants
Root server (fully rentable server):
Advantage: Absolute control (Oversized for most WordPress scenarios)
V-Server(A simulated server on a root server):
Disadvantage: The machine on which the V server is installed divides its resources to all installed V servers. If an application on the server is computationally intensive, it has a negative effect on the adjacent applications.
Shared webspace (like the V server, but with even less control):
Disadvantage: With shared hosting is above all the circumstance that runs on an IP address domains. A test on the page "https://www.backlinks.com/ip_checker.php" showed for my IP "81.19.145.28" the 772 domains ran on it
To perform the test yourself, first click on "https://ipinfo.info/html/ip_checker.php" to determine the IP of the website. Then switch to "https://www.backlinks.com/ip_checker.php" with this IP to perform the test.
What, of course, the capacity is ongoing. Speed optimization is then only effective.
The best solution would be a root server, but too c
omplicated To simplify it you could use a "managed root server". Which is serviced by a technician. But that's very expensive.
The best affordable approach would be a "V-server". You still share resources, but not so many (10-20 others). Cost about 10-20€.
Pictures
Large images create emotions.
But also charge more slowly.
One approach would be to reduce images before uploading them. Sites such as "https://tinypng.com" create a reduction of up to -70%.
For many images in WordPress, the plugin "Smushit" would be recommended. The plugin does not compress as well as "tinypng".
Plugins
Speed tip: Install as few plugins as possible and solve via custom code if possible. There is also the possibility to activate plugins only for a short function and then deactivate them again if they are not needed.
Mimify
Empty spaces ensure that the "line cursor" rises. So the browser needs to jump more open than needed lines. Online services for "mimifying" would be "https://www.cleancss.com"
However, a solution via a plugin is better, because after an update all CSS + JS files would have to be "mimified" again by hand.
Browser caching
Browser caching can be activated manually in ".htaccess"
<IfModule mod_expires.c=""></IfModule> ExpiresActive On ExpiresByType image/jpg "access 1 week" ExpiresByType image/word------------------------------- ExpiresByType image/gif "access 1 week" ExpiresByType text/css "access 1 week"
Gzip + Deflate
These modules are used for server-side compression of all files (incl. php)
Activation takes place in ".htaccess"
<IfModule mod_gzip.c=""></IfModule> mod_gzip_on Yes mod_gzip_dechunk Yes mod_gzip_item_include file . (html?| txt|css|js|php|pl) mod_gzip_item_include handler scgi-script mod_gzip_item_include mine. * mod_gzip_item_include mine.*
Activation of deflate in ".htaccess"
<IfModule mod_deflate.c=""></IfModule> AddOutputFilterByType DEFLATE text/plain AddOutputFilterByType DEFLATE text/html AddOutputFilterByType DEFLATE text/xml AddOutputFilterByType DEFLATE text/css AddOutputFilterByType DEFLATE application/xml AddOutputFilterByType DEFLATE application/xhtml+xml AddOutputFilterByType DEFLATE application/rss+xml AddOutputFilterByType DEFLATE application/javascript AddOutputFilterByType DEFLATE application/x-javascript
Clean up database
Database corpses are created by plugin installations and uninstallations. Also through revisions of Post's. Plugin Solution : "WP Clean up"
After this overview, take a look at two versions of the same content with and without optimization measures 🙂