Full website speed audit - Core Web Vitals (LCP, INP, CLS, FCP, TBT, TTFB) and 69 checks across server location vs. the visitors’ country, rendering, JavaScript, third parties, images, video, fonts, c
Measure first, rank by real impact, then give one precise fix per finding. For AI-built sites the fixes are prompts the owner pastes into their builder; for WordPress they are plugin settings and snippets.
references/checklist.md, one short neutral line each: "Check 8/69 - G1: where the page is served from", "Check 9/69 - G2: where the API and database answer from", and so on for all 69. All checks get the same plain wording; none is singled out or explained as more important.references/server-location.md - how to find where the site is really served from (origin, CDN edge, cache status, backend/API region), how to measure from the visitors' country, the latency cost table, and how to word the recommendation.references/checklist.md - 69 checks (R, L, G, J, T, I, V, F, S, C, N, A, E, P, M, X): Detect, Impact, default tier, Prompt.references/principles.md - why each check matters (Core Web Vitals, distance and round trips, critical path, JS loading, CSS, DOM, caching, images, video, fonts, embeds, navigation, testing), linked to checks.references/impact-analysis.md - ranking by seconds saved, the three report tiers, and the report template. Read before writing the report.references/platforms.md - recognizing Lovable/Base44/Bolt/v0/etc., where they serve from, and what a prompt can and can't change there.references/wordpress.md - the same checks applied with WordPress plugins and snippets; assets/safelist-*.txt and assets/debloat-skip-uncached.php belong to it.assets/collect.js - in-page collector (run in the visitor's browser): server/edge location and cache status from headers, connection timings, empty-shell detection, platform, LCP element, bytes before LCP, render-blocking files, bundle contents, dev-build and source-map leaks, images, video/GIF, fonts, third-party tags, anti-flicker snippets, cache headers, service worker, back/forward-cache blockers, long pages, non-composited animations, API latency.scripts/scan.py - server-side scan: redirects, TTFB, query-string cache, DNS/IP, edge/PoP and cache headers, HTML signals; --from IL measures from real probes in a country (Globalping), --psi pulls PageSpeed Insights.scripts/lighthouse_runs.mjs - runs Lighthouse locally N times (mobile/desktop), prints the median, and checks a performance budget (assets/budget.json).lang="he"/.co.il/₪ means Israel; ask if unclear).https://pagespeed.web.dev/analysis?url=<url>&form_factor=mobile (or scan.py --psi, or node scripts/lighthouse_runs.mjs <url> when Chrome is available). Read the score, the 5 metrics, the field-data box, the LCP element and LCP breakdown, and every failing audit.assets/collect.js in the page, keep its output. Repeat on the other key pages.references/platforms.md) - it decides which fixes are possible.references/server-location.md). Find where the HTML, the JS/CSS, the API/database and the images are served from, measured from the visitors' country (collector in a browser there, or scan.py --from <CC>). Lab tools like PageSpeed run from Google data centers, not from the visitors' country, so they hide this cost. Record the round-trip time and the estimated seconds it adds.references/impact-analysis.md: which metric fails, which LCP phase dominates, seconds per finding.references/checklist.md with evidence - all 69. No silent skips: PASS / FAIL / N/A / UNKNOWN (+ what is missing).references/impact-analysis.md:<head>.server-location.md section 6 - never left as UNKNOWN, never moved to a lower tier because the origin's exact city is unknown.Keep it short; no generic advice that isn't backed by a measurement on this site.
Weekly roundup of top Claude Code skills, MCP servers, and AI coding tips.