How We Hit 100/100 Mobile PageSpeed & 90% SEO Across 332,000+ Next.js 16 Game Pages on $0/Month
Modern PC game releases routinely exceed 140 GB, making fast compression indexing and zero-bloat mobile web performance critical for global gamers.
While building RepackDeck — indexing 7,385+ lossless PC game repacks, 597+ official FLiNG single-player trainers, and 100% campaign mission walkthroughs across 45 languages — we hit three tricky Next.js 16 + SEO engineering problems and solved all of them on a $0.00/month Cloud Run + Cloudflare + Supabase stack.
1. Why loading.tsx Silently Hid <h1> From Non-JS HTML Crawlers
In Next.js App Router, adding a loading.tsx file inside a dynamic route segment wraps the page in <Suspense>. Browsers hydrate the streamed <div hidden id="S:0"> payload cleanly, but non-JavaScript HTML crawlers only inspect the initial shell—causing thousands of false h1_missing and thin-content alerts.
Removing loading.tsx inside /[lang]/game/[slug] and setting htmlLimitedBots: /.*/ in next.config.ts jumped our live on-page SEO score from 60% → 90% across 332,000+ localized pages.
2. Keeping 100/100 Mobile PageSpeed With Live Monetization
- Defer all third-party ad and analytics scripts strictly to physical user gestures (
scroll,pointerdown,touchstart,keydown) with zero<45sfallback timers. - Reserve explicit CSS
min-hwrappers (0CLS) and optimize above-the-fold responsive covers (192w, 256w) with matching<link rel="preload" imageSrcSet>. - Live result on Google PageSpeed Insights API v5: 100/100 Mobile Performance, Accessibility, Best Practices & SEO on our Low-Spec PC Game Repacks Hub (
1.1sLCP,0CLS).
3. Open Docs & Dynamic Edge SVG Shields
We also shipped an edge SVG badge generator (Free SVG Verification Badges) and an open GitHub Pages PC Compression & MD5 Reference.