In this answer will be analyzed the impact of the SEO tools included in Interlinks Manager on the performance of the website.
Automatic Internal Links
The automatic internal links defined in the Interlinks -> AIL menu are applied on the front-end with the add_filter() WordPress function after the post is retrieved from the database and before the post is printed to the screen.
Regular expressions implemented with PHP are used to find in the post occurrences of the defined AIL. When a post is displayed in the front-end the amount of server CPU resources spent to apply the automatic internal links depends on the following factors:
- The overall number of AIL defined in the Interlinks -> AIL menu
- The length and complexity of the HTML of the post
What you should expect
In general (the actual performance also depends on the specification of the server), with a limited number of AIL defined in the Interlinks -> AIL menu (less than 500) you will not experience an increase in the time required to load the page and the additional load on the server CPU will also be negligible.
If your website has a high number of visits or if you have defined a high number of AIL we recommend the use of a caching plugin (for example WP Super Cache). In this way, you prevent the process used to apply the automatic internal links to be repeated each time a post is requested.
Internal Links Tracking
The clicks on the automatic and manual internal links are tracked with POST requests sent to the server when the links are clicked.
This is an optional feature and if you decide to disable this aspect of the plugin to limit the number of requests sent to the server you can do this by setting to “No” the Track Internal Links option available in the Tracking tab of the plugin options.
The analysis performed in the back-end to provide you statistics on the internal links, information about the distribution of the link juice, internal links suggestions, etc. are performed when the user actually requests these statistics and there are no background activities performed by the plugin. For this reason, the statistics generated in the back-end have no effect on the server load.
More information on this subject is available in this FAQ.