Measured entry
uilayouts-mesh-gradient-background
background-effectaurora-meshmotion on file
A full-viewport, client-side React hero built around a custom animated Three.js shader. It ships as a shadcn registry component and includes its own heading, canvas, camera controls, lighting, environment, and noise pass. It depends on Three.js, React Three Fiber, Drei, React Three Postprocessing, and Three type declarations.



Measured
Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.
| Build | OK |
|---|---|
| Mount | OK |
| Console errors | 0 |
| Uncaught page errors | 0 |
| Horizontal overflow | flagged at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 300.6 KB (366.1 KB build, 65.5 KB baseline) |
| Bare mode | OK |
| Provider required | NO |
| Demo used | written from the component source API |
Verdict
It builds and mounts cleanly, but it is closer to a complete WebGL hero than a drop-in background. The hard-coded copy and viewport sizing need refactoring, and the observed overflow makes it a poor choice when responsive containment must work out of the box.
Use it if
- You want an immersive WebGL hero whose copy and green shader treatment will be customized in source.
- Your app already accepts the runtime and delivery cost of a Three.js scene for a prominent landing-page moment.
- You need pointer-responsive motion and are prepared to define reduced-motion behavior yourself.
Skip it if
- You need a reusable background that simply renders behind existing children; this component owns the page and hard-codes its heading.
- Horizontal overflow at responsive widths is unacceptable without additional layout work.
- Your bundle budget cannot justify a full Three.js, Fiber, Drei, and postprocessing stack for decoration.
- You need a CSS-only fallback, server-rendered output, or motion preferences handled out of the box.
Install
| Declared dependencies | three, @types/three, @react-three/fiber, @react-three/drei, @react-three/postprocessing |
|---|---|
| Missing on install | none |
| Bare install | builds and mounts without the shadcn-style helpers |
| Provider | no provider required in the harness |
Add Three.js, React Three Fiber, Drei, React Three Postprocessing, and the Three type declarations. Keep the component behind a client boundary and support its Tailwind utility classes or replace them with local CSS. Refactor the full-viewport wrapper and hard-coded heading before embedding it.
Source and credit
This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.
Author repository
github.com/ui-layouts/uilayoutsAlternatives
Other published entries for the background-effect pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- ruixen-loading-circlegradient-glow
- Renders
- YES
- A11y
- 0
- Gzip
- 17.7KB
- Bare
- pass
- Prov
- NO
- eldora-hacker-backgrounddark-futuristic
- Renders
- YES
- A11y
- 0
- Gzip
- 17.8KB
- Bare
- pass
- Prov
- NO
- ruixen-ripple-circlesgradient-glow
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- ruixen-dual-tone-rain-backgroundunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 18.4KB
- Bare
- pass
- Prov
- NO
- cultui-lightboardliquid-glass
- Renders
- YES
- A11y
- 0
- Gzip
- 19.6KB
- Bare
- pass
- Prov
- NO
- ruixen-mouse-sparkunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 20.6KB
- Bare
- pass
- Prov
- NO