Building a 3D website that stays useful when the scene cannot load
A 3D scene can give a website a strong identity. It should not decide whether a visitor can read the company name, follow a project link, or send an enquiry. The scene and the useful website need separate responsibilities.
On Twin Chiefs, the floating chess kings are a visual layer. The headings, project descriptions, navigation, and contact form remain ordinary HTML. That separation is the starting point for a more resilient experience, rather than a fallback added at the end.
Keep essential content outside the canvas
Use semantic headings, links, and form controls for the things a person must understand or operate. A canvas can draw text, but drawing a label does not automatically provide the semantics or keyboard behavior of an HTML control.
Treat decorative geometry as an enhancement. If the WebGL scene is unavailable, the page should still communicate its purpose and offer the same routes to work and contact information. If a scene is interactive and conveys essential information, it needs an accessible alternative designed for that specific interaction.
Budget for the model and the renderer
Check the exported asset instead of judging performance from the source file alone. Triangle count, texture size, material complexity, and screen resolution all contribute to the result. A small download can still require an expensive frame, and a simple-looking scene can include unnecessary geometry.
The chess source used here is 572,144 bytes with 17,500 triangles. The compressed desktop model is 103,912 bytes with that geometry retained; the mobile variant is 63,800 bytes with 8,000 triangles. These are asset sizes from this project's exports, not a promise about total page weight or frame rate on every device.
The renderer also caps pixel density and pauses rendering when the document is hidden. Test those choices on the devices you care about: lowering an asset's byte count and lowering the work needed to draw it are related but different tasks.
Respect reduced motion throughout the page
A reduced-motion preference should affect the full experience: large scroll-linked movement, pinned sections, entrance animations, and the scene itself. Disabling one animated element while keeping an elaborate page transition leaves the main problem in place.
For this site, reduced motion disables the WebGL scene, smooth scrolling, pinning, and text reveals. The Work collection keeps ordinary navigation. Motion preferences can change while a page is open, so the setup also needs to clean up and restore the simpler layout when that happens.
Give loading and failure different jobs
A loading screen should explain a short transition, not trap the visitor behind a dependency. Decide what must be ready before reveal, what can load later, and when the page should continue with a simpler presentation.
If the design locks scrolling during its opening transition, lock the document consistently and release it during cleanup as well as normal completion. Test wheel, touch, and keyboard input. A hidden overlay with a leftover scroll lock is still a broken page.
- Test a cold load and a repeat visit with cached files.
- Try a narrow screen, reduced motion, and unavailable WebGL.
- Check keyboard access to navigation and contact controls.
- Move between routes and resize while a pinned section is active.
- Verify a failed visual layer does not remove the page's main content.
Measure the useful experience
Use performance measurements alongside visual checks. Core Web Vitals cover loading, responsiveness, and visual stability; a good score still does not replace checking whether someone can complete the task. Compare equivalent conditions, and distinguish a local lab measurement from field data collected from real visits.
A strong visual identity is more convincing when the basic interactions are dependable. Keep the scene deliberate, make the HTML useful on its own, and test the states that a polished desktop demo tends to hide.
Further reading
See the products behind these notes in our work, or start a conversation about a project of your own.