Measured · not a PageSpeed score · your own install
One plugin, one button, two minutes. It names the plugin, query or background task that is eating your dashboard, your backend and your WooCommerce order screens. No credentials, no server access, nothing for you to undo.
The plugin runs on your site. The file stays yours. You send it only if you want to.
Because page caching never applies once you are logged in. Every visitor gets a file that was built earlier. You get a page that is built from scratch, every single time, running every plugin that hooks into the admin. On the site you are reading, that difference is 0.10 seconds against 2.68 seconds, measured the same day with the same tool.
This is also why a PageSpeed score of 98 tells you nothing about the screen you actually work in. Those tools measure the cached, logged-out page. Nobody measures the other one, which is the reason this service exists.
admin-ajax.php and the heartbeat firing every fifteen seconds while you work.There is no form to fill in first, and no call to sit through.
A normal WordPress plugin, installed from a ZIP the way you install any other. It reads only. It changes no setting, no content and no other plugin.
It loads each of your main admin screens five times and takes the median, then reads your environment. Under two minutes on most sites.
You get a file with your numbers. Send it to us for the written audit, or keep it and act on it yourself. Then delete the plugin.
The measurement gives you numbers. The audit tells you what they mean, which of them is worth money to fix, and which of them is normal for a site your size.
It also contains a section listing what is not the problem, so you do not pay somebody to fix the wrong thing. On this site that section rules out the front end, the autoloaded options, the scheduled tasks and the PHP version.
In a WooCommerce store, slowness is not one problem but two, and a caching plugin fixes neither of them.
The admin side: the orders screen is the one page nothing can cache. It is per-user, always current, and in most stores it reads orders out of tables shared with every post, page and product on the site.
The customer side: the cart, the checkout and the add-to-cart calls are excluded from caching deliberately, because otherwise the shop would show stale prices and stock. WP Rocket and the rest do exactly what they promise, and they do it well, but they do not touch these. That is why a store can score well on a speed test and still stall at the checkout.
Read about shops → A page of its own on order screens, where your orders are stored, and what a slow orders list costs in paid hours.
Two things, and the first one is free because a machine does it.
The plugin, your numbers, your file. No account, no email required to run it, no obligation. If the numbers turn out fine, you have lost two minutes and learned something.
Download the plugin (24 kB) Plugins → Add New → Upload Plugin → Install → Activate. Then Tools → AdminVelox Audit.
A fixed scope and a fixed price. We read your measurement, reproduce what needs reproducing, and write up what is slowing your admin, what is a real risk, what is not worth touching, and in which order to act. Delivered in writing, with the reasoning shown.
Fixing the findings is separate work and is quoted after the audit, because until the causes are named nobody can price the cure honestly.
If you go on to order fixes worth more than $1,150, the audit fee comes off that invoice. In practice you only pay for the audit if you decide not to have us do the work.
If the audit does not identify at least three specific, named causes of slowness in your WordPress admin, you pay nothing and you keep the report.
Once the report has been delivered and it does identify them, the fee is not refundable. The work product has been provided.
What this guarantee does not cover: it is a guarantee about the findings, not about how fast your admin becomes. Implementing the fixes is separate work, and the result depends on which recommendations are carried out.
Order the auditor pay now, $450If you pay now, the check still happens first. If three named causes are not there, we refund in full. One form, and you attach the measurement file. We check it within one business day and tell you whether three named causes are there. If they are, we send a payment link, and the audit reaches you within 48 hours of payment. If they are not, we say so and you are not charged.
A form, not an email thread. Attach the measurement file and you get a sharper answer sooner.
If you would rather not run the measurement yourself, leave the file out and say so. We will agree on a temporary account that you can delete the moment the work is done.
An audit that hides its limits is not an audit.
Where the evidence points at the server rather than the site, the audit says so plainly, and says what to ask your host.
Not for the measurement. The plugin runs on your site, under your own session, and produces a file you control. Credentials only come up if you buy the fix afterwards and want us to carry it out.
It reads only. It writes nothing except its own rows, it is inert until you press the button, and removing it deletes those rows. It never touches payments, orders, webhooks or any integration.
Probably not, and that is deliberate. This is about the admin. If your public pages are slow too, the cause is usually somewhere else, and there are plenty of people who do that work well.
That is the most common case, and the most expensive one, because it is the screen your staff sit in all day. Order and product screens are measured separately from the rest of the admin.
Because the combination is usually the cause, not one culprit, and because the plugin you would remove is often the one the business runs on. The point of measuring first is to know which one is worth the disruption.
Two minutes, no credentials, no obligation. You will know within the hour whether your admin is slow for a reason worth paying to fix.
No forms. No bots. Just email.