Communication done by QA Heatmap Analytics

There are three main types of communication that QA Heatmap Analytics performs: communication with site readers (visitors) side, communication with administrators side and the administration screen, and communication during license authentication. Below is an explanation of each.

Communication with site readers (viewers) side

When a reader accesses a site with QA Heatmap Analytics installed, the JavaScript in QA Heatmap Analytics runs in the reader’s browser and does the standard WordPress Ajax communication asynchronously every few seconds.

The data sent from the reader browser through Ajax communication includes scroll position and clicked DOM data. The content is mainly text, often only a few tens or hundreds of bytes in size, and does not occupy or burden the communication bandwidth.

Communication with the administrator side and the admin screen

– Overview of the process in the administration screen

In the administration screen, to display the site access status and heatmap, QA Heatmap Analytics mainly accesses the data stored in the database and processes it for visualization such as graphs.

If this processing volume is too large, it may overload the database, so QA Heatmap Analytics creates a cache file for frequently used functions.

– About Communications

The data required for drawing, which is loaded from the cache file, is sent from the server to the administrator’s browser, and the drawing process is mainly performed by the JavaScript in the administrator’s browser.

Therefore, there is no load on the server for general processing. Still the larger the data volume, the more communication with the administrator’s browser, so it may take longer to display. However, during this time, the server database is not accessed unless complex data display processing is performed, so you can browse at any time.

Communication during license authentication

When a QA license is activated for QA Heatmap Analytics, it is set to be authenticated once a day, at a specific time for each server. If you are using the plugin without activating a license, there will be no this communication at all.

The communication that takes place during license authentication is mainly text data exchange, which is small in size, only a few kilobytes, and takes place once a day, so it would not be a particular problem.

Was this article helpful?