• Resolved jlfunder

    (@jlfunder)


    I installed the most recent version of the slimstat plugin and saw a large increase in page load times. From about 1s to over 3s. After some trial and error, I’ve figured out it occurs when I have the Autoptimize plugin by Frank Goossens and Slimstat activated at the same time. I’m obviously not sure who’s fault it is, but I wonder if you have an idea what could cause this?

    https://www.ads-software.com/plugins/wp-slimstat/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi jlfunder;
    A couple of quick questions that should help us (Camu as Slimstat dev & me doing AO) to better understand what’s happening;
    1. is it the base HTML (the initial request) that is slower, or one (or more) resources loaded later (ajax-admin.php for example)?
    2. are you running a page caching plugin alongside AO (e.g. hypercache or wp super cache)?
    3. did you configure slimstat to track using javascript?
    4. did you do any specific configuration for slimstat in autoptimize (exclude JS from optimization)?

    kind regards,
    frank

    Thread Starter jlfunder

    (@jlfunder)

    1. I’m not an expert here, but it seems like the initial request increases by almost 2s. It just seems to pause and do nothing.

    2. Used to, but I’ve disabled all plugins except Slimstat and Autoptimize.

    3. No, I’m using Server-side.

    4. No. I did find that it’s specifically the “Optimize JavaScript Code” option in Autoptimize that causes the problem.

    best regards

    In that case I’m afraid it’s AO that is slowing things down; without a page caching plugin AO can indeed slow things down, as it will have to extract and combine CSS & JS for each page request and if the resulting string has not been minified yet, also do the minification. I would advise you to (re-)enable a page caching plugin and switch to JS-based slimstat-tracking. If you have JS optimization active, you’ll have to add “SlimStatParams” to the comma-seperated JS-optimization exclusion list.

    @camu; if using server-side, is there any JS in the HTML?

    frank

    Plugin Author Jason Crouse

    (@coolmann)

    Hi both,

    when in server-side tracking, you will need to set Spy Mode to “NO”, if you don’t want to have any javascript added to the source code of the page. This way the tracker will not collect any information about the visitor’s screen size, browser plugins installed and other client-side data (which clearly cannot be detected using PHP).

    Best,
    Camu

    Plugin Author Jason Crouse

    (@coolmann)

    Marking as resolved.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘WP Slimstat Autoptimize causes large increase in page load times’ is closed to new replies.