Anna
(@annareinventwp)
Hi Craig,
Thanks for checking. In normal use, the plugin should add very little server load to WordPress page views. It mainly outputs the player on the frontend and stores its main settings in WordPress options. The heavier work (generating audio) only happens when audio is requested/generated, not on every page load for every visitor. So at roughly 500,000 page views/month, the impact should still be modest unless the site is also actively generating a lot of new audio or using extra features like podcast/background processing.
On the database side, it does not create custom database tables. From the plugin source, the main settings are stored in the natuteto_settings option, and analytics can also create option records such as natuteto_analytics_button, natuteto_analytics_insight, and natuteto_analytics_api when those features are used. So you are mainly looking at a small number of wp_options entries rather than additional tables.
And yes — natuteto_analytics_button is from this plugin.
If you want, I can also help you identify which of these options are autoloaded and which plugin settings would minimize runtime/storage overhead on your site.
Best regards