Heatmap not properly working with more page views

Hello.
I checked here, and the URL top page in the first image does not load the CSS output by Aurora Heatmap.
plugins/aurora-heatmap/style.css
Therefore, the display is broken as shown in the second image.
On the other hand, some pages seem to be loading the CSS normally.
In this situation, some pages will be able to display the heat map and some will not, but I don’t think the cause is the PV count.

Perhaps the minify process or cache settings are controlling the scripts and CSS output to the header differently depending on the type of page.

Hhm it’s crazy. The thing is that only pages with a specific number of PV might have these problems. My Aurora list tells me that it found more than 1000 different entries/pages. All with a lower PV count >1000 loads well – mobile and desktop view. Only pages with more than (in my current case), 1700 PV has this issue (currently 2 pages (but important once)).

For caching: We use WPRocket as main caching plugin.

Thanks for the replies.
As you can see in the image, the heatmap itself is rendered in the “ofckTdC_d.webp” file you provided.
However, it is not displaying properly because the CSS I mentioned earlier has not been applied.
One of the pages that cannot be displayed is the top of the domain, right?
What is the URL of the other page in question?
In addition, please show us the pages where the heatmap is displayed correctly.
I’ll compare and check it here.

You don’t seem to have replied, but I’ll add a few things for you and anyone else who sees this topic.
Aurora Heatmap is one of the few heatmap tools that is completely native to WordPress, without the use of any external infrastructure.
We saw a lot of merit in this approach, but at the same time we were concerned about the following in cases of high traffic
Wouldn’t it affect the general user’s browsing of the site?
Can we draw a heat map even if the data to be recorded is huge?

Especially in the latter case, during the actual development stage, there were cases where the heat map rendering caused 503 errors when the number of accesses was extremely high.
Of course, this is also due to the capabilities of your hosting service.
In Aurora Heatmap, we have tried to make the heatmap work well under various conditions, and one of them is to adjust the number of plots when drawing the heatmap.

Aurora Heatmap – Settings – Number of drawing points in Display settings

This makes it possible to operate a site with a considerable access scale.
Now, as for this issue, it probably doesn’t make sense to reduce the drawing data.
That’s because the drawing is done without error.
However, the display is not correct.
And on your site, some pages are loading the CSS required for the Aurora Heatmap and some are not.
Therefore, you need to check if this is the reason why the rendering is not proper.

Basically, CSS loading is controlled by the theme or a cache plugin.
In this case, it’s probably WPRocket.
If possible, temporarily deactivate it so that the CSS will load properly.

I’d be happy to help you.

• This reply was modified 3 years, 5 months ago by r3098.

Hello @r3098

I had quite a few other things to do last week. The CSS I have not yet tested, but will do so in the next few days.

I just find it very strange that it does not work on pages with increased traffic (that css not loaded). We also use a plugin to block scripts and CSS files for certain pages. The heatmap (Aurora) has not been excluded here (e.g. Mainpage phi24.de/ ).

Since I haven’t heard back from you in a while, I will mark this as resolved.
If you have further questions, please create a new thread.
We’re always happy to help.