2026-05-10 — Re-verified 3 critical SEO/perf issues; 2 already fixed, 1 deployed live

Date: 2026-05-10

Importance: High

Status: 2 of 3 issues confirmed already fixed; 1 partial fix deployed; 2 open decisions for Sam.

What I Did

Verified each of the 3 critical issues from the prior audit against the live site, then executed safe fixes.

Issue #1 — Eager-loaded YouTube iframes site-wide

Finding: ALREADY FIXED before this session.

The 2 "iframe" matches found on the homepage are inside JavaScript template strings (el.innerHTML = '<iframe ...>') inside a saPlayVideo() click handler. They are a custom facade pattern: only injected into the DOM after a user clicks a .sa-story-video button.

Real eager YouTube iframes shipped with HTML: 0 (homepage, location, practice, attorney bio).
Facade markers (sa-story-video / saPlayVideo): 5 on homepage.

No action needed. The audit's claim of 1.3-2.6 MB shipped per embed before interaction is no longer accurate.

Issue #2 — ~250 KB inline CSS + JS, no APO, cf-cache-status MISS

Finding: STILL TRUE on bytes, partially mitigated by edge cache.

Page	Inline CSS+JS	cf-cache-status
Homepage	281 KB	MISS (cold)
/our-team/	243 KB	MISS (cold)
/practice-areas/car-accident-lawyer/	233 KB	HIT
/about-us/meet-our-team/sam-aguiar/	272 KB	HIT

Response headers DO include cache-control: s-maxage=86400, so most pages eventually serve from Cloudflare edge. APO is not enabled. Real options for reducing actual bytes:

(A) Cloudflare APO ($5/mo per zone) — caches HTML at edge with smarter TTLs, doesn't reduce bytes but improves TTFB.
(B) Autoptimize / WP Rocket — externalize and cache inline blocks.
(C) Accept current state — edge cache is already doing most of the work.