Personal project · Website · Technical SEO
This website: a multilingual portfolio built as a technical SEO showcase
A trilingual portfolio designed, developed and optimised end-to-end: the site you are reading now.
- Year
- 2026
- Role
- Design, development, SEO
- Stack
- Next.js · React · TypeScript · Tailwind CSS · next-intl · MDX · Cloudflare Workers

- languages, with localized URLs
- 3
- languages, with localized URLs
- indexable pages in the sitemap
- 78
- indexable pages in the sitemap
- third-party scripts by default
- 0
- third-party scripts by default
- original artwork, drawn in SVG
- 100%
- original artwork, drawn in SVG
Context & challenge
Present services to three language markets (English, Italian and Brazilian Portuguese) without duplicating effort or creating conflicting signals for search engines.
Make the site itself proof of the work: if it sells technical SEO and web performance, it has to demonstrate both.
Objectives
- IPresent services, background and work clearly to clients and recruiters in three languages.
- IIRank for the search terms each market actually uses, with a clean international SEO setup.
- IIILoad fast on any connection, meet WCAG 2.2 AA and stay easy to maintain.
Solution & process
Localized URL segments and slugs per market (for example /it/servizi/seo-tecnico), with self-referencing canonicals and a complete hreflang cluster including x-default.
Static generation for every page, deployed to Cloudflare Workers, with no third-party scripts by default.
A small custom design system with CSS-only motion that respects reduced-motion preferences, and a JSON-LD graph linking Person, WebSite, Service and BlogPosting entities.
Keyword mapping per locale based on Semrush data, so each page targets the search terms used in its own market.
Gallery



Results
A maintainable codebase with type checking, linting and tests in CI.
The first external audit (20 November 2026) scored 100/100 for accessibility in Lighthouse and passed the on-page checks above. Search results will be published once there is enough real data. No estimated numbers in the meantime.
Measured live, in your browser
These are not lab scores or marketing numbers: they are the Core Web Vitals of this page during your own visit, read with the browser's PerformanceObserver API. Values change with your device and connection, which is exactly the point of field data.
This page, measured in your browser
- LCPTarget ≤ 2.50 s
- measuring…
- CLSTarget ≤ 0.100
- measuring…
- FCPTarget ≤ 1.80 s
- measuring…
- TTFBTarget ≤ 800 ms
- measuring…
Live readings from your visit via the PerformanceObserver API. Nothing is sent anywhere.
- Lighthouse accessibility score
- 100/100
- Lighthouse · /en · 2026-11-20
- Colour contrast (WCAG 2.1 AA)
- ✓
- On-page audit · /en · 2026-11-20
- Canonical, single H1, Open Graph and X card
- ✓
- On-page audit · /en · 2026-11-20
External audit of the live page
On-page audit · /en · 2026-11-20
Accessibility
- Lighthouse accessibility score100/100
- Colour contrast meets WCAG 2.1 AA
- Descriptive link names
- Valid HTML language
- Mobile viewport set
- Landmark regions (main, header, nav, footer)
On-page SEO
- URL length44
- Canonical tag points to the current URL
- Meta title length (characters)55
- Meta description present
- Single H1
- Heading structure H1 to H3
Social previews
- Open Graph title, description and image
- X card (summary_large_image)
Highlights
- 3 languages with localized URLs
- Hreflang + canonical generated from one route map
- Live Core Web Vitals readout on this case study
- Contact form with validation and spam protection


