Roughly a third of the design work we love internally never reaches the client. We kill it before it leaves the studio. This is not a quality control problem. It is the quality control system.

The first cut: directional review

Every project has an internal review at the end of the first design week. The team presents three to five directions. The studio principal asks one question: which of these is the strongest position for the company we’re working with? The other directions die.

This sounds harsh. It is. Designers are emotionally invested in directions they’ve spent a week on. The cull is hard. But sending three directions to a client and letting them pick is not a service — it is offloading the studio’s expertise back to the founder, who hired us specifically because they did not have the expertise to make that call.

The second cut: production review

By week four we have a fully-built brand system: typography, color, lockups, motion, applied across mock surfaces. The studio principal sits with the team and asks: would I send this in five years and feel proud? If the answer is qualified — “yes, with some tweaks,” “yes, mostly” — we go back another week.

Roughly a third of week four reviews fail this test. The cost is real. The studio loses a week of margin on the project. The team loses a week of energy. But the alternative — shipping work that is “almost there” — costs the client a brand they will need to redo in eighteen months. We carry the cost so they don’t have to.

What the cull rate produces

The work that survives both cuts is the work the team is unambiguously proud to ship. There is no “I would have wanted to push this further.” There is no “I think this is what they wanted, even though I wasn’t sure.” The work has been beaten on internally for two and a half weeks before the client sees it. By the time it arrives, it is done.

وب وایتال‌ها یک تحویل‌دادنی هستند، نه یک کار بعد از طراحی

بزرگ‌ترین دلیل کند بودن سایت‌ها، تصمیم‌های طراحی بدون محدودیت عملکرد است

بزرگ‌ترین عامل کندی سایت‌ها، تصمیم‌های طراحی‌ای هستند که بدون درنظر گرفتن محدودیت‌های عملکرد گرفته می‌شوند. ویدئوی هیرویی که هیچ‌کس به آن ایراد نگرفت. ست فونتی با هفت وزن مختلف. لندینگ‌پیجی با سی بخش و یک تصویر پارالاکس برای هر بخش.

هر تصمیم، دویست میلی‌ثانیه اضافه می‌کند. تا زمانی که سایت به مرحلهٔ تولید برسد، صفحه پنج ثانیه هزینه دارد.

محدودیت، خودِ طراحی است

ما LCP، CLS و INP را به‌عنوان محدودیت‌های طراحی درنظر می‌گیریم — نه مشکلاتی که تیم فنی باید بعداً اصلاح کند. یعنی: قبل از اینکه طرح را به تیم توسعه تحویل بدهیم، دقیقاً می‌دانیم:

• عنصر LCP چیست

• وزنش چقدر است

• و بودجهٔ عملکرد برای بقیهٔ صفحه چقدر است

این کار خسته‌کننده به‌نظر می‌رسد. واقعاً هم خسته‌کننده است. اما همین دلیل است که سایت‌های ما

روز اول لانچ، هر سه Web Vital را سبز تحویل می‌دهند  نه اینکه بعد از لانچ، شش هفته زمان برای بهینه‌سازی لازم باشد.

جایگزین‌هایی که از همان ابتدا انجام می‌دهیم

• ویدئوی هیرو → WebP متحرک با یک‌دهم حجم، همراه با یک تصویر پوستر به‌عنوان LCP

• انیمیشن ۶۰ فریم → انیمیشن CSS که به prefers-reduced-motion احترام می‌گذارد

• فونت با وزن‌های 100 تا 900 → فونت متغیر با دو محور وزن

• بخش‌های تصویری سنگین → تصاویر بالای صفحه preload، تصاویر پایین صفحه lazy-load با قابلیت بومی مرورگر

چرا این موضوع فراتر از Lighthouse اهمیت دارد

اهمیت این موضوع فقط این نیست که گوگل سایت‌های سریع را در جستجو بهتر نمایش می‌دهد — این کار را می‌کند، اما دلیل مهم‌تر این است که سایت‌های سریع تبدیل می‌کنند.

لندینگ‌پیجی که سه ثانیه طول می‌کشد تا قابل تعامل شود، ۳۰٪ از ترافیک موبایل را قبل از اینکه کاربر حتی یک تصمیم دربارهٔ برند بگیرد، از دست می‌دهد.

زیباترین صفحهٔ طراحی‌شده اگر کند باشد، دیگر یک صفحهٔ زیبا نیست.

یک صفحهٔ کند است که هیچ‌کس آن را ندید.

Web Vitals are a deliverable, not an afterthought

The single largest cause of slow websites is design choices made without performance constraints in the room. The hero

video that nobody flagged. The custom font set with seven weights. The thirty-section landing page with a parallax background image per section. Each decision adds two hundred milliseconds. By production, the page costs five seconds.

The constraint is the design

We treat Largest Contentful Paint, Cumulative Layout Shift, and Interaction to Next Paint as design constraints  not engineering remediations. That means: before we ship a design to the build team, we know what the LCP element will be, what its weight is, and what the budget is for everything else.

This sounds tedious. It is tedious. It is also the reason our shipped sites land in green for all three Core Web Vitals on launch day, instead of needing a six-week post-launch optimization sprint.

The substitutions we make on the way in

Hero video → animated WebP at 1/10 the file size, with a poster image as the LCP element. Sixty-fps motion → CSS-driven animation that respects prefers-reduced-motion. Font weight 100, 200, 300, 400, 500, 600, 700, 800, 900 → variable font axis with two ranges defined. Image-heavy editorial sections → above-the-fold images preloaded, below-the-fold lazy-loaded with native browser support, no external library required.

Why this matters beyond Lighthouse

The reason this matters is not that Google rewards fast sites in search. It does, but the bigger reason is that fast sites convert. A landing page that takes three seconds to interact loses 30% of mobile traffic before a single brand decision is made. The most beautifully designed page that is too slow to use is not a beautifully designed page. It is a slow page that nobody saw.

Enfold Studio is eight years old this quarter. The four of us came from forty studio engagements between us before we started the company. Some were our own studios. Most were as senior designers, art directors, and creative directors at larger places. Here is what we took away that shaped the studio we built.

The agencies were too big

Three of us came from agencies between fifty and two hundred people. The work was often excellent. The conditions for making it were never excellent. By the time a junior designer’s idea reached the client, it had passed through four senior reviews, two account managers, and a creative director’s preference. It was no longer the junior’s idea.

The studios we worked at before that — three to ten people each — produced more direct work. The principal who pitched it made it. The author of the idea defended the idea. There was no committee.

The freelancers were too lonely

One of us spent four years freelancing between studio jobs. The work was the most personal of any period in their career. It was also the most uneven. Every project relied on the freelancer’s mood that week. There was no second person to push back. The work was good when it was good and lifeless when it wasn’t.

A studio with three to seven creatives is the structure that gets the directness of the freelancer with the quality control of the agency. That is what we tried to build.

The thing none of us learned in advance

How much of running a studio is not design. The first two years were a slow lesson in contracts, scope language, payment terms, project management, hiring, performance review, financial planning. The four of us were excellent designers. We were terrible business owners. We bought books, took classes, hired a fractional COO, made expensive mistakes, and slowly got better.

The one piece of advice we wish someone had given us before we started: design your studio operations as carefully as you design your client work. The clarity you bring to brand systems is the same clarity that will keep your studio alive in year five.