Some manage to optimize their own website with a CMS system, but I doubt that they are not developers in these cases. Optimizing a system is a long and difficult task because CMS systems are not designed but kept lean.
What does slim mean? By slim is meant that as little as possible in the basic equipment is included. So that you eventually need a plugin / extension (however, that CMS has named it now). Better said from the beginning, as some CMS systems do not even bring the most necessary settings. One reason is to allow other developers to participate in the project somehow, even if not in the core itself. The other is that the developers have a way to offer and sell their own products, be it with features or complete packages.
How do I get more performance?
There are many ways and it depends on your system, which you use. Most things about performance that are prevalent on the internet are unassigned and so it is not tangible. It may work but you should try to understand what you really need and for that you have to examine your system only if you do not know it. Perform analysis to find out where you have performance losses just so you can really do something effectively for your performance. Here in the blog find very useful and helpful tips and tricks.
What are features?
Features are e.g. You use a plugin and the plugin brings the basics for your project. After a while, if your website needs more than just the basics, then these features are available at a cost. This could be e.g. a redirect help, which you then have to pay at the end (developers should now smile).
To get the best performance out there, you need a system that works with their components to work together smoothly. This means that the basic equipment must already be available so that the performance is maintained. When developing, care must be taken to see which functions are faster and it needs to be re-optimized if necessary. The spelling of code accelerates or slows down your website, this saying is just right: Many cooks spoil the pulp (applies only without structuring). Most people think that with a cache plugin you have everything under control and that your website is running fast, but most websites are full of console errors, as the cache unfortunately does not fix bugs :)
CMS systems and performance losses
And today it is with most CMS systems so that they are strongly influenced by themes, plugins, extensions or the like, as far as the performance is concerned. If you have not already done so, take a closer look at your website and you'll soon realize that it's a long way from performance. No matter how much money you spent on it;)
Of course you could think so now I'll take a CMS and put it clean, but it's hard to know without a developer or even know with developers to choose the right plugins. And if you take a plugin, which has a lot of good reviews, it still does not give you a 100% guarantee personally. You still run the risk of destroying your site or even using a plugin, which no developer has developed and may cause damage in the long term.
Because a bug is not just a bug but part of something bigger.
- Mr. Robot
Of course everything can go very well and you will not have any problems, as well as technically or superficially.
tnado performance clearly noticeable
Long talk short, just test this website yourself
tnado has been set up to become one of the fastest CMS systems from the very beginning, so it has been continuously tuned for performance. All basics are inclusive and open source. Designed for SEO and equipped with responsive templates. With not enough, special AMP engine, all features should give the user the opportunity to join in the lead. Everything we complained about was developed and optimized in tnado.