Hi Romeoo ??
Cheers!
Foreword
I tested the performance yesterday, again, and on a populated WordPress installation, TSF v3.1.1 adds 3.5ms of load time using PHP 7.2.
Roughly half of this time (~2ms) is shown in the plugin identifier in your page’s source. This identifier shows the meta-generation-time. The other half is preparation-time.
The WordPress installation itself could generate pages in 36ms with only the theme “Twenty Seventeen” activated.
Take this as a guideline to determine how much this plugin should affect your website in total ??
Query alteration settings
If your site is huge (read: 10,000+ posts), the search/archive query alteration settings might have an effect. Otherwise, you shouldn’t notice a difference.
You’ll have to test the performance difference yourself. However, I recommend keeping it set to “in the database” for better pagination consistency.
Transient caching
The transient cache options, when enabled, temporarily store the output in the database. With this, the plugin won’t have to recompute and repack the metadata.
The transients are refreshed every seven days individually, or earlier when deemed necessary, like when you change your SEO settings.
When generating the sitemap, the plugin tests each and every post included for “noindex” settings. This can take a long time and it might affect your server’s performance when doing it often. So, I recommend enabling the sitemap generation cache, always.
The Schema.org output cache setting shouldn’t affect performance on up-to-date PHP installations. At most, it’ll shave 20% off from rendering time; this isn’t notable to humans.
In fact, it will cram your database full with “rendered” data, which isn’t always warranted, thus why it’s disabled by default.
I hope this gets you up to speed! (I won’t apologize for the bad pun)
