Website Development
A build framework spanning discovery, UX/UI design and development on Astro and WordPress — engineered so every site launches fast, accessible and ready to rank, instead of retrofitted later.
0
Avg. Lighthouse performance score0
Avg. accessibility score0
Avg. page load timeProject Overview
Every build starts from the same question: what does this business actually need the site to do, and for whom? The answer decides the stack — Astro for projects like Expandify Real Estate, where performance and full control over every line of markup matter most, or WordPress for clients like Miled Andos and Cosmedent, who need to manage their own content day to day.
What doesn't change between them is the standard: fast by default, accessible by default, and technically ready to rank the day it launches — not a set of fixes scheduled for after the site is already live.
At a glance
- TypeStandard web development framework
- Stack choiceAstro or WordPress, by project need
- Design toolFigma, built to a component system
- BaselinePerformance, SEO & accessibility at launch
Design and Development, End to End
I run every project from the first discovery call through launch — discovery, UX strategy, UI design and the production code itself — so nothing is lost translating a design file into a working site.
- Lead discovery and translate business goals into a sitemap and UX strategy before any design starts.
- Design UI systems in Figma, then build and ship them as production code myself.
- Build performance-first sites in Astro, and CMS-managed sites in WordPress, depending on the client's needs.
- Own Core Web Vitals, technical SEO and accessibility as part of the build, not a follow-up pass.
- Test and refine every layout across real devices before launch.
Understanding the Business Before Opening Figma
Every project starts with stakeholder conversations, a review of competitor sites, and a full content audit of anything that already exists, so the sitemap that follows is based on what the business actually needs, not a generic template structure.
0
Stakeholder & competitor sites reviewed0
Sitemap agreed before design begins0
Projects start with a content auditStructure Agreed Before a Single Pixel Is Styled
Core user journeys — an investor inquiry, a service booking, a treatment lookup — get mapped and wireframed at low fidelity first, so the information architecture is settled before color, imagery or type can distract from whether the flow actually works.
0
Core user flows mapped per project0
Wireframe review rounds before UI design0
Structure signed off before visual designA Design System, Not a Set of One-Off Pages
Colors, type scale and components are defined once in Figma as a reusable system, with contrast and touch-target sizing checked against WCAG from the first draft — not corrected after a client or a user flags it post-launch.
0
Design system built per project0
Components meet WCAG contrast in design0
Minimum text contrast ratio enforcedBuilding Straight From the Approved System
Production code follows the approved design system directly, with shared components for buttons, cards and sections reused across every page instead of rebuilt one at a time — version controlled from the very first commit.
0
Design system implemented 1:1 in code0
Components reused, not rebuilt per page0
Git-versioned codebase per projectFor When Performance and Control Matter Most
Marketing and performance-critical sites are built in Astro: static-first rendering with an islands architecture, so the handful of components that actually need interactivity ship JavaScript and everything else doesn't.
0
Avg. Lighthouse performance score0
Avg. Time to Interactive0
Static-first pages, JS only where neededFor When the Client Needs to Own the Content
Clients who need to publish and update their own content run on a lightweight custom theme instead of a bloated page builder, with only the plugins the site actually needs and a content model the client's own team can use without breaking the design.
0
Avg. unused plugins removed per rebuild0
Lightweight custom theme, not a page builder0
Editable by the client without breaking layoutFast at Launch, on Either Stack
Compressed and lazy-loaded images, deferred non-critical scripts, caching and a CDN in front of every site — Core Web Vitals are treated as a launch requirement, not a metric to revisit once something feels slow.
0
Avg. Lighthouse score across both stacks0
Avg. page load time0
Sites pass Core Web Vitals at launchThe Technical Foundation Ships With the Site
Clean URLs, complete meta tags, schema markup and a submitted XML sitemap are part of the build itself, so search visibility work can start the day after launch instead of waiting on a second technical pass.
0
Sites launch with schema markup0
Sites launch with a submitted sitemap0
Sites pass a technical SEO audit at launchWCAG 2.1 AA as the Baseline, Not an Add-On
Semantic HTML, full keyboard navigation, visible focus states, sufficient color contrast, meaningful alt text and ARIA labeling where semantics alone aren't enough — plus reduced-motion support for the users who ask for it.
0
Avg. accessibility score0
Interactive elements keyboard-navigableTested on Real Devices, Not Just a Resized Window
Layouts are designed mobile-first and verified across real phones and tablets, not just a resized browser window, with touch targets, tap spacing and font scaling checked at every core breakpoint before launch.
0
Core breakpoints designed for0
Layouts tested on real devices0
Minimum touch target sizeThe Work Doesn't Stop at Launch
Core Web Vitals are monitored on an ongoing basis after launch, with regressions from new content, plugins or template changes caught and fixed before they affect rankings or user experience.
0
Sites monitored for Core Web Vitals regressionsAveraged Across Builds
0
Avg. Lighthouse performance score0
Avg. accessibility score0
Avg. page load time0
Sites launch with schema & sitemap in placeA Look at the Build
Full screenshots are being prepared for publication as new projects continue to launch.
Technologies
Need a Site That's Fast, Accessible and Built to Rank?
I design and build sites end to end — on Astro or WordPress, whichever fits — with performance, accessibility and SEO handled from day one instead of fixed after launch.