Performance
Server response time, compression, page caching, HTTP version, render-blocking scripts and styles, third-party code, image sizes and formats, and browser caching.
Paste a URL. See what your stack is costing you.
Get a scored report in about 20 seconds: speed, SEO, security and WordPress health, a Bloat Score for your stack, and a plain-English fix for every issue, most important first.
Every check comes with why it matters and how to fix it, ranked by impact so you know what to do first.
Server response time, compression, page caching, HTTP version, render-blocking scripts and styles, third-party code, image sizes and formats, and browser caching.
Title, description, H1, canonical and noindex, structured data, social tags, robots.txt, sitemap, redirect chains, broken internal links and www or non-www duplicates.
HTTPS and certificate, security headers, mixed content, exposed .env, .git and debug files, XML-RPC, username leaks and signs of injected code.
Core version against the latest release, theme, every plugin checked against WordPress.org for outdated or abandoned code, page builder weight and PHP version.
Viewport and zoom, page language, image alt text, form labels and links or buttons that screen readers cannot name.
Trackers found on the page compared with whether a cookie-consent tool is present, useful for UK GDPR and EU ePrivacy.
More than 60 checks in six groups: performance (server response, compression, caching, render-blocking files, images, page weight), SEO (titles, descriptions, headings, canonicals, indexing, schema, sitemap, robots.txt), security (HTTPS, headers, exposed files, XML-RPC, username leaks, signs of injected code), WordPress health (core, theme and plugin versions, abandoned plugins, PHP), accessibility basics and a sample of your internal links.
Yes. It makes normal page requests plus a few requests to well-known public paths, such as robots.txt, the sitemap and xmlrpc.php. It never logs in, submits forms or tries passwords. Only scan sites you own or manage.
The audit measures server response time, compression, caching, render-blocking files, images and page weight itself. When Google PageSpeed data is available for the scan, the Lighthouse score, Core Web Vitals and Chrome field data are added to the report.
It looks for visible signs in the page source, such as hidden iframes, obfuscated scripts and hidden links, and for exposed sensitive files. A clean result is not proof that a site is safe, because malware can hide in files and the database. If anything looks wrong, a hands-on cleanup is the next step.
A 0 to 100 figure where higher means heavier. It combines the page builder, the number of plugins loading files, sampled page weight, script and stylesheet files, render-blocking files, third-party domains and server response time. The breakdown under the score shows exactly how it was built.
Only if you type your monthly online revenue. It uses a simple, adjustable model: no loss up to 2 seconds of load time, then 7% fewer conversions for each extra second, capped at 35%. It is an illustration, not a measurement, and your real numbers will differ.
Your report is kept for 30 days at a private link that only works if you have the address. I only get your email if you type it into the "email me this report" box.
Yes. Hacked-site cleanup, speed fixes and updates are available at fixed prices, and larger rebuilds are scoped after a short call.