pierre-lannoy/wp-vibes

Truthful user experience and browsing performances monitoring.

wp-vibes's Issues

Do not collect information for backend

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

Show number of samples per endpoint

Describe the solution you'd like

I have an issue where some pages on my site that are not super popular are visited by some bot once in a while that has a very slow client side. this gives e.g. FCP in the thousands of seconds. And, it confuses me looking at the results page.

I think having a column on the reports page showing the # of samples that contribute to the number would help. And a filter that would allow hiding rows with less than some number of samples.

It is not clear to me what e.g. the FCP column refers to. Is it the average of the samples? the 75%ile? the median?

I would like to not see results that don't have some confidence to them.

I think also some method to remove or ignore outliers would be useful.

Example:

MySQL [www_database]> select timestamp,country,class,FCP_SUM from wp_vibes_statistics where endpoint = '/angular-content-security-policy-google-tagmanager/';
+------------+---------+---------+---------+
| timestamp  | country | class   | FCP_SUM |
+------------+---------+---------+---------+
| 2023-08-06 | NZ      | desktop |       0 |
| 2023-08-07 | US      | desktop |    6560 |
| 2023-08-07 | UA      | desktop |       0 |
| 2023-08-07 | DE      | desktop |    2878 |
| 2023-08-07 | FR      | desktop |       0 |
| 2023-08-07 | FI      | desktop |     825 |
| 2023-08-07 | DE      | mobile  |    2764 |
| 2023-08-07 | EE      | desktop |     983 |
| 2023-08-07 | IN      | mobile  | 9251220 |
| 2023-08-07 | PE      | desktop |    1471 |
+------------+---------+---------+---------+

Add INP data collection

Is your feature request related to a problem? Please describe.
INP will be officially accounted for starting in March 2024.
Preparations have already begun for site owners to deal with it, so it makes sense to enable collecting that metric before the official deadline.

Describe the solution you'd like
Add INP. What would make sense is to also collect clicks target elements too to give a hint of what to investigate to help fix/improve INP.
Make collecting FID optional and decrease it starting from March 2024.

Describe alternatives you've considered
N/A

Additional context
N/A