Repository navigation
Closed
Labels
enhancementNew feature or requestNew feature or request
Description
Performance audit run on 11 November 2026 with Lighthouse (mobile) against production. The teaser video and missing metadataBase are in #31; serving content from the server instead of fetching it in the browser is #27. This ticket covers the rest.
| Page | Performance | LCP | Blocking time | Layout shift | Page weight |
|---|---|---|---|---|---|
/ |
73 | 3.3 s | 580 ms | 0 | 16,800 KB |
/tour |
80 | 4.7 s | 10 ms | 0.107 | 416 KB |
Accessibility and SEO score 100 on both.
Deliverables
Home page
SpinningLogoimports all of three.js statically (src/app/_components/HomeClient.tsx:6), a 540 KB chunk that causes most of the 580 ms blocking time. Load it after the page is interactive, and not at all when reduced motion is on- The four hologram textures in
public/hologram/are PNGs of 182 to 316 KB each, about 1 MB together. Convert to WebP or AVIF - The animation loop keeps running when the tab is hidden (
SpinningLogo.tsx:174); pause it public/images/home.pngis 14 MB. It goes through the image optimiser, but the source should be a JPEG of a few hundred KB
Every page
- Functions run in
us-east-2(Ohio) while the audience is in France; the home document took 630 ms to respond. Move the functions region to Europe - Files in
public/are served withcache-control: max-age=0, must-revalidate, including the 34 MB video. Give versioned media a long cache lifetime - The carousel on the About page declares images as 5000 by 500 (
src/components/ui/Carousel.tsx:84-85) with nosizes, so phones download desktop-sized images from sources of 0.9 to 2 MB. Set real dimensions andsizes src/app/favicon.icois 197 KB;icon.svgalready exists- The Jost font loads nine weights in normal and italic (
src/app/layout.tsx:18-24); load only the weights the site uses - Spotify sets
loading="lazy"on its iframe; YouTube and Bandcamp do not (src/app/music/_components/)
After #27
/tourhas a layout shift of 0.107 and an LCP of 4.7 s because content appears after a browser fetch replaces "Loading...". Re-measure once Serve Google Sheets content from the server with Cache Components #27 ships; it should remove both
Acceptance criteria
- Lighthouse mobile on production, recorded in this issue before and after:
/performance 90 or more with blocking time under 200 ms;/tourLCP under 2.5 s and layout shift under 0.1 - The home page transfers under 3 MB before the video starts
- The spinning logo still appears and animates on desktop and mobile, and is absent with reduced motion on
- The home document responds in under 300 ms from a European location
- A repeat visit loads images and video from the browser cache
- All pages look the same as before on desktop and mobile
Depends on
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request
Activity
maxitect commentedon Nov 12, 2026
Adaptive streaming for the home page teaser (decided 12 November 2026)
#31 (PR #45) re-encodes the teaser at full 1920x818 in three files: AV1 (7.3 MB), HEVC (7.5 MB) for Apple devices without AV1, and an H.264 fallback (26.6 MB). It autoplays as the home page hero and stays that way.
Add HLS on top of that so slow connections start quickly at a lower quality and step up as bandwidth allows:
hls.js, loaded only where native HLS is missingmaxitect commentedon Nov 13, 2026
Lighthouse, before (production, mobile)
Home page
https://clarksbowlingclub.com/, run 2026-11-13 00:17 UTC with Lighthouse 12.8.2 (default mobile emulation, headless Chrome), before PR #51 merges. Production at this point includes #31 (AV1/HEVC teaser), #33 (Payload), #34 (CSP) and #29 (calendar).The run right after #31 scored 90 with LCP 3.1 s; single Lighthouse runs vary by a few points. The "after" run follows once #51 deploys.
maxitect commentedon Nov 13, 2026
Lighthouse, after (production, mobile)
Run 2026-11-13 00:21 UTC, Lighthouse 12.8.2, default mobile emulation, after PR #51 deployed (
19acbc6).The criterion "90+ on production" is not met. The local production build scored 93, but production stays at 85.
<span>, not the video or an image, so the image and three.js changes don't move it.The next thing to look at is the render delay of the LCP text (font loading for the hero text) once the region is moved.