SLC Bride: a clearer path to wedding planning.
We rebuilt a crowded wedding directory so visitors could find vendors and planning tools more easily. See what changed in the design and how mobile loading improved.
Historical Lighthouse lab results captured on March 23, 2026. Inquiry and revenue changes were not measured in this case study.
Measured results at a glance
61 → 86
Mobile Lighthouse score
Frozen legacy homepage compared with the rebuilt homepage.
16.29 → 4.18
Largest Contentful Paint, in seconds
The first useful screen arrives far faster on mobile.
3median reruns
How we measured
Repeated Lighthouse runs for each source and device profile.
Simplify the homepage and improve mobile loading.
The scope covered homepage messaging, navigation to search and planning tools, and a rebuild from WordPress to Next.js. The before-and-after views below show the design changes.
Benchmarks captured with Lighthouse 12.8.2 on March 23, 2026.
Current experience
Clear product framing, useful hierarchy, and obvious next actions above the fold.
Legacy baseline
Frozen before shutdown so the old UX and performance evidence can still be reviewed side by side.
A homepage that knows its job.
- The value proposition is visible immediately instead of hiding behind clutter.
- Primary actions stay focused on the job the buyer came to do.
- The homepage reads like a guided product path instead of a stitched content pile.
The method is public.
- Legacy baseline frozen on March 23, 2026 before shutdown.
- 3 Lighthouse runs per source and device profile with median aggregation.
- Current Next.js benchmarks can be rerun without needing the legacy site online.
Frozen WordPress baseline vs current Next.js reruns.
These are archived lab measurements from the capture date above, compared with a frozen legacy baseline. They describe this test run, not current visitor experience or sales performance.
Mobile benchmarks
Legacy WordPress baseline compared to the current Next.js build. A positive change is better.
| Metric | Legacy | Current | Change |
|---|---|---|---|
| Performance score | 61 | 86 | +25 pts |
| LCP | 16.29s | 4.18s | +12.11s |
| INP | n/a | n/a | n/a |
| CLS | 0.15 | 0.00 | +0.15 |
| TTFB | 72ms | 111ms | -39ms |
Desktop benchmarks
Legacy WordPress baseline compared to the current Next.js build. A positive change is better.
| Metric | Legacy | Current | Change |
|---|---|---|---|
| Performance score | 84 | 99 | +15 pts |
| LCP | 2.54s | 954ms | +1.59s |
| INP | n/a | n/a | n/a |
| CLS | 0.00 | 0.00 | 0.00 |
| TTFB | 108ms | 103ms | +5ms |
Experience-level comparison
Design changes shown in the screenshots above.
| Area | Legacy site | Current site |
|---|---|---|
| Primary message | Generic headline with weak product framing. | Clear value proposition tied to the real next step. |
| Hero actions | Search exists, but the page quickly competes with multiple distractions. | Search, browse, and planning-tool CTAs stay focused on the core job. |
| Overall feel | A directory homepage with too many competing priorities. | A cleaner first impression that feels intentional and easier to trust. |
Evidence: download the frozen legacy report or review raw Lighthouse JSON files under public/case-studies/benchmarks/slc-bride/raw.
Could your website make the next step easier?
Share your current site and where visitors get stuck. We will recommend a focused next step for improving the experience. Asking is free, and any fee is quoted before work starts.