- results@spiltmedia.com
- 357 SW Kestor Drive, Port Saint Lucie, FL 34953
- Monday–Friday: 9AM–5PM
- 561-203-9290
CASE STUDY — WEBSITE PERFORMANCE REPAIR
We ran the same performance repair on our own WordPress site that we run for clients, and documented it on July 25, 2026. Mobile PageSpeed Performance moved from 63 to 76, Total Blocking Time dropped from 450ms to 80ms, our five-page average rose from 71 to 75.4, and transferred payload fell 38.31%. Lab scores fluctuate between runs, so below is the full account: the problem, the work, the methodology, and the results.
VERIFIED JULY 25, 2026
63 → 76
Official mobile Performance score
450 → 80 ms
Total Blocking Time
−38.31%
Transferred payload across five pages
THE FULL BREAKDOWN
A result matters more when you can see the starting point, the decisions made, and the systems that had to remain intact.
DOCUMENTED BEFORE / AFTER
63 → 76
Official mobile Performance
450 → 80 ms
Total Blocking Time
71 → 75.4
Five-page test average
−38.31%
Transferred payload
CASE STUDY 01
Before touching a client’s site, we ran the same performance repair on spiltmedia.com. Here’s exactly what happened on July 25, 2026.
Our WordPress site had accumulated the usual weight over time: a heavy custom menu, unused shared assets, tracking scripts firing on load, and images larger than they needed to be. Mobile performance was middling and blocking time was high enough to make the first interaction feel sluggish.
We replaced the heavy menu with Elementor’s native navigation, removed unused shared assets, deferred GoHighLevel tracking on mobile until a visitor interacts, limited review-widget overhead, and served better-sized images. We changed how the site loads, not what it does.
Google PageSpeed Insights mobile Performance rose from 63 to 76, and Total Blocking Time dropped from 450 ms to 80 ms. Across a five-page local test matrix, the average score climbed from 71 to 75.4 and total transferred payload fell 38.31%.
About the numbers: These are documented before-and-after captures from July 25, 2026, taken with official PageSpeed Insights and a local test matrix. Lab scores fluctuate with network and device conditions, so we treat these as a record of what we measured, not a permanent guarantee.
HOW WE WORK
Fast is easy if you’re willing to rip things out. The harder job is getting fast while keeping every system that makes the site work. That’s the part we’re careful about.
01
Every change is captured with real tooling on both ends. If we can’t show the number moving, we don’t claim the win.
02
Site Kit, Google Tag Manager, analytics, forms, conversion tracking, accessibility, and Cloudflare security were all kept in place and verified after the work.
03
We defer, resize, and trim overhead so the page feels lighter to a visitor while every feature it relied on still fires exactly when it should.
DESIGN WORK
Case studies cover the measurable side of what we do. If you want to see design and build work instead, that lives in our portfolio.
Tell us what’s slow, unclear, or underperforming, and we’ll tell you honestly whether we can move the number. The first conversation is free.
