0
downloads all time
WordPress plugins
A modular WordPress plugin for website acceleration, SEO hygiene, garbage cleaning, security and convenient administration. The default interface is in Russian. Page caching, front-end optimization, premium plugin.
7-minute install
No manual file editing
+45 bonus points
Credited after payment
12 months of updates
Support and patches included
5 / 5
from 0 buyer reviews
0
downloads all time
1.0.0
current stable version
02.06
last update date
45
bonus points on purchase
Full details
Compatibility, server requirements, archive contents and license terms in one place.
Pluginhub Booster Cache
A modular WordPress plugin for website acceleration, SEO hygiene, garbage cleaning, security and convenient administration. The default interface is in Russian.
Description
The Pluginhub Booster Cache contains independent modules. Any module can be turned on or off in the settings.
1. Page caching and the `CacheManager` API
Main features:
- HTML file cache for anonymous GET requests.
- Cache TTL, lifetime in seconds.
- Manual clearing of the entire cache.
- Cleaning statistics, number of files, volume and time of the last cleaning.
- Shows the current cache size on the disk.
- Caching of the GET REST API.
- Separate mobile and desktop cache.
- Private cache for authorized users.
Cache Exceptions:
- By URL, by path prefix.
- By cookie.
- By User-Agent.
Automation:
- Scheduled cleaning of specified URLs by cron.
- Warming up the sitemap cache, including nested sitemap indexes.
- Manually start the cache warm-up.
2. Optimization of the `OptimizationManager` frontend
Load optimization:
- HTML minification.
- Defer JavaScript.
- Exceptions for Defer JS, by handle or URL fragment.
- Lazy loading iframe.
- Lazy loading of images and `decoding "async"`.
Image Optimization:
- Auto alt for images in the content, if missing.
- WebP and AVIF via `<picture>` if there are sidecar files `.webp` and `.avif'.
Headlines and UX:
- Browser Cache headers.
- Cookie notice banner with consent memorization.
3. Cleaning WordPress `CleanupManager`
Cleaning the core and head:
- Disable Emoji, scripts, styles, RSS staticize.
- Clearing the `wp_head` from service links and tags.
- Deleting the `dns-prefetch'.
- Removing the `recent comments` styles.
- Removing the `ver` from CSS and JS query parameters.
Content and comments:
- Removing the Site field from the comments form.
Performance and service functions:
- Disabling jQuery Migrate on the frontend.
- Disable RSS feeds and redirect to the main page.
- Disable email notifications about auto-updates, core, plugins, themes.
- Disabling Gravatar.
The admin interface:
- Removing links WordPress.org from the admin bar.
- Disable rarely used widgets, Pages, Calendar, Tag Cloud.
- Disabling the upper admin panel on the frontend.
Revisions:
- Limitation of the number of revisions.
- Complete shutdown of revisions.
4. SEO hygiene of `SeoManager` and `SiteStructureManager`
Technical SEO:
- The header is Last-Modified and the correct 304 is Not Modified.
- Noindex for pagination.
- The 'replytocom` redirect.
Elimination of duplicates:
- Redirect date archives.
- Redirect of the authors' archives.
- Redirect tag archives.
- Redirect attachment pages.
- Redirect duplicates of the form `/post/1/`.
Structure and indexing:
- Removing WP JSON API links from `<head>'.
- Disabling the public REST API for guests.
- HTTP -> HTTPS redirect.
- Custom `robots.txt `.
Yoast-compatibility:
- Removing the debug comment in the `<head>`.
- Disabling JSON-LD.
- Removing `<image:image>` from Yoast's XML sitemap.
5. Security of the `SecurityManager`
Basic hardening:
- Disabling XML-RPC.
- Removing the 'X-Pingback'.
- Ban the file editor in the admin area.
- Hiding the WordPress version.
Protection against enumeration and leaks:
- Blocking of the `author` query parameter and author archives.
- Disabling REST endpoint users.
- Masking the text of login errors.
Entry protection:
- Restriction of login attempts, IP lockout.
- The attempt limit and the blocking time are configurable.
Uploads protection:
- Creating a `.htaccess` in uploads with a ban on PHP execution on Apache.
Logs:
- Security event log.
- Clearing the log from the interface.
6. Redirects and 404 `RedirectManager`
- Custom redirects in the `/old -> /new` format.
- 404 error log, URL, referer, time.
- Clearing the 404 log.
7. Tools and integrations
Export and import:
- Export all settings to JSON.
- Import settings from JSON with secure sanitization.
The database:
- Clearing expired transients.
Cloudflare:
- Saving the Zone ID and API Token.
- Purge Everything.
- Purge the URL list.
- Checking the success of purge by the `success` field in the API response.
8. Quick actions in wp-admin bar `AdminBarMenu`
- Open the plugin panel.
- Clear the cache.
- Optimize the database.
- Warm up the cache.
- Clear the 404 log.
- Check the license.
- After the actions, return to the current admin page via the referer, without forcibly switching to the plugin.
9. Setup Wizard and presets `PresetManager` and `PresetHandler`
Presets:
- Blog.
- E-commerce.
- Aggressive.
Wizard Options:
- Apply the recommended optimizations.
- Clear the cache after application.
- Open the desired tab after application.
The behavior of the wizard:
- The profile is saved after application.
- The wizard is automatically marked as completed and hidden.
- The wizard also hides after saving the settings normally.
- There is a manual button to hide the wizard.
10. Interface and diagnostics
Tabs:
- An overview.
- Performance.
- Cleaning.
- SEO.
- Security.
- Tools.
- License.
UI:
- Modern switches.
- Descriptions and hints for each function.
- Convenient action buttons and separate forms by context.
Diagnostics:
- KPI cards, license, 404, TTL, cache statistics.
- Separate cache diagnostics, HTML and REST files, and size.
- Diagnostics of cron tasks, scheduled cleaning of URLs and sitemap preload.
Language support
Russian basic
English
Kazakh
Uzbek
Chinese.
Notes
PHP 7.4 and WordPress 6.0 or higher are recommended.
The PHP blocking feature in uploads requires Apache and `.htaccess` support.
Some features, such as disabling the public REST API, may affect third-party themes and plugins that use REST on the frontend.
Support
If you have any questions or concerns, please contact the author.
Alex Osmanov
🌐 Website: https://pluginhub.pro
📧 Email: support@pluginhub.pro
💬 Telegram: @alexosmanov_ru
Platform
WordPress
Version
1.0.0
Requires
7.4
Tested up to
7.0
Downloads
0
In the archive
In your account
Step-by-step guide
After payment open your account, download the ZIP and save the license key.
Upload via your site admin panel, activate the plugin and check write permissions.
Enter API keys and configure webhook notification URLs.
Run a test payment or check and make sure the integration works.
Installation, customization and care — add to cart and check out.
Install the plugin on your hosting, compatibility check, initial activation.
Deep configuration for your scenario: fields, integrations, roles.
Per form: CRM, email, messengers within plugin API.
Link catalog to external system: schedule, fields, filters.
Targeted PHP/JS changes for your workflow (agreed scope).
Landing or corporate site on CMS from PluginHub ecosystem.
OpenCart / WooCommerce / PrestaShop: catalog, payments, shipping.
New module for CMS API: spec, code, review, handover.
Questions
Need migration, turnkey install or compatibility check? Contact support before payment.
The license covers one project. Extended licensing for more sites is available — ask support.
Yes — 12 months of updates, fixes and install guidance via the ticket system.
Refunds within 14 days if the plugin was not activated on a production domain.
Right after payment confirmation the archive and license key appear in your account under Licenses.
The plugin sends successful requests from Contact Form 7 forms to the MAX messenger via the chatbot API (platform-api.max.ru ). It is suitable for notifying managers in a group chat or for private messages to the user.
The Zendesk for WPForms plugin connects a WordPress site to Zendesk Support. After successful submission of the WPForms form, a new ticket is created on the Zendesk side: the subject is collected from the prefix (if specified), the name of the form and the entry number (entry); the fields of submission are listed in the body of the ticket; the applicant (requester) is determined by email from the form (a valid Email field or a value similar to email is required).
Zendesk for Contact Form 7 connects your WordPress site with Zendesk Support: upon successful submission of the Contact Form 7 form to Zendesk, a new ticket is created with the subject, text, email, and applicant's name (requester), priority, and tags according to your rules.
Ready to launch
Buy the plugin and get the file, license, guide and updates from our catalog.