Measured entry
ruixen-load-ripple
badgeunclassifiedmotion on file
A client-side React ripple loader made from nested, staggered circles. It ships as a shadcn registry UI file with accompanying animation keyframes, and relies on React plus Tailwind utility and arbitrary-animation support. It has no separate runtime package or provider.



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 | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 17.9 KB (83.3 KB build, 65.4 KB baseline) |
| Bare mode | OK |
| Provider required | NO |
| Demo used | written from the component source API |
Verdict
A focused, dependency-light loader that builds and mounts cleanly, stays within its viewport, and introduces no detected accessibility violations. It is a solid fit for decorative waiting states, but teams still need to supply semantic loading feedback and reduced-motion behavior where those matter.
Use it if
- You need a decorative loading indicator for a spacious panel, empty state, or transition screen.
- Your React app already uses Tailwind and can include the registry-provided keyframes.
- You want a neutral loader that works against both light and dark surfaces.
Skip it if
- You need determinate progress, status text, or an accessible loading announcement without adding that behavior yourself.
- Your interface must honor reduced-motion preferences without modifying the animation classes.
- You need a compact inline indicator, since the component uses a fixed square footprint.
- Your project does not use Tailwind and you do not want to translate its utility classes into local CSS.
Install
| Declared dependencies | none declared |
|---|---|
| Missing on install | none |
| Bare install | builds and mounts without the shadcn-style helpers |
| Provider | no provider required in the harness |
In a non-shadcn project, add the React component manually, ensure Tailwind scans its file and supports the utility syntax, and copy the load-ripple keyframes into your global stylesheet or Tailwind configuration. Add client-component handling if your framework distinguishes server and client modules.
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/ruixenui/ruixen.comAlternatives
Other published entries for the badge pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- neu-badgeneumorphism
- Renders
- YES
- A11y
- 0
- Gzip
- 17.5KB
- Bare
- pass
- Prov
- NO
- clay-badgeclaymorphism
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- kibo-listminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 42.4KB
- Bare
- pass
- Prov
- NO
- ruixen-blurred-stagger-textunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 58.1KB
- Bare
- pass
- Prov
- NO
- tripled-auto-revealing-heading-shadcnuiminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 58.3KB
- Bare
- pass
- Prov
- NO
- tripled-dynamic-tag-cloud-shadcnuiminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 61.0KB
- Bare
- pass
- Prov
- NO