Free WordPress audit

WordPress Site Audit

Check whether theme bloat, plugins, weak technical SEO, speed issues, or security basics are creating hidden drag on the site.

WordPress, plugin, builder, CDN, and analytics hints
Performance, SEO, and security findings in one report
Route to optimization, SEO, security, or rebuild work only when evidence supports it
Free Site Audit
WordPress profile

Find the WordPress issues worth fixing first

The scan detects public WordPress signals, performance friction, SEO structure, security basics, and stack evidence.

Find the strongest blocker
See benchmark confidence
Get the right service path

Audit profile

Passive public checks only. No login, no invasive security probing, no load testing without owner approval. This is a diagnostic for a better build decision, not an automated promise.

Benchmark evidence

Queued signals

Response

--

Queued

Public response score --

PageSpeed Mobile

--

Benchmark unavailable

Lighthouse mobile lab benchmark

PageSpeed Desktop

--

Benchmark unavailable

Lighthouse desktop lab benchmark

Field CWV

--

Field unavailable

LCP -- · INP -- · CLS --

Technical SEO

--

Queued

Public HTML scan

Security

--

Queued

Public header scan

Audit progress

Current steps

Fetch public page

queued

Read SEO and stack signals

queued

Run PageSpeed and CrUX

queued

Build your fix plan

queued

WordPress

Queued

Performance

Queued

Technical SEO

Queued

Security Basics

Queued

Stack Detection

Queued
Full report preview

What unlocks after the preview

The emailed report keeps the benchmark evidence, explains what each signal means, and gives your team a practical agenda for a Directorism expert review.

Benchmark evidence

Lab, field, response, and public quality signals.

Fix order

What to repair first, review next, or validate deeper.

Expert route

The most relevant Directorism next step when the evidence supports one.

SCAN SCOPE

What the audit measures

The audit combines our passive public checks with Google lab and field benchmarks where available. We use it to identify the technical blockers a visitor, crawler, or browser can already see before we recommend a build, repair, or deeper review.

Performance

First response timing, cache headers, compression, PageSpeed lab scores, and Core Web Vitals field data when available.

Technical SEO

Titles, descriptions, headings, canonicals, schema, social previews, and indexability hints.

Security Basics

HTTPS, browser protection headers, mixed-content risk, and public exposure signals.

Builder Roadmap

Detected stack, benchmark results, and public issues become an expert agenda for optimization, reconstruction, or deeper audit work.

BENCHMARK METHOD

How the scan turns a URL into evidence

A useful audit separates what we can verify immediately from what needs owner-approved access. The preview is fast, public, and conservative by design, so the next conversation starts with evidence instead of guesses.

No login required.
No invasive vulnerability probing.
No load testing without owner approval.
Missing field data is treated as neutral, not as a penalty.

Benchmark ladder

From public response to fix order

Evidence first

Public response

TTFB, cache, compression

We fetch the public page safely and check the first response, cache policy, content encoding, redirects, and protection pages.

PageSpeed lab run

Mobile and desktop

When the Google key is configured, Lighthouse scores performance, accessibility, best practices, and SEO for mobile and desktop.

Field Core Web Vitals

Real Chrome users

CrUX checks 75th percentile LCP, INP, CLS, FCP, and TTFB at URL or origin level when enough real-user data exists.

Public quality scan

SEO, trust, stack, CRO

The public scan inspects metadata, headings, canonicals, schema, Open Graph, security headers, analytics tags, stack, forms, and CTAs.

YOUR REPORT

Turn public signals into an expert agenda

The report explains what matters now, what can wait, and which issues need deeper access before Directorism recommends optimization, reconstruction, or a full owner-approved audit.

See whether the growth problem is speed, search visibility, trust, measurement, conversion, or platform fit.
Separate lab data from real-user field data so a fast server response does not hide a weak mobile marketplace experience.
Know which fixes are low-effort wins and which ones need owner-approved access before anyone promises a fix.
Bring a technical agenda into a Directorism review instead of guessing from generic PageSpeed screenshots.