How We Score Website Templates
Template marketplaces list thousands of products and leave buyers to guess at quality from preview screenshots. We built our scoring system to close that gap. Every template in our library gets a Design Score and a Dev Score from multiple team members who independently open the file, test breakpoints, work with the CMS, and assign their own scores. The published score is the averaged result of those independent assessments.
These scores are not algorithmic. They reflect what we would tell a colleague if they asked whether a template is worth buying before a client project.
Who Reviews Your Templates
Every template is scored by the same team of 11 professionals: 6 designers and 5 developers, each with more than ten years of experience building websites. The designers score the Design Score; the developers score the Dev Score. Nobody scores an area outside their discipline. You can read each reviewer's background and evaluation perspective on our review team page.
Within each discipline, every reviewer scores independently. The six design scores are averaged into the published Design Score, and the five dev scores are averaged into the published Dev Score. No single person and no algorithm sets a number alone.
The Design Score
The Design Score measures visual quality on a 0 to 10 scale. We look at typography choices, layout hierarchy, aesthetic consistency, use of whitespace, colour application, and how the visual design holds up across screen sizes.
Typography matters beyond font pairing. We check type scale, line height, heading contrast, and whether body copy stays readable at mobile widths. Layout hierarchy means the eye knows where to go first, second, and third without reading instructions.
Whitespace and colour get the same scrutiny. Cramped sections, inconsistent padding, or decorative colour that fights the content all cost points. Responsive visual design means hero layouts, image crops, and navigation still look intentional on a phone, not just shrunk.
A 9.0 on design usually means cohesive type, deliberate spacing, and a layout that would hold up in a portfolio case study. A 6.0 often means the preview looks fine but spacing breaks down on tablet, or the typography scale feels arbitrary once you scroll past the hero.
The Dev Score
The Dev Score measures build quality on the same 0 to 10 scale. We inspect code structure, HTML and CSS organisation, CMS implementation, responsive breakpoint handling, loading performance, and how well the template is documented for customisation.
Code quality means clean class naming, logical component structure, and no obvious copy-paste bloat. On Webflow, we check whether styles are systematic and interactions are built cleanly. On Framer, we look at variant usage and responsive component behaviour. On Shopify, we review Liquid structure, section schema, and theme settings.
CMS implementation is a major factor. Collections, fields, and dynamic content should match how a real site would be managed, not hard-coded placeholders that fall apart when you add pages.
Breakpoint handling means more than a fluid grid. We resize through standard widths and note where layouts break, overflow, or require manual fixes. Performance and documentation round out the score: heavy assets, unused scripts, and missing setup notes all pull it down.
How the Overall Score Works
The Design Score and the Dev Score are calculated independently, each averaged from its own reviewers. Both numbers are always published separately so you can see the full picture.
The Overall Score is the average of the two: Overall Score = (Design Score + Dev Score) / 2. It is the headline number on every template card, and a template has to reach 7.0 Overall to be published at all.
Because the two axes are scored separately, a template can earn 9.0 on design and 5.5 on dev, and we say so plainly. That split is intentional. A beautiful preview with weak underlying structure is a common trap, and buyers deserve to see both sides before they purchase.
When you browse our template listings, you will see the Overall Score on every card and both the Design Score and Dev Score on each template page. We would rather surface an honest gap than hide it.
What a Score Actually Means
Scores are calibrated against templates we have actually used in client work and side projects. Every template published in our library has an Overall Score of 7.0 or above. The ranges below describe what each band means in practice.
Every template in the library has cleared a minimum quality threshold. We do not publish templates below 7.0 on the Overall Score.
9.0 to 10.0
Exceptional and production-grade. We would use this on a client project with minimal structural changes. Design and build quality are both strong, or one axis is outstanding and the other is clearly above average.
8.0 to 8.9
Strong with minor issues. Suitable for most use cases with minimal setup time. Typography, layout, or CMS structure may need small adjustments, but nothing that signals a structural problem.
7.0 to 7.9
Good with meaningful limitations worth knowing before you buy. You can ship a solid site from it, but expect some time on responsive refinements, CMS cleanup, or visual consistency. We publish these because the core quality justifies the listing, and we call out the specific limitations so you can decide whether the tradeoff works for your project.
Below 7.0
Not listed. Templates that score below 7.0 on the Overall Score are not published in the library, regardless of platform, popularity, or creator reputation. We apply this threshold consistently.
How Selective Is the Library?
Very. We have reviewed more than 10,000 Webflow templates, Framer templates, and Shopify themes, and 1,005 of them are published today: 349 Webflow, 434 Framer, and 222 Shopify. That is under 11% of everything we have reviewed. Every template that did not make it scored below 7.0 Overall.
The threshold is the same for every platform, price, and creator. A free template and a premium one face the same 7.0 floor, and a creator with a large following gets no allowance for it. Scores are what decide inclusion, which is why the library stays small while the number of templates we look at keeps growing.
What We Don't Score
We do not score popularity, sales volume, or creator reputation. A bestselling template on a marketplace can still have weak CMS structure or lazy responsive behaviour. We only evaluate the template itself.
We also do not factor in our relationship with a creator. No one pays for a higher score, and no commercial deal influences the numbers. For more on how we operate, see our about page.
