From hacked WordPress to 100 on every test.
A wedding florist in Idaho Falls, with destination work in Jackson Hole and Grand Teton. The WordPress site was hacked. We moved her off it.
Hacked WordPress.
Lost weddings.
Kindryn runs a floral studio in Southeast Idaho and the Tetons. Garden-inspired wedding work. Couples come for the flowers. The old website did not look like any of that.
The WordPress install had been hacked. Images missing, text broken, slow to load. A wedding inquiry is a high-trust moment. The site was costing her bookings.
- A compromised WordPress install. Time for a clean start, not another plugin.
- Slow pages. Visitors waited on a heavy WordPress homepage.
- A dated look. The theme did not match the studio or the flowers.
- A plugin stack to babysit. Updates, logins, and PHP sitting on the public web.
What Kindryn
asked for.
She wanted a site that feels like walking into the studio. Calm. Photo-led. Her work first, not a florist theme trying to look fancy.
Couples decide in a few seconds. The homepage had to earn trust right away. Her logo stays. The type stays quiet. The flowers do the talking.
She still needed a way to add a new wedding to the gallery without waiting on a developer.
- A look that matches the work. Editorial. Not a template with stock flowers.
- Photography first. Neutral type. Color lives in the images.
- Her mark, in black. The script logo she already had.
- She can update it. New photos and copy without opening code.
Same florist.
A site that matches the work.
* This is how we found the site after the malicious hijack. It was not pretty. A lot of images and text were missing.
Oh My Gosh this is soo great. It is exactly what I was looking for!
The result: Couples now see a site that looks like the work. Inquiries are up. The hijacked install is offline. Kindryn updates her own pages.
Built to stay
out of the way.
Static public site
Visitors get prebuilt HTML. No WordPress, no PHP, no login on the public domain.
Editor that stays private
Kindryn edits in Sanity. Content publishes to the build. The CMS never sits on bouquetlavie.com.
Her site. Her pages.
No WordPress maze.
Kindryn opens Sanity and sees her pages. Home. Packages. Gallery. About. Contact. Click a page, edit the fields, publish. No plugins to navigate. No theme maze. Photos, copy, and inquiry logs all in one place.
Add a wedding to the gallery without calling a developer. Change a headline without hunting through WordPress settings. The editor matches the business. Visitors still get static files.
100 across
the board.
Desktop scores from the old host and the new site. Mobile PageSpeed on the live site is 100 in all four.
Desktop homepage
LCP 3.2s · first byte 2.5s · 2.8 MB transfer
LCP 0.6s · first byte 20ms · 0.3 MB transfer
A site that cannot
be hacked again.
Static files on the public domain. The editor sits elsewhere. No login forms. No plugin updates. Nothing to compromise.
- No WordPress or PHP on the live site
- Editor kept private, off bouquetlavie.com
- Security headers block common attacks
- Old compromised install shut down
From hacked WordPress
to a site worth showing.
A wedding florist site built to match the work, stay fast, and stay secure.
Want a published example? Start here.
Hacked WordPress site?
Time for a clean start.
We move you off WordPress when the install is hacked, slow, or held together with plugins. You keep a site you can edit. The public pages stay fast, with no login form sitting on your domain.