TLDR: My CDP audit came back with zero overflow across all seven routes. The dt labels in my pricing value-stack were still rendering at 14px — one word per line. Numbers lie by omission.

The Setup

I'm deep in my site rebuild and I want to ship knowing the mobile experience is actually tight.

So I ran a real audit.

CDP (Chrome DevTools Protocol, the browser's built-in automation API) at 390×844, dpr2, touch. All seven routes. Full-page captures, PIL (Python's image library) slicing to examine sections, per-page horizontal-overflow probe on every one.

The number came back clean.

Zero overflow. Everywhere.

I was this close to calling it done.

The Wall

Something made me actually open the screenshots.

On the /work page — the page that's supposed to convince someone to hire me — the Hormozi-style value-stack was a mess.

The dt elements (dt and dd are the label and value in an HTML definition list) were collapsing to 14px. "Me & my agents" was rendering one word per line. The label column was a sliver.

Not broken enough to overflow. Just broken enough to look like I don't know what I'm doing.

What Happened

The layout was a simple 1fr auto grid.

The dd (value column) used --type-2xl — big, heavy type. In the auto track, it claimed all the width it needed. The dt got what was left: 1fr of basically nothing.

On a 390px screen, basically nothing resolves to 14px.

The overflow probe never cared. The row didn't overflow — it collapsed. The text wrapped. The numbers said "fine." The page said something else entirely.

The Fix

Stack it under the existing 40rem breakpoint.

Below 40rem, the layout goes single-column. The dd gets text-align: right and the whole thing reads receipt-style: label flush left, price flush right.

Two rules. One commit.

Why This Matters to Me

I had internalized the wrong finish line.

"Zero overflow" felt like done. It isn't. Overflow is one axis — horizontal spillage. Font starvation, column collapse, content wrapping into nonsense — that's a whole other class of visual failure, and no numeric probe catches it.

(I've paid a similar tax before, on a different project — a misplaced font-size on html instead of body wrecked a whole layout and took me 12 commits to trace back to one line. The lesson should've been obvious by then.)

The real audit is: run the numbers, then open the screenshots, then ask if what you see would make a potential client trust you with their business.

On that second pass, the pricing section answered that question pretty clearly.

Measure everything. Then look.