Do not collect information for backend

[donbowman]

Describe the solution you'd like

I do not find the backend information useful, and it consumes resources to collect it. IMHO this plugin is oriented at the problem of the average end user consuming the site.

Having an option to disable collection for logged in users, or in the backend, would be much better.

I am aware there is a filter button in the reports, but its off by default, no way to save it

the distribution of performance of backend vs frontend is dramatic, so blending them together doesn't really make an accurate view.

Describe alternatives you've considered

considering adding a dequeue in functions.php

[DahmaniAdame]

I totally agree. There shouldn't be any data collection on the backend.
And collecting data for logged-in users should be disabled by default and have a filter to enable it back if ended.

[Pierre-Lannoy]

Hello to both of you!
Thanks for the suggestion. From my standpoint, doing what you propose @DahmaniAdame is to completely obliterate the UX for all sites where a lot of editors are active - and I have examples where editing is a big part of the UX.
Nevertheless, I understand your concerns. Let me think about what can be done to have "default" values (i.e. backend disabled) for "common" sites.