Common Largest Contentful Paint mistakes that still ship

I keep a short list of LCP mistakes that survive design review. None of them are exotic. They come from treating a quiet desktop load on office Wi-Fi like a primary-content review. I still reach for curl first when something feels off. Curl will not tell me the hero arrived late. A real browser pass will.

SlaySlop's Largest Contentful Paint check "Reviews the loading signal for the primary page content." The mistakes below fight that observation point.

Outcome if you catch these early

You get tickets that name pages and suspect media instead of "make it faster somehow." Agencies that keep this boring tend to keep clients. The call stays about evidence, not vibes.

Boundaries

Read-only public scan. Permission required. Not a pentest. LCP sits under Performance next to CLS and Interaction readiness. Closing an LCP finding does not invent a good CLS. SlaySlop does not edit the target. Only scan hosts you are authorized to assess.

Mistake 1: oversized heroes without a delivery plan

A beautiful 4000px PNG shipped as the LCP element is still common. The design looked sharp. The live phone waited. Responsive images, modern formats, and sensible dimensions are boring. They work.

Mistake 2: discovering the LCP element is not the hero you thought

A cookie banner poster, a web font block, or a carousel slide you forgot can win as primary content. Measure on the live host. Do not declare victory from a design-tool export.

Mistake 3: local Lighthouse as production proof

A green lab run on a quiet laptop is useful. It is not the same as SlaySlop's live public check. Site compare language notes Lighthouse as a lab snapshot while SlaySlop—keeps checking a live URL over time. Use both tools; substitute neither.

Wait—product casing: SlaySlop keeps checking a live URL over time. Fix your strings.

Mistake 4: homepage-only confidence

Campaign landings with video posters often paint later than /. If your handoff script only opens the homepage, you shipped a glance.

# Permissioned: confirm which templates you are about to discuss
for path in "/" "/pricing" "/campaign"; do
  printf '%s => ' "$path"
  curl -sI "https://www.example.com$path" | awk 'NR==1{print}'
done

Mistake 5: collapsing every Performance weirdness into one ticket

LCP, CLS, interaction readiness, and viewport configuration are different sensors. Mixing them into "perf weirdness" wastes a week. Product language attaches evidence to findings. Borrow that packaging.

Mistake 6: fixing in the CDN purge only

Purging cache without changing the hero bytes brings the same late paint back on the next cold load. Temporary "swap the image for launch day" notes expire in silence unless a rescan exists.

Mistake 7: warm-cache demos

The war-room laptop already held the hero. Clients open a cold phone session. Measure the cold path you claim to ship.

LCP mistake watchlist
oversized_hero: yes|no
wrong_lcp_element: yes|no
local_only_lighthouse: yes|no
templates_covered: home|landing|article|mixed
cold_load_checked: yes|no
owner:

Mistake 8: fixing the ticket title only

Renaming a ticket from "LCP" to "Polish media" does not change the live bytes. Require a before/after note with the cited URL and the element that stopped being late.

Documentation culture is part of the bug

Sometimes the theme is fine and the runbook is wrong. The runbook says "always use the full-bleed brand still for every campaign." A tired engineer applies the runbook to every template. The mistake shipped as documentation culture. Fix the runbook in the same change window when you compress the hero. Otherwise the next launch reintroduces the late paint while "following the docs."

Happy path that avoids the list

1. Enumerate public templates in the SOW.
2. Run a permissioned SlaySlop scan.
3. Open LCP evidence on the cited pages.
4. Check CLS and Interaction readiness on the same pass.
5. Name owners and rescan dates before portal access goes out.

Editorial checklist for the Performance section

Before I accept a Performance handoff paragraph, I want three concrete nouns: the URL, the primary content candidate, and the sibling status for CLS. Vague adjectives like "snappy" do not survive client questionnaires.

I also refuse to treat silence on / after a fix as proof about /product/demo. Rescan the routes that mattered. Soft product mention only when it helps: ranked findings with page evidence beat a hallway memory of "felt fine."

Client calls that go sideways

The awkward call usually starts with "but PageSpeed said green." Bring the SlaySlop evidence. Open the cited URL on a phone if you can. Let the late primary content argue for you.

Related next step

Bring the SlaySlop evidence to the awkward call that starts with "but PageSpeed said green last month." Soft product mention only when it helps: ranked findings with page evidence beat a hallway memory of "felt fine."