@nemish seems like you have visible content tracking enabled. Can you maybe share a link to the page? How many content blocks do you have on your page approx?

By default, Matomo checks for newly visible nodes on scroll, and every 750ms where the every 750ms can be customized and set to eg every 0ms (won't do it anymore) as on "scroll" should actually do the job. Possibly we should change the default value there to 0ms.

Additionally, we could set a property that caches that a node has been visible at some point. I think a simple solution may be even just something like this:

diff --git a/js/piwik.js b/js/piwik.js
index c2adab6363..24b44d0a34 100644
--- a/js/piwik.js
+++ b/js/piwik.js
@@ -1,5 +1,5 @@
 /*!
- * Piwik - free/libre analytics platform
+ * Matomo - free/libre analytics platform
  *
  * JavaScript tracking client
  *
@@ -2671,9 +2671,13 @@ if (typeof window.Piwik !== 'object') {
             },
             isNodeVisible: function (node)
             {
+                if (node && 'hasBeenVisible' in node && node.hasBeenVisible) {
+                    return true;
+                }
                 var isItVisible  = isVisible(node);
                 var isInViewport = this.isOrWasNodeInViewport(node);
-                return isItVisible && isInViewport;
+                node.hasBeenVisible = isItVisible && isInViewport;
+                return node.hasBeenVisible;
             },
             buildInteractionRequestParams: function (interaction, name, piece, target)
             {

This way the cache will also be used when a plugin calls the function and the logic is a bit simpler compared to 3.x-dev...nemish:cpu-performance-2 which does the same?

Thanks for contributing to this issue. As it has been a few months since the last activity and we believe this is likely not an issue anymore, we will now close this. If that's not the case, please do feel free to either reopen this issue or open a new one. We will gladly take a look again!