Tuning the Plugin Settings
The code for WPSSO Core is highly optimized — it doesn’t use a bloated framework, doesn’t load or execute modules that aren’t required, and WPSSO Core makes full use of all WordPress caching techniques. As-is, WPSSO Core is very fast and light, but you can fine-tune some options to gain a few milliseconds here and there.
- If you’ve saved a few posts and pages without any duplicate meta tag warnings, you can disable the “Check for Duplicate Meta Tags” option under the SSO > Advanced > Integration tab. This will prevent WPSSO Core from fetching the front-end webpage when editing posts and pages.
- If your website content does not use any embedded videos, or if you prefer not to include embedded videos in your Open Graph and Twitter Card meta tags, set the “Maximum Number of Videos” to “0” under the SSO > General > Videos tab. This will prevent WPSSO Core from searching your content for embedded videos.
- If you want to limit which video service APIs are supported, review the “Check for Embedded Media” options under the SSO > Advanced > Content and Filters tab.
- If you generally select a featured image for your posts and pages, you may set the “Maximum Images to Include” to “1” (the default value) under the SSO > General > Images tab. This will prevent the plugin from searching your content for additional images (the featured image counts as “1” and the plugin will stop there).
- If no excerpt / summary text is available, the content text will be used to create the Open Graph description value. If your content does not rely on shortcodes or plugins to render its text, you may uncheck the “Use WordPress Content Filters” option under the SSO > Advanced > Content and Filters tab.
- You can increase the “Head Markup Array Cache Expiry” option under the SSO > Advanced > Cache tab from the default of 604800 seconds (1 week). WPSSO Core removes outdated cache objects when posts / pages are updated, so increasing the default value should not create any issues.
If you have not installed an opcode and/or transient object cache, you really should. There are many great articles on optimizing WordPress, which cover the subject of opcode and object caching. Please take the time to research opcode and transient object caching solutions – they will make a big difference to your website’s performance and maximum concurrent user capacity.
The MySQLTuner script by Major Hayden from http://mysqltuner.com/ is also excellent for general database tuning.
Full-Page Caching (Plugins or Services)
WPSSO Core allows you to customize a few Open Graph meta tag and Schema markup values specifically for the Pinterest crawler. If you use a caching plugin (or front-end caching service), it should detect the Pinterest user-agent and bypass its cache (for example, look for a “User-Agent Exclusion Pattern” setting and add “Pinterest” to that list). In order to provide the most up-to-date information for social and search crawlers, you may also consider adding the following user-agents to your caching plugin / service exclusion list:
Defragment the Database
The database tables in MySQL can become fragmented as entries are added/removed/updated, especially the options table which holds the transient cache entries. You should defragment you database tables at least daily. I use Phil Dufault’s
mysqlfragfinder.sh script for my own databases.
Here is an example crontab entry:
# defragment mysql tables
0 3 * * * export TERM=vt100; /usr/local/bin/mysqlfragfinder.sh >/var/tmp/mysqlfragfinder.log
And to prevent the script from stopping for a password, add an entry for it in the