cwv-optimizer

Diagnose Core Web Vitals issues on Adobe Edge Delivery Services pages.

Updated May 14, 2026

Search Tags:#performance audit #core web vitals #web optimization #eds #lcp #inp #cls

Ready to run

npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill cwv-optimizer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cwv-optimizer
Source: https://github.com/Focus-GTS/eds-content-ops-skills/tree/main/skills/cwv-optimizer
Command: npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill cwv-optimizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It diagnoses and fixes Core Web Vitals regressions on Adobe Edge Delivery Services (EDS) pages by identifying EDS-specific causes and turning them into actionable code changes.

Core Features & Use Cases

EDS-aware CWV diagnostics: Pinpoints likely LCP, CLS, and INP causes using the EDS performance model (including the 100KB LCP budget and E-L-D loading phases).
Targeted fix recommendations with impact: Produces specific, implementable remediation steps and estimates before/after improvements for each recommendation.
Resource and block forensics: Audits eager vs delayed resource assignment, image dimension/optimization issues (including createOptimizedPicture() behaviors), and third-party script loading patterns.
Before/after verification guidance: Guides users to validate changes by re-running Lighthouse and monitoring real-user results via OpTel.

Quick Start

Ask your AI agent to run cwv-optimizer for your page URL and produce an EDS-specific CWV fix plan with estimated before/after projections.

Frequently Asked Questions about cwv-optimizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix Core Web Vitals regressions on Adobe Edge Delivery Services?▼

Fix Core Web Vitals regressions on Adobe Edge Delivery Services by diagnosing LCP, CLS, and INP failure modes tied to EDS-specific loading phases. The process audits eager and delayed resource assignments, image dimensions, and third-party scripts to produce a ranked, quantified fix report.

Why does my EDS page have a poor LCP score despite following standard image optimization?▼

A poor LCP score on EDS pages often stems from exceeding the 100KB LCP budget or misconfigured createOptimizedPicture() behaviors. Analyzing the eager loading phase and verifying image dimensions against EDS performance budgets isolates the specific cause.

What is the best way to diagnose INP issues caused by third-party scripts on EDS?▼

Diagnose INP issues caused by third-party scripts on EDS through JavaScript profiling and a complete script inventory. Checking delayed.js conventions and loading patterns identifies what blocks main thread interactions during the delayed loading phase.

How do I audit eager versus delayed resource assignment for Core Web Vitals on EDS?▼

Audit eager versus delayed resource assignment for EDS by evaluating the E-L-D loading phases against your performance budgets. This forensics process identifies misallocated resources causing layout shifts and delayed LCP elements.

Can I use Lighthouse baseline measurements to project Core Web Vitals improvements on EDS?▼

Use a baseline Lighthouse measurement to project Core Web Vitals improvements on EDS by quantifying the estimated before and after impact of each fix. Re-running Lighthouse validates changes before monitoring real-user results via OpTel.

What should I do when generic Core Web Vitals guidance does not fix my EDS page regressions?▼

When generic Core Web Vitals guidance does not fix EDS page regressions, apply an EDS-aware diagnostic workflow. This targets OpTel-flagged problems by auditing EDS-specific loading phases, createOptimizedPicture() behaviors, and delayed.js conventions.