Lean does not mean incomplete.
Plain HTML/CSS can still include semantic structure, structured data, hreflang, sitemaps, robots directives, Open Graph and accessibility. Each layer should exist for a clear reason—not to make the technology stack look sophisticated.
Fewer dependencies also reduce attack surface and maintenance cost.
Indexability should be easy to verify.
Each indexable page should return 200, use a self-canonical, have appropriate internal links and appear in the sitemap where relevant. Redirect chains, orphan pages and duplicate canonicals are simple technical issues that can create noisy crawl signals.
For small sites, clarity usually matters more than crawl-budget optimization.
Performance should be solved from the critical path.
When HTML is small and there is no JavaScript framework, the bottleneck is usually fonts, render-blocking CSS, images or hosting TTFB. These are far easier to optimize than a large frontend bundle.
The goal is to reduce how much work the browser must complete before rendering the primary content.
Technical foundation is necessary, not sufficient.
A near-perfect Lighthouse score does not create rankings by itself. Technical SEO gives search systems stable access and understanding; authority, usefulness and evidence still drive most long-term value.