Your FQHC Website Is a Front Desk—Is It Open?
- Wickersham Team
- Jun 11
- 5 min read
We've mentioned this before. We run a test with almost every FQHC we work with. We pull up their website on a mobile phone, not our own phone, but one we have never used before, and we set a timer for 60 seconds.
The question is simple: can a patient who has never heard of this organization figure out how to get care before the timer runs out?
Most sites fail.
Not because the information isn't there. It usually is, somewhere. But somewhere is not good enough when the person looking in is managing a health concern, limited time, limited data, and real uncertainty about whether they will be turned away at the door.
This piece is about what that failure actually costs and what the fix looks like in practice.
Your website is not a brochure
Most FQHC websites were built to communicate organizational identity. They tell the story of the mission, the history, the breadth of services, the awards and accreditations. They are designed with the same instincts that produce annual reports and grant applications, documents that speak to funders, partners and boards.
The patients arriving at the website are a different audience entirely. They are not evaluating the organization. They are trying to access it. They have a specific, urgent, practical question and they need an answer in the next two minutes or they will look somewhere else or give up entirely.
This is not a content problem. It is a design problem. And the distinction matters because the solutions are different.
A content problem is solved by writing better copy. An access design problem is solved by restructuring what appears first, what is findable in three taps, what is written in plain language without healthcare jargon and what happens when someone arrives on a phone with a slow connection and forty seconds of patience.
The five questions every FQHC homepage must answer
Through our work with community health centers, we have identified five questions that every FQHC website must answer immediately, not after clicking, not after scrolling, not after reading three paragraphs of organizational history.
01—Can I be seen here?
This means eligibility must be surfaced immediately, not hidden behind a "Services" dropdown or described in clinical language that assumes prior healthcare knowledge. A clear, plain-language statement should tell a patient, before they do anything else, whether this is a place where they can receive care regardless of insurance status or ability to pay.
02—How do I get started?
A single, obvious next step. Not four options of equal visual weight. Not a phone number buried in the footer. One clear pathway, whether that is calling, scheduling online, or walking in, that does not require the patient to figure out which option applies to them.
03—What do I need to bring or know?
First-time patients arrive with anxiety about the unknown. What will they ask me? What if I don't have insurance? What if I can't pay? Addressing these questions directly, before the patient has to ask them, reduces the friction that turns an intention to seek care into a closed browser tab.
04—Where do I go or whom do I contact?
Location information should be immediate and specific. Include hours, address, phone number, and directions on every page, not just the "Locations" tab. If you operate multiple sites, provide a clear way to find the right one without navigating three levels of the menu.
05—What happens next?
Setting expectations before the first visit is one of the highest-leverage things a website can do. What does the intake process look like? How long will the visit take? Will there be a cost? What happens if the patient doesn't speak English? Patients who know what to expect show up. Patients who don't often don't.
The mobile reality
We cannot have this conversation without naming the channel that most FQHC patients use to access this information.
According to Pew Research Center's most recent data, one in four low-income Americans relies on a smartphone as their primary or only means of accessing the internet. For uninsured and Medicaid-enrolled populations, the core patient population of most FQHCs, mobile is not a secondary channel. It is the channel.
This has specific implications for website design that go beyond making sure the site "looks okay" on a phone:
Load speed matters. A page that takes more than three seconds to load on a slow mobile connection will be abandoned by a significant portion of users before it finishes loading. Every unnecessary image, video autoplay, and third-party tracking script adds to that load time.
Navigation must work with one thumb. Drop-down menus, small touch targets, and multi-level navigation structures that work fine with a mouse are barriers on a phone. The most important actions, Get Care, Call Us, and Find a Location, should be reachable in one tap from the homepage.
Text must be readable without zooming. A minimum body text size of 16px is not a design preference. It is an accessibility requirement and a usability baseline.
Forms must be minimal. If your new patient intake begins with a twelve-field form, a significant number of mobile users will abandon it. Every field is friction. Every required field that isn't absolutely necessary is a patient you may not see.
What the fix actually looks like
We want to be honest about something: fixing an access design problem on a website is not a small project. It often requires restructuring navigation, rewriting content in plain language, rebuilding the homepage hierarchy, and optimizing for mobile performance. For organizations with limited internal capacity, it is a significant undertaking.
But the starting point is not the full project. The starting point is the 60-Second Test.
Run it today. Give the phone to someone who has never seen your site, a family member, a colleague from another department, anyone who will engage with it as a genuine first-time visitor. Watch where they hesitate. Note which questions they cannot answer. That hesitation point is your most important piece of user research, and it costs nothing to gather.
The patients who close the tab without getting an answer are not telling you anything. They are simply gone. The 60-Second Test lets you see what they saw before they left.
A note on governance
One pattern we consistently see in organizations with this problem is that no single person owns the website's access function. The clinical team owns the services content. The communications team owns the brand story. The IT team owns the technical infrastructure. And the patient experience of finding out whether they can be seen here falls through the gap between all three.
Website access clarity is not a design project with a beginning and an end. It is an ongoing operational responsibility that requires someone to own it, review it regularly, and update it when access conditions change. When capacity is limited, the website should say so. When a program's eligibility requirements change, the website should reflect that before patients arrive expecting something different.
The fix is not just technical. It is governance.
Where to go from here
If you want to go deeper into this topic, the FQHC Marketing Field Guide covers the website as a digital front desk in full, including a diagnostic checklist, the homepage priority test, and a framework for evaluating whether your site is functioning as access infrastructure or just as a marketing artifact.
If your organization is facing this challenge and you want to talk through what it looks like in your specific context, you can reach us at hello@wickershamgroup.com.
