Building Confidence
Quality Metrics
Let's be honest: this is a small portfolio site. There's not much on it. Getting good Lighthouse scores here isn't exactly a feat of engineering, and I'm not showing these numbers to brag.
Most people outside the field still associate AI output with slop. But developers already know that AI can help produce clean, fast, accessible code. This page aims at illustrating this. Every deployment goes through Lighthouse, and the CI pipeline blocks anything below threshold. These scores are what shipped.
Below you'll find PageSpeed Insight scores, test coverage, accessibility compliance checks, bundle size, and the quality gates that guard every deploy. All of it is generated automatically — nothing is hand-picked or cherry-picked.
Quality Gates
These scores come from automated quality gates that run on every commit, not spot checks before a release. The tooling is all freely available, and whether to actually enforce it is an engineering decision.
- TypeScript strict modepassing
- ESLint enforcedpassing
- Prettier formattingpassing
- Conventional Commitspassing
- CI ·Unit test coverage ≥ 80%passing
- CI ·E2E tests passpassing
- CI ·Lighthouse CI thresholdspassing
Test Coverage
Unit and end-to-end tests run on every push, with enforced coverage thresholds in CI. The unit test suite covers component rendering, data logic, and server actions, while E2E tests verify full page navigation, form interactions, and accessibility through a real browser. If coverage drops below the configured minimums, the build fails.
PageSpeed Insight Scores
Last audited: April 2, 2026
Slow sites lose people, and that relationship has been measured enough that it doesn't need repeating here. This site stays fast by leaning on optimized assets, minimal client-side JavaScript, modern image formats, and edge delivery.
The accessibility score measures whether people with different abilities can actually use the site. That means semantic HTML, a proper heading hierarchy, sufficient color contrast, keyboard navigation, and ARIA attributes where they're needed.
This category covers technical hygiene: HTTPS everywhere, no deprecated APIs, secure headers, a clean console, and correct resource handling. These are the details that users never notice when they're done right, but pick up on immediately when they're not.
Good SEO tends to fall out of well-structured code on its own. Semantic markup, proper meta tags, structured data, a valid sitemap, and fast load times already cover most of what search engines look for.
Accessibility Compliance
The Lighthouse accessibility score catches a lot, but it doesn't cover all of WCAG. This site also targets WCAG 2.1 AA conformance, which means things like visible focus indicators, skip-to-content links, reduced-motion support, and readable text at 200% zoom. Automated tooling handles the programmatic checks, and manual testing fills in the gaps that tooling can't reach.
WCAG 2.1 Level AA
8 pages tested
Tested with axe-core
Bundle Size
A fast Lighthouse score means nothing if the JavaScript payload balloons on the next deploy. Bundle size is tracked as part of the build process, and the site relies on Next.js server components to keep most logic off the client entirely. Pages that don't need interactivity don't ship a JS bundle for it.