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 |
- PV page data:
qt.config.layout.menu651 KB (372 KB for all oflayouton 16 Nov: it grew, or the two measurements counted differently; not traced), footer collection 379 KB,navigationMenu140 KB,sections101 KB, story 38 KB. - DH page data: footer collection 4.6 KB (the 13 Nov fix works);
layout.menu112 KB,sections50 KB,navigationMenu35 KB, story 13 KB. DH's weight is now mostly inline CSS (653 KB) and SVG (368 KB). - Code, unchanged since 16 Nov: PV
app/server/data-loaders/menu-data.js:5-7still loads full footer stories ({ limit: 4 }, no field list) onmaster0b3f7227and on the pending release branchssr-fixab40d7ad; DH prunes them (fetchAndPruneFooter,47a7e85e, 13 Nov; memoised in41b80112, 18 Nov). Both sites still sendlayout(incl.layout.menu) to the browser:"layout"inWHITELIST_CONFIG_KEYS,app/server/load-data.js:29(PV) /:30(DH). No commit after 16 Nov touches CSS or SVG inlining. - Not checked: whether the inline CSS is critical CSS or the full stylesheet; where the SVG is injected.
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 (🛠️):
- 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/sectionsout of the client state or trim them to what the page uses (data loadersapp/server/data-loaders/, frameworkloadData). - Both: move inline CSS to cached external stylesheets except critical CSS; replace repeated inline SVG icons with a sprite or external file.
- 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):
footerCollection"Footer" = 311 KB per page: 4 sub-collections × 40 stories (ಹೆಚ್ಚು ಓದಿದ ಸುದ್ದಿ 77 KB, ಕ್ರೀಡೆ 75 KB, ಒಳನೋಟ 82 KB, ಟ್ರೆಂಡಿಂಗ್ 77 KB); 117 distinct stories.- The rendered footer has 17 story links, 16 of them from this collection; 4 stories appear twice (links 1–4 repeat as 13–16).
- Mobile (375×667 device emulation): 1 of 17 visible, 16 hidden; none of the 16 footer-collection links is visible. The one visible link (ವರ್ಷ ಭವಿಷ್ಯ) is not from the collection. Desktop shows the 17.
- So ~98% of PV's search visitors (mobile) download ~311 KB of footer data on every page for links they never see. The links stay in the HTML, so Google can still follow them; the fix is to load ~5 stories per sub-collection with only headline, URL and image, not to remove the footer.
Menus (16 Nov 2026, code + live).
qt.config.layout.menuis the raw CMS menu export (PV 371 KB, DH 93 KB; same data ashttps://www.prajavani.net/api/v1/config→layout.menu). In both repos it is read only on the server, to buildnavigationMenu(app/server/load-data.js:56, :134PV @70d7bebf;:56, :145DH @47a7e85e). Every header/footer component readsqt.data.navigationMenu(PV 133 KB, DH 34 KB) instead. The only browser-side reader in the installed libraries is Quintype'sMenucomponent (@quintype/components/dist/es/components/menu.js:26), which neither site imports.- So
layout.menucan be left out of the page data on both sites with no visible change (the/api/v1/configAPI itself is untouched; the server still fetches it). Tech should still click through header, hamburger, footer and a client-side page change on staging.
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 | – |
- PV's LCP element in the lab is a Google ad image (
tpc.googlesyndication.com/simgad/…, requested bypubads_impl.js, not in the initial HTML, nofetchpriority=high). The article's own hero image is not in the server HTML (#7), so the largest element on a phone screen becomes whatever the ads paint, late. - Third parties on one PV article (lab): Google Tag Manager 1.7 MB / 3.0 s main thread; Google/DoubleClick ads 1.2 MB / 2.7 s; Amazon ads 104 KB / 1.8 s; Clarity 28 KB / 1.4 s; Taboola 1.1 MB / 1.3 s; Facebook 271 KB / 0.8 s.
- Other insights (PV): image delivery 458 KB savable; short cache lifetimes ~1 MB;
font-display~270 ms FCP; large DOM; forced reflows; legacy JS 83 KB. - Fix direction (🛠️, ties to #7, #5, #8): server-render the hero image with
fetchpriority="high"so the article's own image is the LCP; reserve fixed space for above-the-fold ad slots; audit Google Tag Manager tags (1.7 MB, 3 s) and defer non-essential third parties (Clarity, Amazon, Facebook) until after load.
What the code confirms about the speed findings (16 Nov 2026, tpml upstream/master 70d7bebf):
- Hero image client-only: ✅
story-header/hero-image/index.js:14<WithLazy>(see #7); nofetchpriorityanywhere. - Google Tag Manager loads at page start: ✅
views/pages/partials/gtm.ejs(standard async snippet), included atlayout.ejs:145; ID from configpublisher-attributes.google_tag_manager.id(app/server/helpers/index.js:69) = GTM-MGBFQ9R (live HTML). - Public container
https://www.googletagmanager.com/gtm.js?id=GTM-MGBFQ9R(532 KB uncompressed, fetched 16 Nov 2026): Microsoft Clarity (1 mention) and Facebook pixel (2) are loaded through it; also 5 custom HTML tags, Google Ads conversion tags (9 mentions), GA4G-DPVVLMRR0T. Amazon, vdo.ai, Taboola, iZooto, Criteo: not in the container. - Google ads
gpt.js: ✅layout.ejs:122(async). Taboola: ✅ads/taboola-ad/index.js. - Amazon ads and vdo.ai: ❌ not in site code (Amazon loader commented out,
ads/utils.js:157-159) and not in GTM → most likely delivered by Google Ad Manager line items / creatives; only the Ad Manager setup can confirm. - Ad slots reserve height: ✅ partly,
ads/ads.m.cssmin-height50/90/250/600 px; field CLS 0.33 more likely from Taboola / unsized slots (#5). - Timings (LCP 17 s lab, 3.6 s field; 3 s GTM main thread) are measurements, not derivable from code.