Module 1: Performance Foundations

Why Speed Equals Revenue

Every person who visits a website is making a quick, mostly unconscious judgement: is this worth waiting for? When a page takes too long to show anything useful, many visitors simply leave, and they rarely come back to tell you why. For a business, that silent exit is lost revenue: a sale that did not happen, a lead form that was never filled in, an article that was never read. This course teaches you how to find and fix the causes of slowness, but first you need to understand why speed deserves your time and your budget.

How slowness costs money

Speed affects a business in several connected ways:

• Abandonment. A visitor who sees a blank screen or a page that jumps around while loading is more likely to press the back button. On mobile data, where connections are slower and sometimes paid per megabyte, patience is even shorter.
• Conversion. Even visitors who stay are affected. Slow product pages, sluggish "Add to cart" buttons and checkout steps that freeze for a second all create friction. Friction reduces the share of visitors who complete a purchase or enquiry.
• Search visibility. Google uses page experience signals, including the Core Web Vitals you will study in the next lesson, as part of its ranking systems. Speed will not rescue poor content, but between two similar pages, the faster and more stable one has an advantage.
• Cost of acquisition. If you pay for ads, every visitor who leaves before the page loads is money spent for nothing. A faster landing page makes the same advertising budget go further.
• Brand trust. A slow or glitchy site feels unreliable. For a payment, lending or e-commerce business, that impression directly affects whether people are willing to share their details.

Many large companies have published case studies linking speed improvements to better business results. You will find them easily online, but be careful about copying their numbers into your own reports. Results depend on the audience, device mix and type of site. The honest approach is to measure your own site, make a change, and compare.

Who your users really are

Developers often test on a fast laptop connected to office fibre. Your users may be on a mid-range Android phone, on a 4G connection that drops to 3G on a matatu, with a dozen other apps running in the background. A page that feels instant on your machine can take many seconds on theirs. Two habits fix this blind spot:

1. Check your analytics for the real device and browser mix. If most of your traffic is mobile, mobile performance is your performance.
2. Test with throttling. Browser developer tools can simulate a slower CPU and network. Use them every time you assess a page.

Worked example: putting a value on speed

Imagine a Nairobi online electronics shop. These figures are purely hypothetical, to show the reasoning. The shop gets 30,000 visits a month to product pages, 2 percent of visits result in an order, and the average order is KES 8,000. Monthly revenue from these pages is therefore 30,000 x 0.02 x 8,000 = KES 4,800,000.

The owner suspects slow product pages are losing customers. Rather than guess, the team does three things:

1. Records the current conversion rate and the 75th percentile load time from real users for four weeks.
2. Compresses the oversized product photos, removes an unused chat widget and adds caching.
3. Records the same figures for the next four weeks, checking that nothing else changed (no big sale, no new ad campaign).

If conversion moves from 2.0 to 2.2 percent with the same traffic, revenue rises to 30,000 x 0.022 x 8,000 = KES 5,280,000, an extra KES 480,000 a month. That is the kind of argument that gets performance work approved. Notice that the value came from the shop's own data, not from someone else's case study.

Speed is a feature, not a finish

Performance is not something you fix once. New images are uploaded, marketing adds tracking scripts, developers add libraries. Without attention, every site slowly gets heavier. That is why this course ends with performance budgets, testing in continuous integration and building a performance culture: the goal is a site that stays fast.

Common mistakes to avoid

• Testing only on your own device. Your laptop is not your customer's phone.
• Chasing a score instead of users. A perfect lab score means little if real visitors still wait. Focus on what people experience.
• Quoting borrowed statistics as fact. Use other companies' results as motivation, but justify work with your own measurements.
• Optimising the wrong pages. Start with the pages that carry money: landing pages, product pages, checkout and sign-up.
• Treating speed as purely technical. Content editors, marketers and managers all affect page weight. Everyone needs to understand why it matters.