FixWeb

// mobile / spotlight

Internationalization, Mobile, and PWA Basics

Viewport, hreflang, language, manifest, and app-readiness signals.

Why it matters

A good site should tell browsers and crawlers which language it is, how it adapts to mobile screens, and whether it behaves like an installable app.

How it works

FixWeb checks rendered viewport metadata, hreflang links, manifest links, and language declarations captured by the crawler.

Site impact

Weak mobile configuration hurts usability; broken hreflang confuses locale targeting; missing manifest metadata limits app-like experiences.

// how fixweb tests for it

How FixWeb tests for it

The rendered snapshot records viewport, html lang, rel=alternate hreflang links, and rel=manifest references.

How to improve

Set a mobile viewport, keep hreflang complete and reciprocal, set html lang for each locale, and add a manifest when the site should be installable.

// run it on your own site

Keep improving while FixWeb keeps watch.

FixWeb crawls public pages like a real browser, then organizes crawl, search, content, accessibility, performance, media, form, runtime, browser-compatibility, owner-data, and repo findings into practical improvement prompts for Cursor, Claude, and Copilot.

Mobile, PWA & i18n
7
tests fired in this category
modules
1
dedicated mobile, pwa & i18n checks
every scan
286+
tests across all categories
  • Free — no credit card, no install, no Slack ping
  • Just paste a URL — we crawl, analyze, and report
  • Severity-graded quality issues, deduped to signal only
  • Current, AI-ready improvement prompts you can paste into Cursor, Claude, Copilot
Run a free scan

// latest modules · practical fixes · better websites

Internationalization, Mobile, and PWA Basics — Quality Spotlight | FixWeb · FixWeb