Measured entry
efferd-cta-2
A static, centered call-to-action strip with a headline, short supporting copy, and paired sales and signup buttons. It ships as a shadcn registry block and relies on Tailwind utility classes, theme tokens, a local shadcn Button component, its utility helper, and a Lucide arrow icon.



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 | 32.2 KB (97.6 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
BARE BUILD
✗ Build failed in 1m 28s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/components/ui/button.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A clean, adaptable CTA for an existing shadcn codebase, but it is mislabeled as a contact form and ships with no button behavior. It needs a shadcn-style setup because the bare project cannot resolve the Button utility import.
Use it if
- You need a compact CTA between page sections or near the end of a landing page.
- Your project already uses shadcn conventions and can supply the shared Button component.
- You want separate actions for contacting sales and starting a signup flow.
Skip it if
- You need an actual contact form with fields, validation, and submission handling.
- Your design system does not use Tailwind theme tokens or shadcn component conventions.
- You need working navigation or event handling without wiring the buttons yourself.
- You want a dependency-light CTA built only from native elements.
Install
| Declared dependencies | radix-ui |
|---|---|
| Missing on install | none |
| Bare install | fails once the shadcn-style helpers are removed, so it needs that setup |
| Provider | no provider required in the harness |
In a non-shadcn project, add Tailwind with the expected color tokens, configure the at-sign source alias, provide a compatible Button component and its utility helper under the expected paths, install the Lucide and Radix dependencies, and connect both buttons to real actions.
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/shabanhr/efferd-uiAlternatives
Other published entries for the contact-form pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- hyperui-contact-forms-1editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.4KB
- Bare
- pass
- Prov
- NO
- hyperui-contact-forms-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.5KB
- Bare
- pass
- Prov
- NO
- hyperui-contact-forms-4editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.5KB
- Bare
- pass
- Prov
- NO
- hyperui-contact-forms-3editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.6KB
- Bare
- pass
- Prov
- NO
- hyperui-contact-forms-5editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 18.4KB
- Bare
- pass
- Prov
- NO
- efferd-contact-2minimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 30.4KB
- Bare
- fail
- Prov
- NO