Before I touch a client's website, I run a test that takes ten seconds and tells me almost everything I need to know.
I open the homepage on my phone, the way most people actually see it. I give myself a slow count of ten. Then I close my eyes and ask three questions: What does this business do? Who is it for? What am I supposed to do next?
If I can't answer all three, the site has a problem that no amount of new content, better photos, or clever copy will fix on its own. And this year, working on sites across the Hill Country and beyond, I've seen that test fail more often than it passes, even on sites that look expensive.
The test isn't about design
A homepage can be visually polished and still fail the ten-second test. I've opened sites with a beautiful photo, a tasteful font, and a headline that says something like "Excellence in Service Since 1998." It tells me nothing. Not what the business does. Not who it's for. Not what I do next.
The opposite happens too. A site can look plain, even a little dated, and still pass, because the words at the top are doing their job: naming the service, naming the customer, and pointing at one action.
That's the part people miss. The test is a copy and priority problem before it's ever a design problem. You can hire the best designer in Texas and still fail it if the homepage is trying to say twelve things at once.
Why sites end up saying twelve things at once
Nobody sits down and decides to confuse visitors. It happens gradually, and it happens for a reasonable-sounding reason every time.
The site launches with one clear message. Then a new service gets added, so a line goes in the hero. Then a board member wants the mission statement up top. Then someone points out the site doesn't mention the second location, so that gets added too. Each addition is defensible on its own. The problem is nobody ever goes back and asks what the page is supposed to accomplish now, with all of it stacked together.
I see the same pattern in the navigation bar. A menu with nine items isn't a menu, it's a decision the business is asking a stranger to make in the first three seconds of a visit, before that stranger has any reason to care. Every extra item is a small tax on attention, and attention is the one thing you can't get back once you've spent it.
What "one job per page" actually means
Here's the structural fix, and it's the same one I use for content calendars and client approval pages: give each page exactly one job.
A homepage's job is not to explain the whole business. Its job is to get the right visitor to the right next page, fast. That might be a services page, a booking link, or a contact form, but it's one thing, stated once, in words a stranger who has never heard of you would understand on first read.
Try this on your own site right now. Open it on your phone. Cover the screen after ten seconds. Ask the three questions. If you hesitate on any of them, that's not a content problem, it's a structure problem, and it's usually fixable by removing far more than you add. Cutting a homepage down to one message is almost always faster and cheaper than writing a new one from scratch.
This is also why a redesign is often the wrong first move. If the underlying photos, brand colors, and voice are fine, and the problem is that the page is trying to do six jobs, you don't need a new site. You need someone to sit down and decide, in writing, what the one job is, then cut everything that isn't in service of it.
Where this shows up in my own work now
I've spent enough time inside other people's homepages this year that fixing this specific problem, the twelve-things-at-once homepage, has become its own piece of what I do. Sometimes that's a smaller fix: rewriting and reordering an existing page so it passes the ten-second test. Sometimes it's building the one page a business actually needs, with a single job, from the ground up. Either way, the diagnosis comes first. I don't touch anything until I know what the page is for.
If you want a second set of eyes on whether your own site passes that test, that's a short conversation, not a long one.
Call to action
If your homepage failed the ten-second test just now, I'd like to hear what got in the way. Get in touch.