How to Win an Awwwards Site of the Day (Jury Guide)

Every creative developer I know has the same screenshot folder: dozens of Awwwards Sites of the Day they wish they'd built. So the question I get asked most often is some version of how to win an Awwwards — and the answer is rarely what people expect. It's not a wilder WebGL effect or a longer loader. It's a clear concept, ruthless usability, and technical polish that holds up when 18 strangers open your site on whatever device is in front of them. This is the guide I wish I'd had: how the scoring actually works, what jurors reward versus quietly penalize, and how to scope a build that can realistically take an Awwwards Site of the Day.

I write this from the panel, not the sidelines. I'm Hon Tran — a creative developer and Awwwards jury member, the first Vietnamese developer to win an international web award, with 9 Awwwards Sites of the Day, 8 Awwwards Developer Awards, 9 FWA of the Day, and two Independent of the Year titles. What follows is how I actually score, and how the panel around me scores.

How Awwwards judging actually works

When you submit a live URL and it's approved, it goes to a jury of at least 18 members who score it independently across four weighted criteria. The system then drops the three scores furthest from the average to kill outliers, and voting runs for about five days. These are the Awwwards judging criteria:

Criterion	Weight	What a juror is actually checking
Design	40%	Typography, layout, color, composition — the art direction
Usability	30%	Navigation, clarity, speed, "can a stranger use this"
Creativity	20%	Originality of concept and execution
Content	10%	Quality and relevance of the work shown

A score of 6.5+ earns an Honorable Mention; the single highest-scoring site of the day takes Site of the Day. Then there's a second pass most people miss: every SOTD winner is sent to the developer jury, scored against the Development Guidelines, and anything above 7 earns a Developer Award — recognizing technical excellence, accessibility, and code quality on top of the design win. (See the official Awwwards evaluation system and Developer Award pages.)

The non-obvious takeaway: Design + Usability is 70% of your score. Newcomers pour everything into Creativity — the 20% slice — and starve the fundamentals. I've scored gorgeous, inventive sites a full point lower than they "deserved" purely because they were slow or confusing. Build the floor before you build the ceiling.

What jurors reward

When I open a submission, a handful of things move my score up fast — and they're consistent across the jurors I compare notes with.

• Original art direction. A site with a point of view, not a moodboard of this year's trends. The fastest way to lose Creativity points is to ship the same horizontal-scroll gallery everyone shipped.
• Directed motion. Animation that guides the eye and paces the story — a pinned scroll sequence, a considered page transition, one signature moment. Motion should mean something.
• A loading experience that respects me. A two-second branded reveal that sets a tone is craft. A six-second progress bar is a usability penalty wearing a costume.
• Flawless responsiveness. I score on real devices. A site that's as considered on a phone as on a 27-inch display reads as professional maturity.
• Content that's actually good. Real copy, real case studies, real imagery. Lorem-ipsum energy shows, even at 10% weight.

If you want the full build-side playbook behind these, I break it down in how to build an award-winning portfolio site.

What jurors penalize

The penalties are more predictable than the rewards, which is good news — most of them are avoidable.

• Random effects. Motion with no hierarchy: everything floats, parallaxes, and reveals, so nothing matters. This is the single most common reason a creative site scores like an average one.
• Jank. A WebGL hero that drops to 20fps reads as broken, no matter how beautiful the still frame. I'll come back to this — it's where most ambitious sites lose the award.
• Broken mobile. A desktop masterpiece with a collapsed phone layout caps at an Honorable Mention. There is no "desktop-only" excuse anymore.
• Derivative concepts. Borrowing the trend of the moment tanks Creativity directly.
• No accessibility floor. Missing focus states, no reduced-motion path, low contrast, a custom cursor that hides the real one — small things a juror reads as carelessness.

The unglamorous part: technical polish wins or loses it

Here's the truth nobody puts on the moodboard. The difference between an Honorable Mention and a Site of the Day is almost never raw creativity — it's polish. And polish is mostly performance and parity.

60fps on real devices. I don't score on a maxed-out workstation; I open sites on a laptop and a mid-range phone, like a real PRO user would. Animate transform and opacity only — they stay off the layout/paint path — and never animate width, top, or box-shadow on scroll. The fastest way to feel the difference is to run one clock for the whole site instead of three competing requestAnimationFrame loops:

import Lenis from "lenis";
import gsap from "gsap";
import { ScrollTrigger } from "gsap/ScrollTrigger";

gsap.registerPlugin(ScrollTrigger);
const lenis = new Lenis({ duration: 1.1, smoothWheel: true });

// One ticker drives smooth scroll, DOM tweens, and shader uniforms together
lenis.on("scroll", ScrollTrigger.update);
gsap.ticker.add((time) => lenis.raf(time * 1000));
gsap.ticker.lagSmoothing(0);

Mobile parity. Cap the device pixel ratio so you're not rendering at 3x on a phone for no visible gain, and pause off-screen WebGL:

renderer.setPixelRatio(Math.min(window.devicePixelRatio, 2));

Reduced motion. Gate decorative animation behind the user's preference. It's an accessibility win and a usability signal — and it directly feeds the Developer Award:

const reduced = window.matchMedia("(prefers-reduced-motion: reduce)").matches;
if (!reduced) initScrollAnimations();

Fast TTFB and LCP. A slow first paint colors a juror's entire impression before the design even loads. Aim for an LCP under 2.5s even with the motion — ship less JS, dynamic-import the heavy WebGL modules, and stream the first view. I go deep on this exact tension in Core Web Vitals for animation-heavy sites, and you can verify the targets against web.dev's Core Web Vitals.

This is the work that earns the Developer Award specifically: SOTD winners that also nail accessibility, performance, and clean code are the ones that score above 7 with the developer jury. If you want to win an Awwwards Developer Award, treat the technical layer as a design surface, not a chore.

Is it worth it? An honest cost-benefit

Let me be candid, because the awards industry rarely is. Chasing a Site of the Day adds real time to a build — typically a polish-and-QA phase of one to two extra weeks on top of the design and motion work, almost all of it spent on performance, cross-device testing, and accessibility. That's not free.

So is it worth it? It depends on why you want it:

• For a portfolio or studio brand — yes. A Site of the Day is a permanent, third-party-verified credibility signal. It opens client conversations that cold outreach never will. My own awards are the reason a chunk of my clients found me.
• For a client project — sometimes. If the brand benefits from being seen as cutting-edge (fashion, agencies, product launches), the award is a marketing asset. For a lead-gen brochure site, the budget is better spent elsewhere.
• For learning — always. Building to the Awwwards bar forces a level of craft that makes every subsequent project better, award or not.

How to scope an award-ambition build

If you decide it's worth it, scope it honestly from day one — retrofitting "award quality" onto a finished build never works.

1. Concept first. One sentence that makes the art direction inevitable. If you can't say it, the jury won't feel it.
2. Design the signature moment — the one interaction people screenshot — and protect the rest of the site's performance budget around it.
3. Build with a performance budget, not a performance afterthought. Measure on a real mid-range phone weekly, not the day before submission.
4. Reserve a dedicated polish week for 60fps, mobile parity, reduced motion, focus states, and TTFB. This week is where Honorable Mentions become Sites of the Day.
5. Submit a flawless, live production build early in the week so your five-day voting window gets full traffic — and never deploy changes mid-vote.

For a feel of what this level looks like shipped, the By-Kin award-winning website case study and the Iventions events website case study both walk through the concept-to-craft path on real projects. And if you're curious what consistency at this level requires over time, here's what winning Awwwards Independent of the Year twice actually took.

FAQ

How long does the Awwwards voting period last?

Around five days. Once your live site is approved it goes to a minimum of 18 jurors who score it independently across Design, Usability, Creativity, and Content, with the three most extreme scores dropped automatically.

Do I need WebGL or 3D to win a Site of the Day?

No. Plenty of SOTDs are pure CSS and GSAP with exceptional typography and directed motion. WebGL helps on the Creativity axis, but only if it serves the concept and holds 60fps. A flawless 2D site beats a janky 3D one every time I score.

What's the difference between an Honorable Mention and Site of the Day?

Same jury vote. A score of 6.5+ earns an Honorable Mention; the single highest-scoring site that day takes Site of the Day. The gap is almost always usability and performance polish, not creativity.

How do you win an Awwwards Developer Award?

You can't apply for it directly — every Site of the Day is automatically sent to the developer jury and scored against the Development Guidelines. Score above 7 on technical execution, accessibility, performance, and code quality and you earn the Developer Award on top of the SOTD.

Want to build one?

Building to the Awwwards bar is a real investment of craft and time — directed motion, WebGL, and the unglamorous performance work that actually wins the score. If you'd rather commission a site engineered to compete for a Site of the Day, that's exactly what I do for studios and brands. Browse shipped, awarded work in the projects archive, and let's talk about what you're building.

---

Written by Hon Tran — creative developer and Awwwards jury member, with 9 Awwwards Sites of the Day, 8 Developer Awards, 9 FWA of the Day, and two Awwwards Independent of the Year titles. hontran.dev