# Before you buy a website template: a 10-point checklist

> Ten checks to run before you buy a website template: pages, content, mobile, keyboard, contrast, speed, licence, updates and AI readiness. Most take minutes.

- Author: [Vas](https://shipthemes.com/authors/vas)
- Published: Oct 28, 2026
- URL: https://shipthemes.com/blog/premium-template-checklist

Screenshots show how a template looks, but not whether it is pleasant to work with, usable by every visitor, or legal to use for your project. Below are ten checks you can run before you pay: most take a few minutes and need no code.

This checklist is for people who choose a template for their own site or for client sites and are not expected to know programming. For each point: why it matters, how to check it, and what should make you wary.

We sell Astro templates, so we have an interest here. The checks fit any template, ours included. We have not tried to measure how much the checklist protects against a bad purchase: these are practical rules, not research results.

> **Current as of October 26, 2026.** Software versions, standards and service terms change, and everything here is stated as of this date. The numbers in brackets point to the sources at the end of the page.

## In short: ten points

1. **The pages you need are there.**
2. **Texts live separately from the layout.**
3. **Colors and fonts are set in one place.**
4. **The site works on a narrow screen.**
5. **The site can be used with a keyboard.**
6. **The text has enough contrast.**
7. **Pages load quickly.**
8. **The license allows your use.**
9. **The template is updated, and you can see it.**
10. **The template is ready for work with AI.**

Points 1–3 can be checked from the description and documentation, points 4–7 in a browser on the demo, and points 8–10 from the license text, the changelog and the project files. By our estimate, a full pass takes about 15 minutes; the order of steps is at the end of the article.

## Design and content: points 1–3

### 1. The pages you need are there

**Why.** An extra page is easy to remove, but a missing one you will have to build yourself: it decides how much work is left after the purchase.

**How to check.** List the pages without which the site cannot launch: home, about, services or pricing, contact, blog, a 404 error page, a privacy policy. Compare your list with the pages of the demo and with the template’s description.

**Warning sign.** The demo has only a home page, and the list of pages is not stated anywhere.

### 2. Texts live separately from the layout

**Why.** So that you can change a text without touching the design: yourself or with an AI assistant, which then does not risk breaking the layout. Astro has “content collections” for this: texts are stored in separate files, and a schema describes the required fields; if a field is missing or its type is wrong, the build shows a clear error.[1]

**How to check.** Find the section in the description or documentation that says where page texts live. If you can access the template’s files, ask the assistant: “Where in the project are the page texts, and what do I need to change to fix the headline on the home page?” Before buying, ask the seller the same question.

**Warning sign.** The answer “edit a few dozen files” or complete silence in the documentation about where things are.

### 3. Colors and fonts are set in one place

**Why.** So that you can change the brand color without hunting for it across all the code. CSS has variables for this: you write a value once and use it everywhere it is needed.[2]

**How to check.** Look in the documentation for a section on styling or branding. Ask: “How many places do I need to change to switch the accent color and the heading font?” A good answer (by our assessment): one or two places, with a file name.

**Warning sign.** The branding documentation is silent, and you would have to change the color by search and replace across the whole project.

## Quality: phone, keyboard, contrast, speed (points 4–7)

These four checks are done in a browser on the template’s demo, and you do not need to read any code. Automated tools find only part of the problems: in a 2017 GOV.UK test on a deliberately “broken” page with 143 barriers, ten tools together found 71%, the best of them alone about 41%, the worst 17%.[3] So after the tools, look at the page with your own eyes. And accessibility problems are not limited to bad templates: according to WebAIM data for February 2026, at least one detectable WCAG error was found on 95.9% of the home pages of the million most popular sites, and weak text contrast on 83.9%.[4]

### 4. The site works on a narrow screen

**Why.** Many visitors will come from a phone. The WCAG accessibility standard (level AA) requires content to be readable without scrolling in two directions at once at a width equivalent to 320 CSS pixels. Exceptions: content that needs a two-dimensional layout, such as maps, diagrams, video, games, presentations, data tables, or toolbars that must stay in view.[5]

**How to check.** Open the demo in Chrome, right-click the page and choose “Inspect”. In the developer tools click the “Toggle device toolbar” icon and, in Responsive mode, enter a width of 320 (there is also a ready-made 320px button, Mobile S).[6] Scroll the page, open the menu, press the buttons. This is only an approximation of a real phone, so it is worth opening the demo on an actual phone as well.[6]

**Warning sign.** A horizontal scrollbar appears, text overlaps neighboring blocks, the menu does not open, or the buttons are hard to hit.

### 5. The site can be used with a keyboard

**Why.** Not everyone uses a mouse. The standard (WCAG 2.4.7, level AA) requires that wherever keyboard control exists, there is a mode with a visible focus indicator, that is, you can see which element is currently selected.[7]

**How to check.** Open the demo and press Tab. Focus should move through links and buttons in a logical order, usually top to bottom and left to right; Shift+Tab goes back, Enter activates a link or button, Esc closes dialogs and dropdown menus. At every step you should see an outline or highlight, and you should be able to leave any block using only the keyboard, with no “traps”.[8]

**Warning sign.** Nothing is highlighted when you press Tab (the outline is often removed with the style `outline: none`[8]), focus gets stuck in the menu or jumps to random places.

### 6. The text has enough contrast

**Why.** Light gray text on white is hard to read, especially with weak eyesight or in bright sun. For normal text, WCAG (level AA) requires a contrast ratio of at least 4.5 to 1; for large text (18 pt or larger, or 14 pt and larger in bold, roughly 24 px or 18.5 px bold) at least 3 to 1. Exceptions include disabled elements, pure decoration, text nobody can see, text that is part of a picture with other significant visual content, and logos.[9]

**How to check.** In Chrome, in “Inspect” mode, hover over the text: the tooltip shows the contrast number, and a warning icon appears next to it if there is a problem. In the color picker, the Contrast ratio section shows whether the color passes the AA and AAA levels.[10] Check the palest places: gray secondary text, button labels, text over photographs, the footer. You can add the WAVE extension from WebAIM for Chrome, Firefox and Edge: it identifies many WCAG errors and supports a manual review, but does not replace it.[11] After you replace the colors with your own, check the contrast again: in the template it is calculated for its own colors.

**Warning sign.** Pale gray text on a light background, white text on yellow, text over a photograph with no darkening.

### 7. Pages load quickly

**Why.** Speed shapes how a site feels, especially on a phone. You can measure it with the free tool Lighthouse.

**How to check.** Lighthouse runs from the Lighthouse tab in Chrome’s developer tools (click “Analyze page load”, then “Run audit”) or on the PageSpeed Insights website.[12] It gives a score from 0 to 100: 90–100 counts as good, 50–89 as “needs improvement”, 0–49 as poor.[13] Run the check three times: the score fluctuates from run to run, and the documentation advises looking at the spread rather than at a single number.[13] For Core Web Vitals, these values count as “good”: the largest block of the page appears within 2.5 seconds (LCP), the page responds to a tap or click in 200 milliseconds or faster (INP), elements do not “jump” during loading, and the layout shift score (CLS) is no higher than 0.1; the targets should be met for 75% of page loads.[14] Keep in mind: the demo sits on the seller’s hosting and your site will be on a different one, and your images and scripts will change the result too (this is our assessment).

**Warning sign.** The score on the demo itself is clearly below 50, or the page clearly “jumps” while loading.

## Rights and support: points 8–9

### 8. The license allows your use

**Why.** A template is bought under license terms, and they differ between stores: on ThemeForest the standard license covers one end product,[15] while on Webflow a paid template’s single-use license covers one end product for you or one client, and each further client or project needs another license.[16] If you need the template for client sites or for resale, this is the deciding point.

**What to ask the seller.**

- Which sites does the license cover: your own, client sites, resale?
- How many sites can you build from one purchase?
- How long do updates and support last, and are they included in the price?
- What about a refund if the template does not suit you? For digital goods in the EU, the right to withdraw from a purchase within 14 days is lost if you started the download after expressly agreeing to give up that right.[17]

Read the license text before buying. If client projects are at stake, show it to a lawyer.

**Warning sign.** There is no license text on the site before purchase, or it is vague, along the lines of “use it however you like”.

### 9. The template is updated, and you can see it

**Why.** A template is software, and it needs updates: for new Astro versions and with fixes. A changelog shows what changed and when. A good changelog is written for people: each version has its own entry with a date, the newest entries are on top, and changes are grouped into added, changed, deprecated, removed, fixed and security.[18]

**How to check.** Find the changelog and look at the date of the last entry. Ask which Astro version the template is built on. The Astro documentation advises moving to the current major version as soon as possible and says that old versions are not supported; as of October 26, 2026 it lists version 7 as the latest.[19] You can update Astro and its official integrations with the command `npx @astrojs/upgrade`.[19] Also ask about the template itself: what do you need to do to get its new version?

**Warning sign.** There is no changelog, the last entry is old, and the template is built on an old Astro version.

## Ready for AI: point 10

### 10. The template is ready for work with AI

**Why.** If you will change the template together with an AI assistant, it needs to understand the project quickly and check its own work. AGENTS.md is a plain text file in the project root with rules for the assistant: where things are, what not to touch, how to check the result; many tools read it.[20] The second pillar is the content schema (point 2): when a field is wrong, the build gives a clear message, and the error is visible right away.[1]

**How to check.** Three questions for the seller or for the project files:

- Is there an AGENTS.md (or CLAUDE.md) file in the project?
- Does it have commands and locations: how to run and build the site, where texts, colors and images are, what must not be changed?
- Is there one check command (usually the build) after which you know the site is not broken?

**What counts as a good file.** Short and specific. In a 2026 study (a preprint on arXiv), such files did not reliably increase the share of tasks solved and raised the cost, by over 20% on average for files written by AI; rules about non-standard practices turned out to be useful, while project overviews did not.[21] The study looked at resolving issues in code repositories, not at editing a site from a template, so its conclusion cannot be applied directly. Our conclusion: look for a precise file, not a thick one. More about these files is in our article [on AGENTS.md, CLAUDE.md and llms.txt](https://shipthemes.com/blog/agents-md-claude-md-llms-txt).

**Warning sign.** There is no file at all, or it is just a retelling of the project with no commands and no prohibitions.

## A 15-minute check: the order of steps

The times are approximate; this is our estimate. You need the template’s demo, the Chrome browser and the description or documentation.

1. **2 minutes. Pages.** Compare the template’s page list with yours (point 1).
2. **3 minutes. Phone.** Device mode, width 320, scroll the page and open the menu (point 4).
3. **2 minutes. Keyboard.** Press Tab from the top of the page to the footer (point 5).
4. **3 minutes. Contrast.** Check the 3–4 palest places (point 6).
5. **3 minutes. Speed.** Three Lighthouse runs, write down the spread of the scores (point 7).
6. **2 minutes. Documents.** Find the license, the changelog, the Astro version and the AGENTS.md file; ask the seller the questions from points 2, 3 and 8–10 that the description does not answer.

For each point, write “ok”, “doubt” or “red flag”. In our opinion, a red flag in points 8 and 9 (rights and updates) matters more than several doubts about design: you can fix the design yourself, but the license terms you cannot.

## Where the checklist will not help

- **It checks the demo, not your site.** Your texts, colors, images and scripts change both contrast and speed. After setup, repeat points 4–7 on your own site.
- **Tools do not replace a person.** A good Lighthouse score and a green WAVE report do not prove that everyone can use the site comfortably: in the GOV.UK test, automated tools missed part of the problems even all together.[3]
- **Lab tests are not the same as visitors’ experience.** Lighthouse does not replace measurements on real visitors and cannot measure INP.[14]
- **It does not assess code quality, security, or fit for your audience.** For code and security you need a specialist (our assessment).
- **It does not replace legal review.** If you must comply with legal accessibility requirements, license terms or a contract with a client, show the question to a lawyer. We are not lawyers, and this is not legal advice.

## Summary

- Screenshots do not show the main thing: how a template behaves on a phone, from a keyboard, while loading, and under its license terms.
- Most checks can be done in 15 minutes in a browser, on the demo and without code.
- A red flag in rights and updates (points 8–9) weighs more than small design flaws.
- Tools find only part of the problems: after them, look at the page yourself and repeat the checks on your own site once you replace the colors and texts.

### Want to run this checklist on our templates?

The checklist fits any template, ours included. On ShipThemes templates you can check part of it on the site itself: each template page lists its pages and has a live preview (points 1 and 4–7), the [licence](https://shipthemes.com/license) is published in full before you buy (point 8), and every release is logged in the [changelog](https://shipthemes.com/changelog) (point 9). For points 2, 3 and 10, ask us before you buy: hello@shipthemes.com. Browse the [template catalog](https://shipthemes.com/templates).

Choosing a template for a law firm? The pages, the advertising rules and the contact-form warnings to plan for are in [“Law firm website design in 2026”](https://shipthemes.com/blog/law-firm-website-design).

If you are still testing an idea rather than choosing a template, start with the article [“How to test a product idea fast: a website in one weekend”](https://shipthemes.com/blog/test-product-idea-with-landing-page). And we described how to work with a template after the purchase in the article [“How to work with a website template using AI: a simple step-by-step plan”](https://shipthemes.com/blog/work-with-website-template-using-ai).

## Frequently asked questions
### Can I check a template without knowing how to program?

Mostly, yes. Points 1 and 4–9 are done in a browser and from the documentation. For points 2, 3 and 10, the seller or an AI assistant with access to the project files is better placed to answer.

### Is a Lighthouse score of 90 or higher enough?

No. The score fluctuates from run to run,[13] a lab test does not replace measurements on real visitors and cannot measure INP,[14] and automated accessibility checks find only part of the problems.[3]

### Must a template “fully comply with WCAG”?

A template can provide a good foundation: contrast, visible focus, responsive layout. But the outcome depends on your content: texts, colors and images. We cannot verify a seller’s claim of “full compliance” and advise you to go through the key points yourself. If you have legal accessibility requirements, consult a specialist.

### Can I use a template for client sites?

It depends on the license. On ThemeForest the standard license covers one end product,[15] and on Webflow each further client or project needs another license.[16] ShipThemes’ standard licence covers client work: you can build websites for your clients and charge for that work, on as many projects as you need, but not resell the template itself ([licence](https://shipthemes.com/license)). Always read the license text before buying.

### What if the template does not suit me?

For digital goods in the EU, the right to withdraw from a purchase within 14 days is lost if you started the download after expressly agreeing to give up that right.[17] ShipThemes templates are digital downloads, so there are no refunds as standard; if a template is faulty or not as described, we fix it, and if we can’t, you’re entitled to a price reduction or a refund ([refund policy](https://shipthemes.com/refund-policy)).

### Do I need to repeat the check after setting up the template?

Yes, for points 4–7. Contrast and speed depend on your colors, images and scripts, while the template was tested on its own.

## Sources

Pages checked on October 26, 2026.

1. [Astro Docs, Content collections](https://docs.astro.build/en/guides/content-collections/)
2. [MDN, Using CSS custom properties](https://developer.mozilla.org/en-US/docs/Web/CSS/Guides/Cascading_variables/Using_custom_properties)
3. [GOV.UK Accessibility blog, “What we found when we tested tools on the world’s least-accessible webpage”, February 24, 2017](https://accessibility.blog.gov.uk/2017/02/24/what-we-found-when-we-tested-tools-on-the-worlds-least-accessible-webpage/)
4. [WebAIM, The WebAIM Million (2026 report, February 2026 data)](https://webaim.org/projects/million/)
5. [W3C, Understanding SC 1.4.10: Reflow (WCAG 2.2)](https://www.w3.org/WAI/WCAG22/Understanding/reflow)
6. [Chrome for Developers, Simulate mobile devices with device mode](https://developer.chrome.com/docs/devtools/device-mode)
7. [W3C, Understanding SC 2.4.7: Focus Visible (WCAG 2.2)](https://www.w3.org/WAI/WCAG22/Understanding/focus-visible)
8. [WebAIM, Keyboard Accessibility](https://webaim.org/techniques/keyboard/)
9. [W3C, Understanding SC 1.4.3: Contrast (Minimum) (WCAG 2.2)](https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html)
10. [Chrome for Developers, Color contrast in Chrome DevTools](https://developer.chrome.com/docs/devtools/accessibility/contrast)
11. [WAVE Web Accessibility Evaluation Tools (WebAIM)](https://wave.webaim.org/)
12. [Chrome for Developers, Lighthouse overview](https://developer.chrome.com/docs/lighthouse/overview)
13. [Chrome for Developers, How Lighthouse calculates your overall Performance score](https://developer.chrome.com/docs/lighthouse/performance/performance-scoring)
14. [web.dev, Web Vitals](https://web.dev/articles/vitals)
15. [ThemeForest, Licenses](https://themeforest.net/licenses/standard)
16. [Webflow, Template licensing info and guidelines](https://templates.webflow.com/template-licenses)
17. [Your Europe, returning goods bought at a distance](https://europa.eu/youreurope/citizens/consumers/shopping/returns/index_en.htm)
18. [Keep a Changelog, version 1.1.0](https://keepachangelog.com/en/1.1.0/)
19. [Astro Docs, Upgrade Astro](https://docs.astro.build/en/upgrade-astro/)
20. [AGENTS.md, the format’s official site](https://agents.md)
21. [Gloaguen et al., “Evaluating AGENTS.md: Are Repository-Level Context Files Helpful for Coding Agents?”, arXiv, version 3 of September 29, 2026 (preprint, not peer-reviewed)](https://arxiv.org/abs/2602.11988)
