There was a time when 1und1 had an extremely bad reputation. This was mainly due to a hard memory limit, which repeatedly caused problems, since systems such as WordPress in particular required more and more memory. PHP, WordPress and all the plugins including translations were loaded into memory so that not much memory was left. The end was often uncreated thumbnails. Thankfully, those times are over. But the configuration is still not quite perfect.
But before I get straight to my complaints. I think 1und1 or IONOS, as the company is now called, has made a great development. At the WordCamp Hamburg we were still discussing whether we as organizers can really accept 1und1 as a sponsor given the bad reputation in the community. But the points of criticism were accepted and the server technology was outdated. In the meantime, the servers are generously equipped with memory and GZip is now also standard.
This is an excellent example of the advantages an investment in the WordPress community, especially WordCamps, can have. The return on investment is not necessarily monetary. The employees get direct, honest feedback from the end users of the product and the multipliers (developers, designers, etc.). Despite all the justified criticism of the past, I think they did an excellent job with this conversion. The decision to issue the inclusive certificate as a wildcard certificate was also a very customer-friendly strategy. But now to my criticism:
Especially after Matthias Kittsteiner’s article on the Epiphyt blog about the problem of deleted metadata, Imagick is preferable to GD image library. A warning is given in Site Health if the preferred Imagick module is missing:
If the warnings bother you, they can be deactivated, or the module must be installed later. I described how to do this in an article about PDF preview images. The hoster there is domainfactory, but it seems to work identically with Ionos. The only disadvantage is that the specification has to be adjusted every time you change the PHP version. It would be very nice if this could be done right in the backend along with some of the most important PHP settings.
Imagick is qualitatively better, supports WebP from version 7 onwards, in contrast to the GD library, in the best case it receives the meta data (depending on whether the other libraries are also up to date) and can also create preview images from PDFs.
My second point of criticism is only sometimes encountered. Ionos was using MySQL 5.5 and then immediately switched to MySQL 5.7. At least my customers use either 5.5 or 5.7.
Unfortunately, WordPress warns of an outdated version for MySQL smaller than 5.6:
However, there is no way to update a database with just one click. The database must therefore be completely exported and then imported in a newly created version (then in version 5.7 or even more recent). Of course, the access data will then also change. Quite a lot of effort for a mostly barely visible benefit. The warning goes away, okay, but the speed gains are probably barely noticeable. Especially when caching is used. In the course of version maintenance, it would still be cool to have such a simple upgrade path.
Let’s come to point 3 and thus to the last point on my list. Let’s face it, Ionos is still a bulk hoster. A lot of customers are on these hosters and therefore the resources have to be limited somehow. Ionos has accommodated customers in many other areas, but one value still annoys me from time to time: the upload limit.
By default, a file can only be 64MB in size. That’s enough for 99% of all media (images, PDFs, documents, etc.), but the limit is reached with self-hosted videos. Unfortunately, I have run into this limit several times. Thanks to Add from Server by core developer Dion Hulse, I was able to easily work around the problem, but the value could probably be increased. Unfortunately, the limit to which the whole thing can be increased is not very easy to find. In the article linked above, 128MB is used as an example. But I could not find whether this is the maximum and whether this applies to every tariff…
All three points are not really bad problems. Colleagues used to say that extra fees would have to be added to 1und1. Those times are over for me. I can work well with 1und1. If you don’t ignore the warning emails about Extended Support, you can conveniently set (almost) everything you need at a fair price in a backend that has now been modernized.
I only have one other point of criticism, but it has nothing to do with the server configuration and is therefore behind a different door… 😉
This article is part of the series: Hosting Advent Calendar
You can find all articles via the keyword advent calendar