WordPress plugin
Leverage Browser Caching Pro for WordPress Performance
When a visitor returns to a site, their browser can reuse cached documents instead of fetching them again. Leverage Browser Caching Pro delivers settings for managing browser cache durations and other WordPress performance tasks from an admin page.
When a visitor returns to a site, their browser can reuse cached documents instead of fetching them again. Leverage Browser Caching Pro delivers settings for managing browser cache durations and other WordPress performance tasks from an admin page.
Choose how long supported pictures, web fonts, stylesheets, scripts, documents, data, and other files remain in a visitor’s browser cache. The caching settings also include GZIP compression, Cache-Control headers, Keep-Alive, and ETag removal. Performance testing services such as Google PageSpeed Insights, GTmetrix, Pingdom Website Speed Test, WebPageTest, and YSlow can help you review recommendations.
Code, media, and font settings
- Minify CSS, JavaScript, and HTML.
- Delay JavaScript loading.
- Lazy load images and iFrames.
- Optimize Google Fonts.
These controls address how front-end code and media load alongside the browser’s handling of cached files.
Database and WordPress tools
Pro also includes database cleanup, DNS prefetch, preload links, Heartbeat Control, and XML-RPC Disable. WooCommerce optimization is included for stores that need performance settings alongside their product and checkout content.
Manage settings and review performance
The base plugin applies browser caching automatically. The Pro edition adds a settings admin page where you can manage its available capabilities. The Pro offer also includes premium support and updates.
- Install Leverage Browser Caching Pro in WordPress.
- Activate the extension.
- Open its settings admin page.
- Choose the caching, compression, code, media, database, and site options that suit your website.
- Review performance with your preferred testing service.
Browser caching requires an Apache web server with the mod_expires module enabled and a writable .htaccess file in the WordPress root directory. This functionality does not work on Nginx or IIS servers.

