Sports fans checking live odds, matchup picks, and betting guides on moneyline.com are almost always on mobile phones right before kickoff or tip-off. While Next.js is designed for fast server-side rendering, your homepage is currently shipping a massive 1,004-kilobyte (1.0 MB!) raw HTML document and loading 172 separate <script> tags on initial paint after a 795-millisecond server delay.
Why Your Next.js Homepage Ships 1.0 MB of Raw HTML & 172 Scripts
When we inspected the DOM and HTTP response on https://moneyline.com/ (featured in Black Flag Creative's portfolio), we traced the slowdown to a classic Next.js getServerSideProps / __NEXT_DATA__ serialization bottleneck:
- 1,004 KB Homepage HTML Document: When unfiltered CMS objects, full article bodies, and deep sportsbook odds trees are returned directly from
getServerSidePropsorgetStaticPropswithout field projection, Next.js serializes the entire payload twice—once in the rendered DOM and a second time inside the inline__NEXT_DATA__JSON script block—pushing your homepage HTML past one full megabyte. - 172 Separate
<script>Tags: Unconsolidated chunk splitting and third-party tracking scripts force mobile browsers to download and hydrate 172 script tags on initial load, severely impacting Interaction to Next Paint (INP) and Total Blocking Time (TBT). - Four Competing
<h1>Headings & Agency Footer Link: The homepage currently renders4separate<h1>tags and carries an external agency backlink in the footer.
Next.js Hydration Fix: Projecting only the required card fields in your data-fetching layer (title, slug, excerpt, thumbnail, and summary odds) will immediately shrink your homepage HTML from 1,004 KB to under 60 KB and cut React hydration time on mobile by 80%.
Next.js Telemetry Recorded on Moneyline.com
| Next.js Layer | Measured on Moneyline.com | High-Velocity Media Spec | Core Web Vitals Impact |
|---|---|---|---|
Initial HTML + __NEXT_DATA__ |
1,004 KB (1.0 MB) |
Under 65 KB |
Google warns when HTML/SSR payloads exceed 128 KB; 1 MB stalls mobile hydration. |
| Script Tag Count | 172 script tags |
12–18 route chunks |
172 scripts create heavy main-thread blocking on iOS and Android. |
| Server Response (TTFB) | 795 ms |
Under 80 ms (ISR / Edge Cache) |
Serializing 1 MB of JSON on the server delays every page response. |
| Heading Hierarchy | 4 <h1> tags on homepage |
Single primary <h1> |
Clarifies primary topical hierarchy for Google News and organic search. |
Where We Can Help the Moneyline Engineering & Editorial Team
1. Trimming __NEXT_DATA__ Serialization from 1,004 KB to Under 65 KB
We can help your team add DTO field projection in your Next.js data-fetching functions so full article content and unused sportsbook arrays are stripped before serialization—cutting 900+ KB off every homepage load with zero visual changes.
2. Consolidating the 172 Script Chunks & Enabling Sub-50ms Edge Caching
By tuning your webpack/Next.js chunk splitting, deferring third-party analytics via Web Workers/Partytown, and configuring stale-while-revalidate edge caching, your odds tables and picks pages will open instantaneously.
3. Clean Single-<h1> Hierarchy & SportsEvent Schema
Consolidating your homepage to a single primary <h1> and enriching matchup pages with structured SportsEvent and NewsArticle Schema.org JSON-LD markup strengthens Top Stories and organic sports search rankings.
Reach Out Anytime If You Would Like a Hand
Feel free to share this breakdown with your engineering team so they can inspect the 1,004 KB __NEXT_DATA__ payload and 172 script tags. If you would ever like our help optimizing moneyline.com's Next.js performance or Core Web Vitals, check out our systems engineering work on the WebDesigner.LA Portfolio, grab a time on my Consultation Calendar, or call or text me at (818) 903-2338.