Key Takeaways
- A theme demo is a sales sample, not proof that your finished website will be fast, accessible or easy to edit.
- Assess the complete stack: theme, builder, required plugins, licences, updates, hosting, content and integrations.
- Use your own page types and business tasks during the trial. A homepage demo cannot prove that a long service page, shop or multilingual site will work well.
- Record pass, concern or fail for each of the 15 checks below, with evidence and an owner for every concern.
- If important requirements need repeated workarounds, the apparent saving may disappear. That is the point to compare a leaner foundation or custom development.
An off-the-shelf WordPress theme can be a sensible starting point. It can reduce design time, give editors prepared layouts and make a straightforward business website affordable. The risk is committing because the demonstration looks polished, then discovering that the real site needs a builder licence, several companion plugins, awkward content workarounds and ongoing developer help.
This checklist is for the stage before purchase or implementation. Use it against the exact theme version, licence and plugin bundle you are considering. Install it on a private trial or staging site, add realistic content and keep notes. Do not rely only on screenshots, a vendor's speed score or a list of advertised features.
If you are still deciding between a prepared theme and a bespoke build, read our broader custom website versus template guide. That article owns the commercial comparison. This one has a narrower job: deciding whether a particular WordPress theme is safe and suitable enough to commit to.
Before starting, write down five representative items: the busiest service page, a typical article, the main enquiry form, one awkward content requirement and, if relevant, a product or checkout journey. Those examples stop the review drifting towards the easiest pages.
Test 1: Replace the Demo Content with Realistic Material
Theme demonstrations are carefully selected. Titles fit the allocated space, photographs share a style and every card contains roughly the same amount of copy. Real businesses are messier. A service name may be 12 words long. A case study may need several outcomes, a quotation and a gallery. Team members may have portrait and landscape photographs. Some pages need a comparison table or detailed terms.
Build at least three representative pages with your own draft copy and ordinary images. Check long headings, missing images, short excerpts, large tables, lists, captions and validation messages. View them on a narrow phone as well as a desktop. The theme passes when the layout remains readable without cutting important text or forcing every page into the demo's content length.
A theme that only works after rewriting every heading to fit is controlling the content rather than supporting it. That is a concern, especially for an SEO-led website where clear, specific headings matter.
Test 2: Confirm the Licence, Ownership and Allowed Use
Find out exactly what the purchase covers. Some licences apply to one production site. Others limit updates or support to a year. Bundled fonts, photographs, icons, page builders and premium plugins may have separate conditions. A developer's agency licence may not transfer to you when the working relationship ends.
Record the licence holder, renewal date, renewal cost, number of sites and what stops working if a subscription lapses. Ask whether you may create a staging copy, use the theme for more than one regional site and continue using the installed version after support ends. Keep invoices and licence keys in a business-owned account.
The theme passes when the business can prove its right to use every paid component and understands the renewal position. Do not treat access to a developer's account as ownership.
Test 3: Trace the Update Path
A theme is not a one-off design file. It sits beside WordPress core, PHP, plugins and hosting software that continue to change. Check the theme's current version, release history, supported WordPress and PHP versions, and the date and substance of recent updates. A long changelog full of compatibility fixes may be healthier than a project that has not changed for two years.
Ask how custom styling will be protected. Direct changes to vendor theme files are normally overwritten by the next update. A child theme, site-specific plugin or controlled configuration may be appropriate, but each needs documentation. Confirm that updates can be tried on staging, backed up and rolled back.
The official WordPress Theme Handbook explains the parts of a theme and the development standards around them. Use it as a reference when a supplier describes where custom behaviour will live. Pass this check only when there is a repeatable update route rather than a promise to fix problems when they appear.
Test 4: Complete Real Editing Tasks
Do not accept a guided tour of the nicest screen. Ask the person who will maintain the site to complete normal tasks without coaching. They should create a page, change a global call to action, replace an image with useful alternative text, edit a menu, schedule an article, preview the result and recover an earlier revision.
Notice where the work happens. Does the editor show roughly what the visitor will see, or does it expose rows of unexplained settings? Can a user accidentally change fonts and spacing on one page? Are reusable sections genuinely global, or must the same telephone number be updated in many places?
The theme passes when a trained editor can complete common work confidently while the design system protects sensible limits. If ordinary publishing depends on the original developer, include that ongoing cost in the decision. Our WordPress development service is built around maintainable editing as well as front-end design.
Test 5: Map Every Required Page Template
List the page types the finished website needs, not only the pages that exist at launch. A typical service business may require service, sector, location, team, case study, article, contact, search, legal and error templates. A shop may add product, collection, basket, checkout and account screens.
Create a simple matrix. Put the required page types down one side and the theme's supported layouts across the top. Mark whether each is provided, configurable, needs a small extension or requires substantial custom work. Check archive and search views as carefully as single pages because they are easy to overlook.
The theme passes when its core layout system covers the recurring content types cleanly. A one-off custom template is not necessarily a problem. Ten one-off templates suggest that the starting theme may be a poor fit. This is where a short website audit and consultation can prevent an expensive false start.
Test 6: Build a Plugin Dependency Register
Many commercial themes show features supplied by companion plugins rather than the theme itself. Import the demo on a disposable installation and note every plugin it requests. For each one, record its purpose, publisher, licence, update history, data handled and what breaks when it is disabled.
Look for overlapping jobs. Two form plugins, several optimisation tools or both a builder and a block library add choices without necessarily adding value. Check whether switching themes would leave behind unreadable shortcodes or builder-specific content. A dependency that controls ordinary headings, buttons or columns deserves particular attention because it makes future migration harder.
WordPress's performance optimisation guidance makes clear that themes, plugins, hosting and content all affect the finished result. Pass this check when every required plugin has a justified job, an owner and a replacement or removal plan.
Test 7: Inspect the HTML and Rendering
A page can look correct while its structure is confusing to browsers, assistive technology and search engines. Open the rendered source or browser inspector. Check that there is one meaningful main heading, headings follow a logical order, navigation uses links, buttons perform actions and important copy exists as HTML rather than inside images or scripts.
Turn off JavaScript briefly and inspect what remains. WordPress themes may use JavaScript for menus, filters and visual effects, but the main content and ordinary links should not disappear without a good reason. Check the page on a slow connection for flashes, overlaps and controls that become usable only after a long delay.
The theme passes when the delivered document has clear semantic structure and its essential content does not depend on a fragile visual trick. This technical check is more useful than counting how many animation styles the theme advertises.
Test 8: Measure Core Web Vitals with the Real Stack
Install the fonts, cookie controls, analytics, forms, images and plugins the finished site will actually use. Then measure the representative pages on a mid-range mobile profile. Run more than once and investigate the causes, not just the score. Large hero media, delayed font loading, builder scripts and moving banners can all change the result.
Google's Core Web Vitals documentation explains the loading, responsiveness and visual-stability signals. Laboratory tools help during development, while field data describes real visits once enough traffic exists. Do not present a clean vendor demo's laboratory result as evidence for your future site.
Set a practical performance budget before approval: which pages, device settings and third-party services are in scope, and which regressions would block launch. Our article on whether a WordPress rebuild is worth it explains the wider performance decision. This theme check passes when the real stack is within the agreed budget and the team knows how it will prevent regressions.
Test 9: Perform Manual Accessibility Checks
An accessibility label on a marketplace listing is only a starting point. The finished combination of theme, builder, plugins, colours and content needs review. Navigate the trial site using only a keyboard. Confirm that focus is visible, the order makes sense, menus can be opened and closed, modals do not trap the user and the main form reports errors clearly.
Zoom the page, increase text size and test a narrow viewport. Check colour contrast, link purpose, form labels, heading order, image alternatives and motion controls. Automated tools can identify some issues, but they cannot judge whether instructions make sense or focus moves to the right place.
Use the W3C's official WCAG 2.2 Quick Reference to connect findings to the relevant criteria. Pass this check only after manual review of the actual layouts you plan to use. If you need an independent review, see our accessibility and WCAG service.
Test 10: Verify SEO, Schema and Metadata Control
For each important page type, confirm that an editor can set a sensible title, meta description, canonical URL, index instruction and social-sharing image without editing theme files. Check that heading structure is not dictated by the visual style. Make sure breadcrumb and navigation links reflect the real hierarchy.
Inspect structured data in the rendered page. Some themes output generic organisation, article or breadcrumb markup by default. Duplicate or inaccurate schema can appear when an SEO plugin adds a second version. The correct response is not to add every possible type; it is to output accurate data that matches visible content.
Also check archive pagination, internal search, author pages and attachment pages. Decide which should be indexable rather than accepting defaults. The theme passes when metadata and schema can be controlled per content type, there is one clear owner for each setting and no unavoidable duplicate output.
Test 11: Exercise the Ecommerce Journey
If the site will sell, install the exact ecommerce system and extensions rather than trusting styled screenshots. Create products with long names, sale prices, variations, stock states and missing images. Test search, filters, basket, checkout, account, refund information and transactional messages on mobile.
Check what happens when scripts fail or a payment is declined. Confirm that validation explains the problem without deleting entered information. Review taxes, delivery rules, currencies and consent with the people responsible for those areas; a theme cannot decide business policy for you.
Performance matters across the whole journey, not only on the product page. A beautiful catalogue is not enough if the basket clashes with the theme or an update breaks checkout. Pass this check when the supported ecommerce templates work with realistic products and the critical purchase route has an update and regression plan.
Test 12: Check Localisation and Multilingual Behaviour
Even a UK-only site may need dates, addresses, telephone numbers, tax wording or regional pages handled consistently. If more than one language or market is planned, test it before choosing the theme. Add a long translated heading, switch text direction if relevant, change date and number formats and examine menus, forms, search and error messages.
Identify text that is hard-coded in theme files or supplied by plugins. Confirm that it can be translated through normal WordPress methods. Check how language versions connect, how URLs are formed and whether hreflang will be managed by a supported tool rather than improvised template code.
The theme passes when localisation affects the whole journey, including validation and transactional content, not just the navigation. If international expansion is only a future possibility, record the likely route and cost now so today's theme does not quietly close that option.
Test 13: Prove the Important Integrations
Write down the systems the website must exchange data with: CRM, email marketing, booking, payment, analytics, consent management, recruitment or internal reporting. A marketplace badge saying that a theme is compatible with a plugin does not prove the complete workflow.
Build a small end-to-end trial for each business-critical connection. Submit the form, check the record reaches the correct system, confirm consent and source fields are retained, and test the confirmation and error routes. Decide which integration belongs to the theme, which belongs to a plugin and which should remain independent of presentation.
The theme passes when critical connections still work after a theme update and can be monitored without examining the screen manually. Avoid putting business logic directly into a vendor theme where a future design change could remove it.
Test 14: Review Security and Ongoing Maintenance
No visual theme can secure an entire WordPress website, but it can add risk through old libraries, bundled plugins, unsafe custom code or an abandoned update path. Check the publisher, support channel, update history and responsible disclosure route. Search the changelog for security fixes and confirm that required plugins are still actively maintained.
Agree the operating routine before launch: backups, staging, update frequency, malware monitoring, user access, multi-factor authentication where supported, logging and rollback. Remove demo importers, inactive plugins, sample users and unused templates after setup. Give licences and hosting accounts to the business rather than leaving them in a freelancer's personal account.
The theme passes when maintenance has named owners and a documented recovery route. A theme sold as a one-off purchase still lives inside software that changes. Budget for that reality.
Test 15: Score the Exit Route and Custom-Development Decision
The final check asks what happens if the theme stops fitting. Export the trial content. Switch temporarily to a standard WordPress theme and see what remains usable. Identify shortcodes, builder data, custom post types and settings that disappear. Record how forms, redirects, media and SEO fields would move.
Score all 15 checks as pass, concern or fail. A concern needs a cost, owner and mitigation. Treat a fail as serious when it affects a core customer journey, accessibility, security, search control, ownership or the ability to maintain the site. Several low-impact concerns may be acceptable for a short-lived campaign. Repeated failures across core requirements point towards a different theme, a lean custom WordPress foundation or another platform.
This is the boundary between selection and development. Do not choose custom work simply because it sounds premium. Choose it when the prepared options cannot meet important requirements without brittle overrides, unnecessary dependencies or recurring costs. If you want a second opinion on the evidence, contact MattDarm before the build is committed.
Turn the Results into Acceptance Criteria
Keep the checklist with the project brief. For every concern, state what must be true before launch and how it will be checked. For example: “The service-page template must keep a 70-character heading visible at 320px width,” or “An editor must update the global enquiry call to action in one place.” Specific wording makes approval possible.
The theme does not need to win every cosmetic preference. It does need to support the content, journeys and maintenance model the business actually has. If it passes the important checks with only small, documented gaps, it may be a very efficient foundation. If the evidence depends on replacing half the stack, it is no longer an off-the-shelf saving.
Frequently Asked Questions
Can I properly assess a WordPress theme before buying it?
You can usually assess the documentation, licences, update history, demo structure and support record before purchase. For editing, plugin and performance checks, ask for a trial, use a refundable option where the terms allow it, or ask the implementer to build a private proof of concept before the full project is approved.
How many plugins is too many for a WordPress theme?
There is no useful universal number. Ten focused, maintained plugins can be safer than three large overlapping ones. Record what each plugin does, what it loads, who maintains it, which data it handles and what breaks if it is removed.
Does an accessibility-ready theme make the finished website compliant?
No. It describes the starting theme, not the completed combination of colours, content, plugins and custom changes. Test representative finished pages manually against the accessibility target agreed for the project.
Should I reject a theme that does not get a perfect performance score?
No. A single perfect laboratory score is not a sensible buying rule. Test representative pages with the real fonts, images, consent tools, forms and plugins, then judge them against an agreed performance budget and the causes of any weakness.
When should I stop adapting a theme and choose custom development?
Consider a different foundation when important journeys, editing tasks, accessibility, integrations or SEO controls need repeated workarounds. Price the workarounds, maintenance and exit cost, then compare that total with a lean custom build.
Make the Decision from Evidence
A prepared WordPress theme is useful when it reduces work without creating hidden operational debt. Run the checks with real content, keep the evidence and make important gaps part of the contract. If the theme can pass on those terms, commit with confidence. If it cannot, change direction before the costly implementation begins.
