Independent theme evidence lab

Pretty fast.
Prove it.

Choose a WordPress theme with the conditions attached. We separate measured lab baselines, repository facts and editorial judgment—so a clean demo never passes for a real-world guarantee.

First dataset published 16 Aug 2026 · Three mobile runs per theme

PREVIEW BASELINE / MOBILEControlled, not conclusive
Lab study
01
LOWEST SELF-CONTAINED LCPGeneratePress
0.93s
Transfer25 KBmedian
Blocking0msTBT, not INP
Shift0.000CLS
EvidenceModerateone scenario
  1. 01GeneratePress0.93s
  2. 02Kadence1.08s
  3. 03Blocksy1.08s
  4. 04Botiga1.23s
Read the test conditions and limits →
Every fact wears a source labelMeasuredOfficial repositoryEditorialField data unavailable

Shortlist, with caveats

Strong foundations—not magic scores

These are editorial starting points. Open a profile to see the measured baseline, dependency warning and who should actually use it.

View all theme profiles →

The real problem

A theme is one link in the chain.

A tiny empty shell can top a benchmark and still become a heavy production site. We make the hidden layers visible before you commit.

See what actually makes WordPress slow →
  1. 01
    Themetemplates, base CSS, layout system
    measured here
  2. 02
    Builder + blocksrendering, assets, DOM depth
    varies
  3. 03
    Pluginsqueries, scripts, third parties
    varies
  4. 04
    Contentimages, fonts, embeds, inventory
    varies
  5. 05
    Hosting + cacheTTFB, edge delivery, runtime
    varies

Evidence model

No blending unlike data into one mystery number

Lab and field measurements answer different questions. Vendor and repository facts have different confidence again.

01Measured

Measured preview lab

Three fresh Lighthouse mobile runs on the official WordPress.org preview. Useful for a controlled baseline—not a production promise.

Current test setup →
02Field

Real-user field data

CrUX can reveal production experience, but reliably attributing WordPress sites to a theme is difficult. We show “unavailable” instead of guessing.

Why field and lab differ →
03Official repository

Repository metadata

Version, update date, ratings, install bucket and screenshots come from the public WordPress.org Themes API, with a retrieval date.

Review sources →
04Editorial

Fit and trade-offs

We interpret workflow, dependencies, visual flexibility and scenario fit. Judgment is clearly labelled and kept out of measured metrics.

Editorial rules →

Two-minute decision tool

Start with your stack, not a leaderboard.

Tell us what you are building, how you edit and where you accept complexity. The finder explains its match—not just the result.

Open the theme finder →

EXAMPLE MATCH LOGIC

SiteContent publication
EditorNative blocks
PriorityLowest dependency risk
Likely matchGeneratePressbecause it stays neutral without requiring a builder