Perfume.JS is a tiny, web performance monitoring library that reports field data back to your favorite analytics tool. 

Perfume.JS WebSite: https://zizzamia.github.io/perfume/

Perfume.JS Github: https://github.com/zizzamia/perfume.js

OutSystems App - PerfumeJS Client Probe: https://www.outsystems.com/forge/component-overview/20208/perfume-js-client-probe-o11 (This component)

OutSystems App - PerfumeJS Mobile Probe: https://www.outsystems.com/forge/component-overview/20210/perfumejs-mobile-probe-o11

OutSystems App - PerfumeJS Customizations: https://www.outsystems.com/forge/component-overview/20209/perfumejs-customizations-o11

OutSystems App - PerfumeJS Backoffice: https://www.outsystems.com/forge/component-overview/20211/perfumejs-backoffice-o11

This component, is an OutSystems implementation of Perfume.JS to allow information to be sent to a server in case of errors or timeouts.

You can either use it to send information for your analystics tool of choice, or to the Perfume.JS Backoffice OutSsystem app app.

Here is an overview on how it can be used: 

The component is highly customizable, it will be extended in the future and more information will be shared as well.

The metrics available are: 

• Navigation Timing
• Navigator Interface
• Resource Timing
• Service Worker Status
• StorageManager interface
• First Paint (FP)
• First Contentful Paint (FCP)
• Largest Contentful Paint (LCP)
• First Input Delay (FID)
• Cumulative Layout Shift (CLS)
• Total Blocking Time (TBT)
• Navigation Total Blocking Time (NTBT)
• Element Timing

For more info check the site: https://zizzamia.github.io/perfume/

Note: Ideally the probe should be used for troubleshooting purposes and not as a analytics tool.
If you want to stream the information to an analytics tool you can override the probe behaviour.

The component is highly customizable, it will be extended in the future and more information will be shared as well.