You open the site on your laptop and it is instant. You open it on your phone on mobile data and stare at a white screen. Lighthouse agrees with your phone. You check the CSS, it is a few kilobytes, and you go looking for a big image that is not there.
What happened on Pigeon’s Mission.
The site was a Claude Design export. Its design system lived in a folder called _ds/: under 5KB of CSS in total, split across eight files. The main styles.css pulled them in with an @import chain.
So the browser made eight extra requests for almost no bytes, and it could not even start most of them until it had read the file that asked for them. Concatenating the eight files into one and inlining it in the head was worth about four seconds of mobile Speed Index.
No image changed. No script changed. The same CSS, delivered in one piece.
Why a tiny file can block the page.
CSS is render-blocking. The browser will not paint anything until it has every stylesheet the page depends on, because painting early and then restyling would be worse. That is the right behavior. It just means every stylesheet sits on the critical path.
An @import inside a stylesheet is invisible until that stylesheet has downloaded and been parsed. Only then does the browser learn there is another file to fetch. If that file imports something else, the browser waits again. Each level is a full round trip to the server.
On a desktop on fiber, a round trip costs almost nothing, so the chain never shows up. On a phone on mobile data, latency is the expensive part of every request, and the payload barely matters. A tiny file and a large one cost nearly the same to start. A chain makes you pay that cost in sequence instead of all at once.
That is why the file size is a red herring. Count the hops.
Splitting a design system into small files is good for the people editing it. Tokens in one file, type in another, components in a third. Keep it that way in the source. Just do not ship the split to the browser.
Where these chains come from.
Almost never from somebody deciding to build one. They arrive with something: a design system export that was split for the people editing it, a theme whose stylesheet imports three more, a font service that hands you a one-line import and sounds like it is doing you a favour.
| Where the CSS came from | How it usually arrives | What to ship instead |
|---|---|---|
| A design system exported as separate files | An @import chain inside styles.css | Concatenate at build time, and inline the result while it is small |
| A theme or template you bought | A few link tags, with imports hidden inside them | Keep the link tags, flatten the imports. Parallel is fine, sequential is not |
| A web font service | An @import at the top of your stylesheet | Self-host as WOFF2 and preload it from the head |
| A component library | One large stylesheet for the whole library | Ship it as one request. One big file beats nine small ones on a phone |
| A page-specific stylesheet | A link tag in the head of that page | Nothing to fix. The browser finds every link tag at once |
The pattern worth noticing: every row that needs fixing is a file that learns about another file. Every row that is fine is a file the HTML already knew about.
The thirty-second check.
Open the network panel, filter to CSS, reload with the cache disabled, and look at the left edge of the bars. If every stylesheet starts at roughly the same moment, you have no chain. If each one starts where the last one finished, you are looking at a staircase and the fix is in this piece.
Lighthouse will also name it for you under the critical request chain audit, which reports the longest chain on the page. That number is the one to drive down, and it is not the same thing as the number of requests.
How to find it and fix it.
Lighthouse lists it under the critical request chain audit, and the network panel shows it as a staircase: one request, then a gap, then the next. If your stylesheets start one after another instead of together, you have a chain.
- No
@importin any shipped stylesheet. Concatenate at build time, or link each file from the head so the browser finds them all at once. - Small critical CSS inlined in the head. Under a few kilobytes, a separate request costs more than the bytes it saves.
- Fonts loaded from the head as self-hosted WOFF2, not from an import buried in a design system file.
- Measured on a phone on mobile data, before and after. The chain does not exist on your desk.
This is section 10 of the 5Four Launch Checklist, and it now gets checked on every Claude Design export before it ships. It sits next to the rest of the Core Web Vitals work, because a white screen is a loading problem before it is anything else.
Related: design system in the glossary, Core Web Vitals in the glossary, the Site System.



