← Issues index

39. Article pages are 1.3–1.9 MB of HTML, mostly repeated boilerplate — Medium (PV, DH)

Added 16 Nov 2026. Live measurement, one recent text article per site, Googlebot UA, 16 Nov 2026.

Re-check 19 Nov 2026: still an issue on PV (heavier than on 16 Nov), partly on DH. Live, Googlebot UA, one article per site (PV same article …-4376516; DH …/bengaluru-emerges-as-second-largest-ai-startup-cluster-in-asia-4223444, a different article from 16 Nov), Cloudflare HIT on both:

KB, uncompressed PV 19 Nov PV 16 Nov DH 19 Nov DH 16 Nov
Total HTML 2,235 1,864 1,303 1,289
Embedded page data 1,311 954 223 219
Inline CSS 461 461 653 637
Inline SVG 373 373 368 367
JSON-LD 17 11 10 20

Original measurement, 16 Nov 2026:

Article HTML (uncompressed) PV DH
Total 1,864 KB (344 KB gzip) 1,289 KB
Embedded page data (<script id="static-page">) 954 KB 219 KB
Inline CSS (<style>) 461 KB 637 KB
Inline SVG icons 373 KB 367 KB
JSON-LD 11 KB 20 KB

PV's embedded data (952 KB): the story itself is 28 KB; the rest repeats on every page: qt.data.footerCollection 328 KB, qt.config.layout 372 KB, qt.data.navigationMenu 133 KB, qt.config.sections 83 KB.

Why it matters: every Googlebot fetch downloads and parses this (PV Crawl stats ≈ 122 KB/request on the wire; 21–27 GB/day, #3); uncached pages take ~1 s at the origin (#14); large HTML and inline CSS/SVG slow first render on mobile (CWV, #5/#15). With PV's limited crawl/render attention (#2, #3), lighter pages are cheaper to fetch and render.

Fix (🛠️):

  1. PV: load the footer collection with only the fields and count the footer shows (or render the footer from a small server-side list), and keep navigationMenu / config.layout / sections out of the client state or trim them to what the page uses (data loaders app/server/data-loaders/, framework loadData).
  2. Both: move inline CSS to cached external stylesheets except critical CSS; replace repeated inline SVG icons with a sprite or external file.
  3. Measure before/after: HTML size, origin TTFB, Crawl stats KB/request.

Verify: view-source size of an article drops well below 1 MB (PV embedded data close to story size + a small config).

Footer collection: what is embedded vs what readers see (checked by the user in Chrome DevTools, 16 Nov 2026, article …-4376516):

Menus (16 Nov 2026, code + live).

DH comparison (live, 16 Nov 2026, article …-4208571): DH embedded data is 220 KB (raw menu 93 KB, config.sections 50 KB, navigationMenu 34 KB, story 28 KB; footer collection < 8 KB). DH already fixed the footer on 13 Nov 2026 (47a7e85e "Cwv issue (#2094)", app/server/data-loaders/menu-data.js:5-37): "story-fields": "headline,slug,url" and only 4 stories per sub-collection. PV's loadFooterCollection (menu-data.js:5-7 @ 70d7bebf) still requests full stories ({ limit: 4 } only). PV's footer shows 4 groups × 4 links, so DH's function can be ported to PV unchanged (~300 KB less per PV page). DH's remaining weight is inline CSS (637 KB) and inline SVG (367 KB).

DH lab speed (Chrome DevTools trace, 16 Nov 2026; mobile 412×915, Fast 4G, 4× CPU, cold cache; article …-4163706): LCP 729 ms (TTFB 171 ms + render delay 558 ms), CLS 0.01; no CrUX field data for that URL. Insights flagged: image delivery (158 KB savable), short cache lifetimes (1.1 MB), font-display (~220 ms FCP), large DOM, third parties, forced reflows, legacy JavaScript (86 KB). PV trace pending (browser tool unavailable); PageSpeed Insights API quota (keyless) exhausted for the day.

DH footer on mobile (DevTools, 412×915, 16 Nov 2026, article …-4163706): footer collection 5 KB, 12 stories, 12 footer story links, all 12 visible. PV for comparison: 311 KB, 117 stories, 16 of 17 links hidden on mobile.

PV page speed (Chrome DevTools trace, 16 Nov 2026; mobile 412×915, Fast 4G, 4× CPU, cold cache; article …-4376516):

PV lab PV real users (CrUX p75, this URL) DH lab (…-4163706)
LCP 17.0 s (TTFB 0.17 s, load delay 14.4 s, load 0.6 s, render delay 1.8 s) 3.6 s (TTFB 0.71 s, load delay 6.75 s) 0.73 s
CLS 0.03 0.33 (poor) 0.01
INP – 306 ms –

What the code confirms about the speed findings (16 Nov 2026, tpml upstream/master 70d7bebf):