Skip to content

Example: rebuilding a slow carrier site that paid traffic abandons

Illustrative example — not a client result. How we would approach a logistics site that takes nine seconds to render, and the metrics a rebuild would target.

May 20, 20266 min readTexas Solutions engineering · Web development

Illustrative example — not a client result. This is a hypothetical scenario written to show our approach. The figures are example targets, not results achieved for a client.

The scenario

Imagine a regional logistics operator running 40 vehicles with a site that takes nine seconds to render on a mid-range phone. They spend on paid search, and a large share of those clicks bounce before the hero image appears. Enquiries go to a shared mailbox with no CRM behind them, and no content change can happen without a developer.

What we would do

  • Rebuild on Next.js with a token-driven design system and a performance budget enforced in continuous integration.
  • Model every page block in the CMS, including service pricing, so the marketing team can publish without a deploy.
  • Wire enquiry forms into the CRM with campaign, source and page attribution attached to each lead.
  • Add a quote calculator to the carrier landing page so visitors can get a number before committing to a conversation.

Example targets after 90 days

Example metricExample starting pointExample target
Mobile Lighthouse4196
Largest Contentful Paint8.9s1.6s
Enquiries per month1138
Cost per enquiry$187$61

What would matter most

Speed work drives enquiry volume, but CRM attribution drives cost. Once every enquiry carries its source, the paid budget can move toward the campaigns that produce booked work rather than the ones that produce form fills.

Case studyIllustrative examplePerformanceLogistics

Turn the reading into a number

The calculator uses the same published ranges referenced in these articles. A few questions and you have a figure in US dollars.