SEO and speed

Targets on a phone (Lighthouse, as in Google's PageSpeed Insights): performance 95+, accessibility 100, best practices 100, SEO 100. Ginta's demo sites score 92–100 / 100 / 100 / 100.

What Ginta does on every page

• Inlines only the CSS rules the page uses from /_g/ginta.css (no render-blocking stylesheet).
• Serves Google Fonts and Pexels photos from the site's own address (no extra connections; visitors' browsers never contact Google or Pexels), AVIF/WebP for photos, the main Latin font files preloaded.
• Adds width/height to images it knows, loading="lazy" below the first big image, and gives that one fetchpriority="high" and a preload.
• Canonical link and Open Graph fallbacks, sitemap.xml, robots.txt, hreflang between translations (about.html in lang="lt" ↔ en/about.html in lang="en").
• Pings IndexNow (Bing, Yandex, Seznam, Naver…) after each publish.
• Checks every site a few minutes after it changes and keeps the scores (stats).

What your pages should do

• <html lang>, the viewport meta, a <title> and a <meta name="description"> on every page.
• One <h1>, then <h2>, <h3> without skipping. alt on every image; aria-label on icon-only links/buttons.
• Text contrast 4.5:1 (3:1 for large text), also on badges and text over photos.
• The hero picture as an <img> (not a CSS background), so it can load first.
• Apps: prerender pages at build time; a client-only <div id="root"> is empty for search engines.

Ginta warns about the first points when you publish (warnings in the answer).