Caching options depend partly on your hosting environment
Caching offers several controls across hosting environments, but its dynamic and object-caching options are SiteGround-specific.
File-based caching stores static HTML, while dynamic caching and Memcached are available only on SiteGround servers. Cache purging can happen automatically or manually, and browser-specific caching can be enabled.
You can exclude post types or specific URLs, including URL patterns for subpages, and check whether dynamic caching is active for a URL. For sites hosted elsewhere, the file-based option and purge controls remain the relevant tools.
Frontend controls for CSS, JavaScript and fonts
Frontend settings let site owners reduce asset size and adjust how selected resources load.
- CSS: Minify stylesheets, enable or disable CSS combination, preload combined CSS, and exclude styles from minification or combination.
- JavaScript: Minify scripts, defer render-blocking JavaScript, and exclude selected scripts from optimization.
- Fonts: Add a preconnect for Google Fonts and preload locally hosted fonts, helping browsers establish connections and load font files earlier.
These switches offer control over individual asset groups, so sites with unusual scripts or styles can use exclusions where broad optimization may not fit.
Image compression and lazy loading
Image compression and lazy loading extend the plugin’s optimization beyond caching and code changes.
- Image compression: The plugin describes compression of up to 85% without sacrificing quality; treat that as a stated maximum, not a guaranteed result for every image.
- Lazy loading: Listed as a media optimization, it can defer image loading until needed, which may help pages with many images.
Database, HTTPS and Heartbeat controls
Environment settings cover connection security, database upkeep and WordPress background activity.
- HTTPS enforcement: Enable HTTPS for the site to support secure browsing.
- Scheduled database maintenance: Remove unnecessary database items and optimize tables on a schedule. With InnoDB, table optimization is handled by the storage engine itself.
- Heartbeat control: Change the WordPress Heartbeat API frequency in different site areas or disable it. This gives administrators a way to adjust resource use, though disabling it removes the API’s periodic checks.
A broadly adopted plugin with some hosting-specific features
Speed Optimizer pairs broad adoption with a meaningful hosting caveat: its dynamic and Memcached caching features require SiteGround servers.
The plugin is among the directory’s most widely installed, and its rating is good across many reviews. Support data shows 60% of 10 threads resolved, a useful but small sample when judging how consistently support issues are addressed. The plugin was updated recently, so it appears to be maintained; sites on other hosts should weigh the available file-based caching and frontend tools against the server-specific options.
