QA Analytics communicates mainly in three ways: with site readers (visitors), with administrators on the administration screen, and with license authentication.
Communication with site readers (viewers) side
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
On the admin screen, QA Analytics primarily accesses data stored in the DB to display site access status and heatmaps, which are then processed for graphs and other visualizations.
Since this large processing volume may overload the DB, QA Analytics responds by creating cache files for frequently used functions.
– About Communications
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
For users of the licensed version of QA Analytics, license activation is performed once a day, at a fixed time for each server. If you are using the free version, there will be no communication associated with the activation.
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.