How I build
Most local business websites fail for the same three reasons: they are slow, they are invisible on Google, and they never ask for the appointment. Everything about how I build exists to fix those three.
Performance standards
Google measures how fast your page shows its main content, a metric called LCP, and it ranks slow sites lower because people leave them. Speed is not a technical vanity number. It is whether the visitor is still there when your phone number appears. These are the targets every site I ship has to meet:
LCP
main content visible
CLS
layout never jumps
INP
instant response to taps
- Main content visible in under 2 seconds on a phone
- Lighthouse scores of 95 or higher for performance, accessibility, best practices and SEO
- A stable layout that never jumps while loading
- Instant response to taps and clicks
The stack
I build on the same foundation used by some of the fastest sites on the web. What matters is what each piece buys your business:
- Next.js
- The site is generated in advance, so it loads fast and has no plugins to break or patch.
- Vercel
- Served from a global network with automatic scaling. Your site does not go down on a busy day.
- TypeScript
- A stricter way of writing code that catches errors before they ever reach your visitors.
- Tailwind
- A disciplined design system, so every page stays consistent as the site grows.
Accessibility
Every site I build meets WCAG 2.1 AA, the accessibility standard referenced in most US lawsuits over inaccessible websites. That matters twice. About one in four American adults lives with a disability, so accessibility is market reach. And an accessible site is a smaller legal target. For medical practices this is not optional.
How I approach SEO
No tricks, no shortcuts that burn a domain. SEO that lasts is structural:
- Structured data that tells Google exactly who you are, what you do and where you serve
- An internal link architecture where every page reinforces the others
- Content written for what your customers actually search, not for what sounds good
- A Google Business Profile that matches your site, so you show up on the map
The process
Discovery and architectureweek 1
What the business needs the site to do, and the structure that gets it there.
Designweeks 1 to 2
A design plan approved before any page gets built. No surprises.
Buildweeks 2 to 4
The site itself, tested on real phones against the performance targets above.
Content and SEOin parallel
Copy, metadata and structured data, in both languages when the project is bilingual.
Launch and supportlaunch week
Domain, analytics and search registration, plus 30 days of included fixes.
What I don't do
- No recycled templates. Your business is not a theme with the logo swapped.
- No slow page builders weighed down by plugins.
- No sites you cannot update. You get a site your business can live with.
- No SEO tricks that trade next month's ranking for this month's report.
If any of that is what you are looking for, I am not the right fit, and that is fine. It saves us both time.