Theme audit · Beginner · one evening
How to choose a WordPress theme — Audit the Demo in DevTools Before You Fall for It
You are about to inherit somebody else's request waterfall for the next three years, so measure the demo before you read a word of the sales page.
The short answer
Judge a theme on what its own demo does on the wire: how many requests the front page makes, how many bytes it transfers, how much CSS and JavaScript is render-blocking, and how many web fonts and icon fonts it enqueues on a page that uses none of them. Open DevTools on the demo and read the Network panel before you read the feature list.
That is the measurement that predicts your next three years. A theme you can strip back is worth more than a theme that looks finished, because the bundled slider, the icon font and the page builder that came with it will still be loading on every page long after the design has been replaced.
By the HostingFast team · Reviewed 24 August 2026
Beginner
Skill floor
Quick
Hands-on time
5
Steps in total
24/7
Support on call
You need an evening, a browser with DevTools and a staging site for the finalist. Managed WordPress plans here allow up to 10 staging copies, so auditioning two themes properly is not a problem.
Nothing here changes your live site until the final step, and even then the staging copy means the audition happens somewhere nobody can see it.
Read the Network panel before the sales page
Open the theme's own demo, open DevTools, hard reload with the cache disabled, and read four numbers off the Network panel: total requests, transferred bytes, the number of render-blocking stylesheets, and how many separate font files load. Then run Lighthouse against the same URL and note the largest contentful paint element.
Demos are the theme at its best: fast hosting, optimised images, no plugins fighting it. If the demo already makes a hundred and forty requests and ships six hundred kilobytes of CSS, your version will be worse, not better, because you are going to add content and functionality to it.
The costs you cannot remove later
Some weight is optional and some is welded on. A bundled page builder that stores content as shortcodes means leaving the theme later requires rebuilding every page. An icon font loaded globally for three icons is a font file on every request. A slider library enqueued site-wide is JavaScript parsed on pages with no slider.
Check what the theme enqueues on a page that uses none of its features — a plain blog post is the honest test. Anything loading there is loading everywhere, and no optimisation plugin removes it cleanly, it only defers the moment you pay for it.
Block themes, classic themes and the CSS budget
A block theme leans on the editor's own styles and tends to ship less bespoke CSS, which usually means fewer stylesheets and a smaller critical path. It also means the block editor is the design surface, so if the team expects a visual builder that is a conversation to have before you commit.
A classic theme with a good stylesheet can be just as quick, and a classic theme with a bundled builder rarely is. The pattern that predicts trouble is not the era of the theme, it is how much of the design lives in generic drag-and-drop wrappers rather than in semantic markup.
Auditioning the finalist properly
Install it on a staging copy with your own content, not the demo's, because real content is longer, uglier and heavier than the placeholder. Then measure the same way you measured the demo and compare against the baseline you took from your current theme.
Throttle to a slow mobile profile in DevTools while you are there. A theme that is pleasant on a desktop connection and unusable on a throttled one is a theme whose problems will arrive as a bounce rate rather than as a complaint.
The stack these steps were measured on
Every walkthrough here is run against the platform we operate — cPanel, LiteSpeed in front of NVMe, Softaculous, WP-CLI over SSH — so the field names in the instructions are the field names on your screen.
Backups run daily on every plan, and restoring a file or a database is one action in the panel rather than a support ticket.
- Judged on requests and bytes, not screenshots
- The welded-on costs identified up front
- Auditioned on staging with real content
- Engineers on support at any hour
Why HostingFast
Standard on every plan
Measured, not admired
The evaluation is four numbers from the Network panel plus a Lighthouse run, which is a decision you can defend in six months.
Permanent costs identified
Bundled builders, icon fonts and global sliders are named as the things you cannot remove, before you commit to them.
The honest test named
Checking what loads on a plain blog post reveals what is enqueued site-wide, which is the weight you actually pay for.
5 steps, no padding
Five checks, each producing a number or a yes-or-no answer, and any theme that fails one is off the list.
Auditioned on real content
The finalist goes on a staging copy with your own content, because placeholder text flatters every design ever made.
Engineers on call
Support answers at any hour, including the questions about what a theme is doing to your cache behaviour.
Quick Start
From order to online
- 1
Measure your current theme first
Before you look at anything new, record requests, transferred bytes and largest contentful paint for your own homepage and a typical inner page. Without that baseline every candidate looks like an improvement, including the ones that are not.
- 2
Open the demo in DevTools and read four numbers
Hard reload with caching disabled and note total requests, transferred bytes, render-blocking stylesheets and font files. Run Lighthouse on the same URL and note which element is the largest contentful paint.
- 3
Check what it loads on a page using none of its features
Find a plain blog post on the demo and look at what is still enqueued. Icon fonts, slider libraries and builder assets that appear there are loading on every page of your site, forever, whatever you build.
- 4
Read the changelog and the support forum, not the screenshots
A theme updated three times in the last year by a responsive author is worth more than a prettier one abandoned eighteen months ago. The support forum tells you what breaks and how quickly it gets fixed, which the sales page never will.
- 5
Audition the finalist on staging with your own content
Clone the site, install the theme, import real content, then measure exactly as you measured the demo and compare against your baseline. Throttle to a slow mobile profile before you decide anything.
Built In
Loaded onto every plan
- Staging environments for testing before you ship
- NVMe storage on every tier, not only the expensive ones
- LiteSpeed caching in the server, not bolted on by plugin
- WebP conversion built in, at no extra cost
- WordPress Toolkit, with updates applied for you
- Daily backups with self-service restores from the panel
- Per-site PHP version switching in the control panel
- Support staffed by humans, every hour of the day
- In-place account upgrades, with no migration to change plan
- A renewal price identical to the one you signed up at
Frequently Asked
What people ask us most often
How many requests should a theme's front page make?
There is no magic threshold, and anyone quoting one is guessing. The useful framing is comparative: measure two or three candidates the same way and pick the lightest that does the job, then check the result against the Core Web Vitals bands — largest contentful paint under 2.5 seconds, interaction to next paint under 200 milliseconds, layout shift under 0.1. A demo already struggling to hit those will not improve once you add content.
Is a block theme faster than a classic one?
Usually, but not because of the era. Block themes tend to ship less bespoke CSS and lean on the editor's own styles, which shortens the critical path. A well-written classic theme can match it. What reliably predicts a slow site is a bundled page builder storing content as shortcodes, and that can appear in either category.
Does a page builder always cost me largest contentful paint?
It costs you CSS and JavaScript on every page whether or not that page uses builder features, and it usually wraps content in several layers of generic divs, which makes the critical path longer. Whether that shows up in LCP depends on your hero element. What is certain is the lock-in: content stored as builder markup means changing theme later is a rebuild rather than a swap.
Child theme, or the theme's own customiser?
Use the customiser and the theme's settings for anything it supports, because those survive updates by design. Create a child theme when you need to override template files or add functions, since editing the parent directly means your changes disappear at the next update. If you find yourself needing a child theme for basic layout changes, that is a signal about the theme rather than about you.
Keep reading
How to Speed Up WordPress
Measure, change one thing, measure again — the loop that separates a real gain from a moved score.
How to Set Up a Cron Job
Schedule work properly, and replace WP-Cron with a real cron entry so it does not depend on traffic.
WordPress (Glossary)
The definition this page leans on, with the theme and plugin relationship explained.
Email Hosting
Mailboxes on your own domain, with filtering in front and IMAP, POP and SMTP available.
Domain Names
Search, register and transfer names — first year free with an annual hosting plan.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Give the theme quicker hardware.
NVMe behind a LiteSpeed cache, staging copies to audition on, free SSL and migration, and a price that never moves.
View Email Hosting plans