1. The Danger of `loading="lazy"` on Hero Images
Content Management Systems universally apply native `loading="lazy"` attributes to all media attachments. When applied to above-the-fold hero assets, this instructs the browser to actively defer loading the largest visible element, artificially destroying Largest Contentful Paint (LCP) times and delaying the First Contentful Paint.
<!-- 1. Inject preload hint in the <head> -->
<link rel="preload" as="image" href="/hero-avif.avif" fetchpriority="high">
<!-- 2. Remove lazy loading and enforce high fetch priority -->
<img src="/hero-avif.avif" alt="Hero Banner" loading="eager" fetchpriority="high">2. Relational Database Query Bloat
Unindexed and bloated database queries—specifically `wp_options` queries with `autoload='yes'`—drive up Time to First Byte (TTFB) before the server even begins parsing the DOM. If TTFB exceeds 600ms, a sub-2.5s LCP becomes mathematically impossible regardless of frontend optimization.
-- Identify excessive autoloaded options causing TTFB bottlenecks
SELECT option_name, length(option_value) AS option_size
FROM wp_options
WHERE autoload='yes'
ORDER BY option_size DESC LIMIT 10;3. Edge Caching via Cloudflare Workers
The ultimate LCP tuning strategy is bypassing the origin server entirely for anonymous traffic. By deploying full-page HTML caching directly on CDN edge nodes (via Cloudflare Workers or Fastly), global TTFB drops to under 40 milliseconds.