Most websites are too big. Not too detailed, not too ambitious — too big. They hold pages that were added to satisfy a meeting, pages nobody has read since launch, pages whose only job is to make a navigation bar look substantial. The site grew because adding a page is easy and removing one feels like a loss.
We think the loss runs the other way. Every page you publish is a page you have to maintain, a page that can go stale, a page that dilutes the few that matter. A site with five good pages says more than a site with thirty average ones, because the reader can hold five pages in their head. They cannot hold thirty.
The page count is a design decision
When a client asks for a website, they usually arrive with a sitemap already in mind: Home, About, Services, Portfolio, Team, Blog, Testimonials, FAQ, Contact. It reads like a checklist of what a website is supposed to have. But that list was never designed. It was inherited. Nobody sat down and decided that this particular business, with this particular thing to say, needed exactly those nine pages.
So that is the first thing we do. We ask what the site is for — the one outcome that matters — and we count backwards from it. A photographer needs to show work and be hireable. A music teacher needs to be found and booked. Almost everything else is a page that exists because other sites have it.
Fewer pages, faster site
There is a practical argument too. Fewer pages means less to build, less to test, less to break, and less to load. A site that ships as a handful of static documents is fast in a way that no amount of optimization can fake. There is no framework booting up, no waterfall of requests, no layout shifting under the reader as things arrive. The page is just there.
This is not nostalgia for the old web. It is a recognition that most of what slows a site down is weight the site did not need in the first place — and a lot of that weight is pages. Cut the pages and the performance problem mostly solves itself.
What “fewer” is not
Fewer pages is not the same as less content. A single well-built page can carry a long essay, a detailed case study, a full argument. We are not asking anyone to say less. We are asking them to stop spreading what they have across rooms the reader has to walk between.
And fewer is not a fixed number. A documentation site needs many pages; that is its nature. A studio’s front page does not. The discipline is not “five pages always.” It is “no page that does not earn its place.”
The test
Here is the test we use. For every page, ask: if this were gone, what would the reader miss? If the honest answer is nothing — if the page exists to look complete, or because the template had a slot for it — the page goes. If the answer is something real, the page stays and we make it good.
Run that test on most websites and they get smaller. Run it on a good website and almost nothing moves, because the pages were chosen, not collected.
That is the whole case. Build the smallest site that does the job. It will be faster, it will be easier to keep, and it will say more — because the reader can actually see all of it.