Too invasive and slows down homepage significantly

The plugin has some nice features but there is a major flaw:

Although we deactivated the standard TOC completly and only activated the sticky TOC and also only for posts, the functions seem still to run on our homepage. I deeply tested it. When sticky TOC is activated (only for posts), our hompage loading time piles up from 1s to 2,8s which is an insane increase. I tested multiple times. I also deactivated the plugin completely and the results are the same.

The plugin adds then the class “ez-toc-section” to every header like h1, h2, etc. It seems it is duplicating the whole page before it is thrown out, that′s while page load almost triples. I asked the support, even send a video, but it seems the support has no technical knowledge, so you kind of walk in circles with them without a result.

For me personally this invasive behavior is too much. Sticky TOC shouldn′t run on homepage or other pages when it′s deactivated. And I mean really shouldn′t run the functions, not only hiding elements via CSS if that′s the case.

A better solution would be they would wrap their functions and run them only on desired posts, pages, etc. for example with:

function my_custom_function_for_single_posts() {
    if (is_single()) {
        // Your function or code to run only on post pages
    }
}
add_action('wp_head', 'my_custom_function_for_single_posts');

But I′m not completly sure were their problem really comes from. Perhaps they will fix it in future. For everyone until now I recommend test you page loading times, with and without activated plugin, to be sure that your site won′t be affected badly.

Regards

—

Edit: They tried to fix the issue and had full access to my installation but couldn′t manage it. The problem is still there. The plugin is too invasive and will slow down your pages. I found out that the “sticky toc class” is added on almost every page throughout your installation and page speed is influenced very badly. I cannot recommend this plugin. The problem seems to lay in how the plugin works. I think there′s a function that crawls the sites and then throws out a new DOM where it adds classes to the h tags. And it does it regardless where u want it to run only. Therefore it doesn′t matter if you set it to “blog” only. It will do it either way and double or tripple your loading times for almost every page. Better search for something more lightweight for now. No need to slow down your site just for a table of contents. I assume that most people that don′t have the technical knowledge for this don′t realize this problem at all.

• This topic was modified 3 months, 2 weeks ago by Artan. Reason: edit because after review problem still exist