Lume
Show the fire without punishing the phone.

- Problem
- Lume is wood-fired chef's cuisine, with an eight-course tasting menu and service Thursday through Saturday. The fire is the selling point, and fire is shown on video, which is exactly what weighs the most and behaves the worst on a poor connection.
- Design decision
- Load the video only when the visitor can afford it. The hero starts with a static WebP image that's already visible, and the nearly two-megabyte video isn't downloaded by default on any visit.
- Technique
- A hero video with the device's consent. The video ships with preload set to none. load() is only called if the visitor isn't asking for less motion and doesn't have data saver on. In every other case the element is removed from the DOM and the image stays. The video only becomes visible after loadeddata, so there's no flicker, and if loading fails it removes itself.
- Expected result
- The hero weighs what a 76KB WebP weighs for anyone arriving on limited data, and turns into moving fire for anyone with the connection to afford it. The same page serves both without punishing either.
Lighthouse · mobile
88 Performance
100 Accessibility
100 Best practices
100 SEO
Lighthouse 13 on mobile, median of three runs · September 2026.
How it was made
The hero image is served with picture, WebP with a JPG fallback, high fetchpriority and a preload in the head. It carries Schema.org JSON-LD markup of type Restaurant with hours, cuisine and price range. There's fallback navigation inside noscript, so the site stays navigable without JavaScript. Skip link, visible focus in the brand amber and a prefers-reduced-motion block that turns off every transition. Reservations open WhatsApp with the message pre-filled instead of relying on a backend.