Hello, we have issues with page responsivness – loading times on page http://www.modre-novice.si. We host on highest performance LiteSpeed server. We tried to optimize page with suggested cache plugin WP Super Cache – still not good, than we optimized it with liteSpeed cache – dedicated cacheing plugin for litespeed servers and it was a bit better but still too slow for an news portal.
We asked host to check on it and these were theirs findings:
Hello,
I checked the status of the website and ran a fairly simple test to see how long the initial response time is. I noticed that the response time for the website itself is indeed as described by the client — it takes more than two seconds for the main page to load.
I reviewed the server settings to see if there was anything that could still be optimized, but it seems the configuration is fine and nothing major has been overlooked. I then started looking into the application itself, so I began disabling WordPress plugins to identify which ones have the biggest impact on performance.
First, I disabled the top half of the plugins, but there was no noticeable change. Then I re-enabled them and repeated the process for the bottom half, where it turned out that some plugins could be problematic. When I started disabling the plugins one by one, I found that the “tagDiv Cloud Library” plugin, when disabled, reduced the total page render time by half.
I continued and disabled the “tagDiv Composer” plugin as well, which significantly reduced the load time even further — down to around 320 ms.
Usually, these modules for building and designing websites generate code that, unfortunately, isn’t very optimized for loading speed, even though the end product often looks nice. When I look at the website’s source code, the first thing I notice is that the <head> section is quite large and contains a huge amount of data.
The <head> tag stretches all the way to line 353 in the source code, and there’s a lot going on in that part of the code. This affects how quickly the browser can start loading the content from the <body> section. If there’s too much “bloat” in the <head> area, the browser has to process all of that before it can begin rendering any content.
My suggestion would be to review this page builder and consider replacing it with something else that would ultimately produce better performance.
If you decide to move to a VPS server, it will definitely be able to handle more of these “slow” requests compared to shared hosting. In addition, once the server is actually under load, we can recheck some parameters, and if the page still doesn’t load as expected (in this case, around 2.5 seconds is a typical result for an uncached single request), we can then increase certain limits on the server to achieve higher throughput.
________________________
What is the solution here?
My layman’s question is whether the website still works and looks the same when those two plugins are disabled? Namely, the news or posts are generated in the classic way under “Posts” without using these specific plugins. I’m wondering if they can remain disabled and only be turned on when needed — for example, when editing content on individual pages (and not on posts).
As for the tagDiv Cloud Library, it seems that this plugin provides the layouts for the posts themselves, the archive page, category pages, etc. Does the website’s visual structure break if this plugin is disabled?
Hello,
The situation is as follows, when you deactivated the tagDiv Composer and tagDiv Cloud library plugins on the site, you only had shortcodes displayed, that is, text, as a result, the delivery time becomes very fast because only one query is made to the database that brings only text to that page, this is simple, easy and fast to interpret, while when these plugins are active and blocks are used that display articles, ctegories, menus, cpts…, images, texts, background images, different functionalities … it is normal for the duration to be a little longer, but if the site is well optimized it should be under 2 seconds.
Thank you!
