Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / How a Five-Second Website Load Kills Your Customer Journey
Transcript
- Lucas: So there's this moment in every customer journey that almost never gets mapped. It happens before the visitor sees your hero image, before they read a headline, before they even know if they're in the right place. It's the time between clicking a link and the page actually rendering. Luna: The loading screen. Or worse, the loading spiral that never ends. Lucas: Exactly. And most journey maps treat that as a blank space. They start the journey at 'visitor lands on homepage.' But in reality, the experience starts with that first byte. And if that byte takes too long, the journey ends before it begins. Luna: We've all been there. Three seconds in and I'm gone. But how do you actually quantify that as a touchpoint? Lucas: Let me give you a concrete case. I was talking to a mid-market home goods brand, GreenLeaf Home. They sell sustainable kitchen products online. Their team had built this beautiful journey map—awareness, consideration, purchase, loyalty. They'd mapped every email, every social post, every product page. But they'd never mapped load time. Luna: Classic blind spot. It's technical, not marketing, so it falls through the cracks. Lucas: Right. Their average desktop load time was 4.7 seconds. Mobile was even worse—over 6 seconds. Their bounce rate on mobile was 67 percent. And their checkout completion rate was 22 percent below industry benchmark. They assumed it was a messaging problem. They kept rewriting copy, changing button colors. Luna: But the problem wasn't what they said. It was whether anyone stayed long enough to read it. Lucas: So we added a 'speed audit' layer to their existing journey map. We took each major touchpoint—Google Ads click, social link, email CTA, organic search result—and we measured the load time at that specific entry point. Then we color-coded it. Green under 2 seconds, yellow 2 to 4, red over 4. Luna: I bet the map looked like a Christmas tree. Mostly red. Lucas: Almost every entry point was red. The only green touchpoint was their thank-you page, which was a text-only confirmation. That told them something important: the speed problem wasn't their server or their hosting. It was the page content itself. Luna: So what was causing the bloat? Lucas: Two main culprits. First, they were serving full-resolution product images that were 3000 pixels wide. For a mobile user, that's downloading a 5-megabyte file to display on a 400-pixel screen. Second, they had six third-party scripts loading on every page—analytics, a chatbot, a review widget, a retargeting pixel, a live chat, and an A/B testing tool. Each script was blocking the page from rendering. Luna: So the page couldn't even start showing content until all those scripts finished talking to each other. That's the classic render-blocking issue. Lucas: Exactly. So we prioritized two fixes. First, automated image compression. They set a max width of 1200 pixels and used WebP format. That cut image payload by about 70 percent. Second, they deferred all non-critical scripts. The chatbot and the review widget could wait until after the page was interactive. The only script that loaded immediately was the core analytics. Luna: And the results? Lucas: Over eight weeks, average load time dropped to 1.8 seconds on desktop, 2.4 on mobile. Bounce rate on mobile fell from 67 percent to 36 percent. Checkout completion rate rose by 14 percent. And revenue per visitor—that's the metric that combines conversion rate and average order value—went up 14 percent as well. The fixes cost them maybe 40 hours of developer time. Luna: That's a massive ROI for something most marketers never even look at. But here's my question: why doesn't every journey map include a speed layer? It seems so obvious in hindsight. Lucas: I think it's because speed lives in a different silo. Marketing owns the journey map. Engineering owns page speed. And the two teams rarely share a meeting. The marketer's job is to get the visitor to the page. The engineer's job is to make the page load. But nobody owns what happens in between. Luna: So the touchpoint becomes a no-man's land. And the customer pays the price with their time. Lucas: There's also a conceptual problem. Most journey maps are built around actions—click, scroll, add to cart, purchase. But load time isn't an action. It's a condition. It's the environment in which the action happens. And conditions are harder to map because they're invisible until you measure them. Luna: But once you do measure them, they become actionable. GreenLeaf didn't need to change their messaging. They just needed to let their message arrive faster. Lucas: That's the key insight. Speed isn't just a technical metric. It's a touchpoint. It's the very first moment of truth in the customer journey. And if that touchpoint fails, no amount of clever copy or beautiful design will save you. Luna: Let's dig into the practical side. If someone listening wants to add a speed layer to their own journey map, where do they start? Lucas: First, pick your top three entry-point pages. Could be your homepage, a key product page, and your checkout page. Run each through a tool like Google's PageSpeed Insights or Lighthouse. That gives you a load time and a list of specific fixes. Luna: Then map that load time onto your existing journey. If your Google Ads click lands on a page that takes 5 seconds, that's a red touchpoint. You need to fix that before you optimize your ad copy. Lucas: Second, look at your most expensive pages. Not in terms of ad spend, but in terms of what they're supposed to do. If your checkout page is slow, you're leaking revenue at the exact moment the customer is ready to buy. That's the highest-leverage fix. Luna: And one thing I'd add: don't just look at average load time. Look at the distribution. If half your users experience 2 seconds and half experience 8 seconds, your average says 5 seconds—but the experience for that half is terrible. You want to look at the 90th percentile, or better yet, the load time for the slowest 10 percent of users. Lucas: Great point. Especially on mobile where network conditions vary wildly. A user on 5G might get your page in 1 second. A user on 3G in a subway might take 12 seconds. The journey map should reflect both realities. Luna: And if this episode has sparked something you've actually used in your own work, maybe a speed audit you ran or a page you optimized, that's exactly the kind of thing that keeps these conversations going. This show stays free because listeners who find value in it occasionally throw a few dollars our way. If today was useful, you can find us at buy me a coffee dot com slash fexingo. No pressure, just a way to keep the lights on. Lucas: Yeah, and it directly funds the research and the tools we use to find cases like GreenLeaf. So if you've ever gotten a tip you applied, that's the link. Otherwise, let's get back to the map. Luna: So you've identified your slow entry points. What's the next step after the audit? Lucas: You prioritize based on impact and effort. Image compression is usually the quickest win. It's a one-time configuration change in your content management system or your image CDN. Next, look at third-party scripts. Every script you add is a promise to the browser: 'Wait for me before you show the page.' You need to ask whether each script is truly necessary on every page. Luna: And the answer is almost always no. The chatbot doesn't need to load on a blog post. The A/B testing tool doesn't need to run on the thank-you page. Lucas: Exactly. Load scripts conditionally. Only on pages where they're actually used. And defer everything that isn't blocking the critical rendering path. Luna: One thing I want to emphasize: this isn't just about technical optimization. It's about respecting the customer's time. Every second of load time is a tax the customer pays before they can even evaluate your offer. If you can reduce that tax, you're not just improving a metric—you're improving the relationship. Lucas: That's a beautiful way to put it. And it's why speed belongs in the journey map. Because the journey isn't just about the touchpoints you control. It's about the experience the customer has at each one. And the first experience is always speed. Luna: So final takeaway: add a speed layer to your journey map this week. Pick three entry pages, measure them, and fix the one that's bleeding the most revenue. It might be the highest roi change you make all quarter. Lucas: And if you do, drop us a note. We'd love to feature your before and after in a future episode. For now, I'm Lucas. Luna: And I'm Luna. See you next time.