Skip to content

Home page LCP: get production Lighthouse mobile to 90+ #52

Closed

Description

@maxitect

Follow-up to #35 (PR #51, merged 13 November 2026). #35 cut the home page to 1.2 MB before the video and scored 93 on a local production build, but production Lighthouse mobile stayed at 85 with LCP 3.7 s, before and after the merge (numbers in #35's comments).

What the production run shows:

  • The LCP element is a text <span> in the home hero, not the video or an image. The breakdown gives about 320 ms time to first byte and 230 ms element render delay on an unthrottled trace; the simulated 3.7 s comes from what the text waits on (most likely the web font for the hero text and the scripts ahead of it)
  • The Netlify functions still run in the default region (US East), while the database is Neon main in Frankfurt
  • Most of the page weight is HLS segments: on Lighthouse's emulated connection the player picks the 1080p rung. That is the video working as intended, not something to cut

Deliverables

  • Find what delays the hero text's paint on production (font loading, font-display, preload, render-blocking CSS or scripts) and fix it without changing how the hero looks
  • Check whether the home page document is static or rendered per request on production, and make it static if it can be
  • The Netlify functions region moved to Frankfurt (eu-central-1), or a written note of why it can't be on this plan. The region is a Netlify UI setting: a user step, not code
  • Lighthouse mobile on production before and after, recorded in this issue

Acceptance criteria

  • Lighthouse mobile on production for / scores 90 or more, median of three runs, with LCP under 2.5 s
  • The home hero looks the same at 1280 and 390 px in English and French
  • The teaser still autoplays with its poster, through HLS first
  • No console errors or CSP violations on the home page

Depends on

#35

Activity

  1. self-assigned this
    on Nov 13, 2026
  2. maxitect commented on Nov 13, 2026

    @maxitect
    ContributorAuthor

    Lighthouse, production before (13 November 2026, Lighthouse 12, mobile)

    Two sets of three runs: scores 79 / 94 / 87 (median 87, LCP 3.7 s) and 90 / 91 / 81 (median 90, LCP 3.4 s). The LCP element is the footer copyright span, painted from the server HTML. Cause found: withPayload sends Critical-CH on every route, so Chrome re-requests the document on a first visit (427 ms on production, 5 ms locally). Fix and preview numbers (95 / 97 / 97, LCP 1.7 to 2.4 s) are in PR #54. The production re-run follows the merge. The functions region needs the Pro plan; details in the PR notes.

  3. maxitect commented on Nov 13, 2026

    @maxitect
    ContributorAuthor

    Lighthouse, after (production, mobile)

    Three runs on https://clarksbowlingclub.com/, 2026-11-13 00:59 UTC, Lighthouse 12.8.2 default mobile emulation, after PR #54 deployed (c2dc9bf).

    Run Performance LCP FCP TBT Speed Index
    1 97 2.4 s 1.0 s 0 ms 3.4 s
    2 94 2.2 s 1.0 s 0 ms 5.2 s
    3 95 2.2 s 1.0 s 0 ms 4.8 s

    Median 95, LCP 2.2 s: the criterion (90+, LCP under 2.5 s, median of three) is met. No console errors in any run. / no longer sends Critical-CH; /admin still does.

    The functions region stays in the default US East: moving it to Frankfurt needs a Pro plan, and the home page is served from the CDN cache, so it does not affect this score.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions