Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Hessel de Jong

    (@hesseldejong)

    Hi @hamil1,

    We are working on improving the performance of our tracking script. We are still investegating what works best. However cookieless should be almosts as fast as normal tracking. But we would like to investigate the issue.

    You don’t have cookieless turned on at the moment. Could you run the tests again with gtmetrix.com and share the reports url here? (For example: https://gtmetrix.com/reports/really-simple-plugins.com/AYvgbXFn/)

    This way we can dive a little deeper into finding the problem.

    Kind regards,
    Hessel

    Thread Starter hamil

    (@hamil1)

    Thank you for your quick response. The no cookie feature is enabled https://ibb.co/JQmkc3T
    Results on GTmetrix
    https://gtmetrix.com/reports/kurzyonline.edilo.cz/PIlBvqTM/
    https://gtmetrix.com/reports/kurzyonline.edilo.cz/OLCy6Hd1/
    The slowdown is showing up in PageSpeed Insights mobile. For desktop, the test is in the green numbers.
    I don’t have the PRO version of GTmetrix, so I can’t simulate Android.

    Plugin Author Hessel de Jong

    (@hesseldejong)

    Hi @hamil1,

    Okay, I don’t have an explanation as of now for the POST request for Burst Cookieless being slower. I should investegate more.

    But I do have a solution that will improve pagespeed for cookieless and normal tracking. The solution is tracking the hit when the page is fully loaded. At the moment we track the hit after the DOM has loaded (This is moments before the page has fully loaded).

    By tracking the hit when fully loaded your data might be a little bit less accurate because you could miss a hit of someone who left before the page has fully loaded.

    If you want to try this setup you can download a ZIP file from our Github. You can download a zip from this url: https://github.com/Really-Simple-Plugins/burst/compare/Fire-hit-after-page-load

    We are trying out the different tracking options and figuring out what works best. Both for speed performance and for data accuracy. So another option is waiting for that update.

    I hope this helped! If not don’t hesitate to reach out again ??

    Kind regards,
    Hessel

    Thread Starter hamil

    (@hamil1)

    Hi @hesseldejong,

    I’m not gonna get into the experiment. I’d rather wait for the next stable version of the plugin and then test.

    Thank you and best regards.

    Plugin Author Hessel de Jong

    (@hesseldejong)

    Hi @hamil1,

    That’s okay too. I’m not sure if the next version will already contain the improved speed. Because we still need to do some research.

    I will update this thread when we have released the improved speed version.

    Kind regards,
    Hessel

    Plugin Author Hessel de Jong

    (@hesseldejong)

    Hi @hamil1,

    We have just updated our tracking to be a lot faster. We’ve also added a Turbo mode which defers the Burst script.

    Hope this improves your pagespeed!

    Kind regards,
    Hessel

    Thread Starter hamil

    (@hamil1)

    Hi @hesseldejong,
    thank you for the message. Unfortunately, PageSpeed Insights mobile measurement does not confirm the speedup for my site.

    Plugin Author Hessel de Jong

    (@hesseldejong)

    Hi @hamil1,

    It looks like Burst could not install an endpoint on your website. The endpoint is faster, than using the REST API. I think we can’t add an endpoint because we don’t have write access in the root. You can try and follow this article: https://burst-statistics.com/troubleshoot-tracking/

    If you need help, let me know ??

    There is also a new option “Turbo mode’ which defers the script and places it in the footer. That will probably improve your pagespeed as well.

    Hope this helps!

    Kind regards,
    Hessel

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Tracking without cookies slows down the web’ is closed to new replies.