P6 · Page speed, ads and analytics

Sites: Prajavani (PV, www.prajavani.net), Deccan Herald (DH, www.deccanherald.com) · Priority: 6 of 6 · Prepared: 18 Nov 2026 by the Product, SEO and Data team · Internal refs: #39, #7, #5, #6, #8, #10, #15, #16, #29

Summary

This package covers front-end weight, layout shift, ad code and analytics timing. Most items are PV only. Start with two cheap, low-risk changes: port DH's footer loader to PV, and stop sending the raw CMS menu to the browser on both sites. Together they remove roughly 670 KB of embedded data from every PV article page (about 300 KB from the footer, 371 KB of raw menu; uncompressed). DH saves 93 KB from the menu. The Taboola space fixes (items 4 and 5) are small and can ship early. The remaining items are a hero and header layout flip, ad-slot clean-ups, a broken font build, and a GA4 page_view that fires too late. One item (field CLS on some pages) still needs investigation.

Core Web Vitals are only a light ranking signal. The benefit for readers (less jumping, faster first paint) is better established than any ranking gain. Do not expect a ranking change from this package alone.

Impact

What the measurements show:

What is NOT proven:

Items

Issue: PV embeds a footer data collection of about 311 KB in every article page, but phone users cannot see most of it.

Evidence:

Fix:

Impact: about 300 KB less embedded data per PV article page. Smaller HTML helps every Googlebot fetch and mobile first render. Not a proven ranking factor.

Verify: view-source on a PV article: footerCollection is far smaller (DH's is 5 KB). Mobile footer still shows its links on staging. Compare HTML size and Search Console Crawl stats KB/request before and after.

2. Both sites: stop sending the raw CMS menu to the browser — Medium · PV, DH · Fix proposed

Issue: qt.config.layout.menu is the raw CMS menu export. It is on every page but the browser never reads it.

Evidence:

Fix:

Impact: up to 371 KB less per PV page and 93 KB less per DH page, with no visible change expected.

Verify: on staging, click through the header, hamburger, footer and a client-side page change. View-source shows layout.menu is gone. PV article HTML should end well below 1 MB (embedded data close to story size plus a small config).

3. Both sites: move inline CSS and repeated SVG out of the HTML — Medium · PV, DH · Fix proposed

Issue: Article HTML carries large inline CSS and inline SVG icons.

Evidence (16 Nov 2026, same live measurement as above):

Fix: keep only critical CSS inline and serve the rest as cached external stylesheets. Replace repeated inline SVG with a sprite or external file.

Impact: smaller, more cacheable HTML. Magnitude not measured.

Verify: record HTML size, origin TTFB and Crawl stats KB/request before and after. Re-run Lighthouse (mobile) on one article per site.

4. PV: reserve space for the Taboola feed below the article — Medium (lowered from High on 12 Nov 2026) · PV · Fix proposed. Can ship early.

Issue: The Taboola feed below the article has no reserved height. The page jumps as the reader scrolls, and the text moves by about 240 px.

Evidence:

Fix:

Impact: removes the biggest measured source of CLS. Ranking effect is expected to be small (see Impact section).

Verify: Chrome DevTools, Performance panel, Live metrics. Mobile emulation, 4× CPU, Fast 4G. Load an article, wait 5 s, scroll slowly to the bottom. Pass: CLS below 0.1, and taboola-below-article / tbl-feed-container or footer is no longer the main shifting element. Test at least two text articles and two cartoon pages (cartoons were about 0.67 after scrolling before the fix). Field CLS in Search Console updates on a rolling 28-day window, so expect results about a month after release.

5. PV: reserve space for the Taboola mid-article block — Low (lowered from Medium on 12 Nov 2026) · PV · Fix proposed. Ship with item 4.

Issue: #taboola-mid-article-personalisation (.taboola-4u in story-elements.m.css) is inserted after the 4th paragraph with no height.

Evidence: measured shift 0 to 242 px (lab, Oct 2026).

Fix: give .taboola-4u a reserved height. Same blank-space check with the Taboola owner as item 4.

Impact: reading comfort. Small effect on rankings.

Verify: same test as item 4; no jump at the 4th paragraph.

6. PV: header and hero layout flip on phones — Medium · PV · Fix proposed

Issue: helper/custom-hook/useDevice.js returns null until after mount, so every phone first renders the desktop layout, then switches.

Evidence:

Fix:

Impact: removes a 100 to 270 px jump on load. Load CLS is already small, so the gain is mainly smoothness and LCP (with P1).

Verify: mobile emulation, 4× CPU, reload an article with a hero image. Headline, byline and hero should not move in the first 3 s. Load-only CLS below 0.05.

7. PV: ad slot and ad container clean-ups — Medium (double requests), Low (hydration) · PV · Fix proposed

Issue: Ad slots are defined twice, and ad containers differ between server and client.

Evidence:

Fix:

Impact: fewer duplicate ad requests, no hydration warnings, possibly less late CLS. Ad ops should check fill, revenue and viewability around the change.

Verify: console shows no defineSlot error. Network panel shows one request per slot until a refresh is expected. No hydration warning on desktop. Ad ops confirm slots still fill.

8. PV: unexplained high field CLS on some pages — Medium · PV · Needs investigation

Update 19 Nov 2026: folded into item 4. The lab figures below were measured on load only. The item 4 lab test shows PV CLS above 0.1 only after scrolling, mostly from the Taboola feed, and both field values fall in that after-scroll range. No separate fix is needed; re-check these two URLs after item 4 ships, and add web-vitals attribution logging only if field CLS stays above 0.1.

Issue (original): Field CLS is far above lab CLS on some pages, and the cause is not known.

Evidence:

Fix (no code fix yet): add web-vitals attribution logging on live pages so real shifting elements are captured, then act on the results.

Impact: unknown until measured.

Verify: after a week of logging, list the top shifting elements by page type. Re-check field CLS after items 4 to 7 ship.

9. PV: fix broken font files — Low (Googlebot view), but readers are affected · PV · Fix proposed

Issue: Some "font" files served by PV are not fonts. They fail for every reader, not only Googlebot.

Evidence:

Fix: in the font rule add type: "javascript/auto" (keeps file-loader working under webpack 5), or use type: "asset/resource" and drop file-loader.

Impact: fonts load for readers; fewer font-swap shifts are possible (not measured).

Verify: curl -s <font url> | head -c 4 returns wOFF or wOF2 (or blank bytes for TTF). The console shows no font decode errors.

10. PV: third-party scripts and GTM load — Medium · PV · Fix direction only

Issue: Third-party code dominates PV's main thread in the lab.

Evidence (one PV article, lab, 16 Nov 2026): Google Tag Manager 1.7 MB and 3.0 s main thread; Google/DoubleClick ads 1.2 MB and 2.7 s; Amazon ads 104 KB and 1.8 s; Clarity 28 KB and 1.4 s; Taboola 1.1 MB and 1.3 s; Facebook 271 KB and 0.8 s.

Fix: audit GTM tags and defer non-essential ones (Clarity, Facebook) until after load. Ad ops should check where Amazon and vdo.ai are injected.

Impact: unmeasured. INP of 306 ms (CrUX p75, 16 Nov 2026) is a candidate to improve.

Verify: repeat the DevTools trace and compare third-party main-thread time and LCP.

11. Both sites: send the GA4 page_view earlier — Medium · PV, DH · Fix proposed, not built. Needs GA4 report-owner input.

Issue: The page_view event is sent after other events, so some visits have no landing page in GA4 ("(not set)"). This is not a ranking issue. It makes GA4 page-level reports undercount real visits, including organic landings.

Evidence:

Fix:

Impact: more accurate GA4 landing-page reports. This changes event order and any report that uses comment_number, so tell report owners before release.

Verify: fresh browser profile: the first GA4 hit is page_view with _ss=1. After release, the web "(not set)" share on DH articles should fall from 8.9% toward 1% or less. Track daily for 2 to 4 weeks. App sessions, 30-minute session timeouts on open tabs and bots will still show "(not set)".

Release checklist

  1. Items 1 and 2 first (smaller HTML, low risk). Staging click-through: header, hamburger, footer, client-side navigation.
  2. Items 4 and 5 together (Taboola space). Confirm blank-space behaviour with the Taboola owner.
  3. Item 9 (font build). Check font URLs with curl.
  4. Items 6 and 7, ideally alongside P1's hero-image work, so LCP and layout change once.
  5. Item 11, with GA4 report owners informed before release.
  6. Start item 8 (web-vitals logging) at once; it needs time to collect data.
  7. After each release: Lighthouse mobile on one article per site, CrUX p75, Search Console Core Web Vitals report (allow about 28 days), GA4 "(not set)" share, and Crawl stats KB/request.
  8. Ad ops sign-off that ad fill and viewability did not drop.