Skip to content
Abundance Marketing Partners
Case StudiesPricingAboutContact
Start a Project Conversation
Abundance Marketing Partners

We build custom apps, AI workflows, internal tools, modern websites, and the delivery systems that make smart teams faster.

Start a Project Conversation

Services

  • Custom Apps
  • AI Workflows & Agents
  • Internal Tools & MCP
  • Modern Websites
  • Delivery Infrastructure

Company

  • About
  • Case Studies
  • Pricing
  • Service Areas
  • Articles
  • How We Work

Contact

  • Start a Project Conversation
  • hello@abundancepartners.app

Want the operating logic behind the work?
Read how we work

Local service areas

Salt Lake CitySandyDraperSouth JordanLehiProvo
See all service areas

© 2026 Abundance Marketing Partners LLC. All rights reserved.

Privacy PolicyTerms of Service
Case Studies

Proof that the modern build model produces better outcomes.

The strongest public proof right now is the SLC Bride rebuild, so we show the work in full: before-and-after screenshots, frozen baselines, benchmark data, and the stack shift underneath it.

View Current Site Archived Legacy Baseline

Featured proof

A cluttered legacy build became a faster, cleaner, AI-friendlier product experience.

The rebuild stripped out the clutter, clarified the value on first view, and moved the project onto a modern stack that is easier to improve over time.

61 -> 86

Mobile Lighthouse score

16.29s -> 4.18s

Largest Contentful Paint

3 median reruns

Benchmark method

SLC Bride

A clearer product story, a faster mobile experience, and a codebase built for the next round of work.

This project stripped away promo-heavy clutter, clarified the value proposition, and moved the experience onto a modern Next.js stack that is easier to extend than the legacy WordPress baseline.

Benchmarks captured with Lighthouse 12.8.2 on March 23, 2026.
Current SLC Bride homepage
Current experience
Clear product framing, useful hierarchy, and obvious next actions above the fold.
Legacy Salt Lake Bride homepage
Legacy baseline
Frozen before shutdown so the old UX and performance evidence can still be reviewed side by side.

What improved

  • 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.

Why the proof holds up

  • 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.
Performance Comparison

Frozen WordPress baseline vs current Next.js reruns.

This panel stays valid after legacy shutdown because the old numbers are frozen and timestamped while the current build can still be rerun.

3 runs per device, median aggregation
Mobile Benchmarks
Legacy WordPress baseline compared to the current Next.js build.
MetricLegacyCurrentDelta
Performance Score6186+25
LCP16.29s4.18s+12111
INPn/an/an/a
CLS0.150.00+0.1
TTFB72ms111ms-39
Desktop Benchmarks
Legacy WordPress baseline compared to the current Next.js build.
MetricLegacyCurrentDelta
Performance Score8499+15
LCP2.54s954ms+1588
INPn/an/an/a
CLS0.000.00-0.0
TTFB108ms103ms+4.7
Experience-level comparison
The difference is not just faster metrics. It is a cleaner buying experience.
AreaLegacy siteCurrent site
Primary messageGeneric headline with weak product framing.Clear value proposition tied to the real next step.
Hero actionsSearch exists, but the page quickly competes with multiple distractions.Search, browse, and planning-tool CTAs stay focused on the core job.
Overall feelA 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.

If the current stack is slowing the product down, that is usually fixable.

The work usually starts with a cleaner product story, a stronger hierarchy, and a better stack underneath so the next version is faster to improve too.

Start the Conversation Review Services