September 24, 2026
September 2026: WordPress Toolkit - a page for every site, PageSpeed and one-click security
The WordPress Toolkit used to be a list of sites with a Log in button. Now every site has a page of its own. Click Manage on any tracked site and you get an overview, a speed report, performance switches and a Security tab that hardens the site in one pass - with no config files to edit and no plugin to install.
An overview of the site
Summary cards show the WordPress version (flagged latest, outdated or insecure), the PHP version, the active theme, how many plugins are active and how many are waiting for updates, the account's disk usage and the state of its SSL certificate - next to a screenshot of the home page. Log in takes you straight into wp-admin as an administrator, without the password.
The page opens instantly from the last known state of the site and refreshes itself a second later, so you are never waiting on WordPress to boot just to look at it.
PageSpeed scores
Add a free Google PageSpeed Insights API key in Settings and each site gets a PageSpeed card: mobile and desktop tested at the same time, the four Lighthouse scores - performance, accessibility, best practices and SEO - and the Core Web Vitals behind them. The same test supplies the screenshot, so servers with no browser installed get one too.
Performance, applied live
- Nginx cache - pages served from nginx's FastCGI cache instead of PHP, with logged-in users, carts and checkouts never cached, and the Reqad Cache Purger plugin clearing it whenever content changes.
- Disable WP cron - a real system cron job every 2 minutes instead of cron running on visitors' page loads, now logged to
~/logs/cron.log. - Search engine indexing - switch it off on staging and development copies.
- Maintenance mode - visitors get a "back soon" page with HTTP 503, so search engines come back later instead of dropping pages, while you keep working on the live site.
Security in one click
The Security tab holds 17 hardening measures. Tick Select recommended, press Apply changes, and each row reports what is now in force. Unticking a measure reverts it.
- Web server rules - block xmlrpc.php, wp-config.php,
readme.html, dot-files, backups and database dumps; refuse PHP inwp-includes,uploadsand cache directories; stop author scans and aggressive crawlers; and send HSTS, X-Frame-Options and nosniff headers. - WordPress - hide the WordPress version from pages, feeds and script URLs; disable file editing and script concatenation in the dashboard; turn off pingbacks; or move the login page to an address of your choice.
- Files and keys - make sure all eight security keys and salts are strong, and lock
wp-config.phpdown to its owner.
Blocked requests answer 404, not 403: to a scanner, a protected file looks exactly like a missing one.
Login only from your IPs
For sites where only you log in, one option shuts password guessing down entirely: wp-login.php and the core update screens answer only to the IPs you list. Reqad adds the server's own addresses automatically so WordPress updates keep working, leaves password-protected posts open to everyone, and warns you before applying a list that would lock you out. If your IP changes anyway, the panel's Log in button still gets you in.
Error pages for every site
Every site now has clean 403, 404, 500, 502, 503 and 504 pages, in light and dark, that do not name the web server. WordPress keeps its own themed 404 and maintenance pages - Reqad's only appear where WordPress does not answer.
A fix worth updating for
While building the security rules we found that on nginx servers the vhost's rule refusing PHP inside wp-content/uploads never matched, because it came after the PHP handler. New vhosts are generated correctly, and updating Reqad corrects every existing vhost automatically - tested and rolled back if nginx rejects the result.
The full walkthrough is in the documentation: WordPress Toolkit.