How Websites Actually Work — Lesson 5
Speed, Security, and Performance
Learning Objectives
- 1Explain how caching and CDNs improve website speed.
- 2Understand why page speed affects conversion and search ranking.
- 3Create a practical website launch and ownership checklist.
Why speed is a business metric
Website speed directly affects revenue. Research consistently shows that each additional second of load time increases bounce rates and decreases conversions. A site that loads in one second converts at roughly twice the rate of a site that loads in five seconds. For e-commerce sites, the relationship between speed and revenue is even more dramatic.
Google uses page speed as a ranking factor in search results. Slow sites rank lower, which means less organic traffic, which means more dependence on paid advertising. Speed is not just a user experience issue — it is a search visibility and customer acquisition issue.
Speed problems can come from many sources: large unoptimized images, slow hosting, too many third-party scripts, unminified code, lack of caching, distant server locations, poorly optimized databases, or excessive plugin overhead. Diagnosing speed issues requires understanding which part of the system is the bottleneck.
Caching: saving copies for faster delivery
Caching stores copies of website files so they do not need to be regenerated or re-downloaded on every visit. Browser caching saves files on the visitor device. Server caching stores pre-built pages so the server does not rebuild them for every request. CDN caching stores copies at locations around the world.
Effective caching dramatically improves performance. A page that takes two seconds to generate from the database might serve in 50 milliseconds from cache. For content that does not change frequently, caching is one of the most impactful performance improvements available.
The tradeoff is that cached content can become stale. If you update your website but visitors see the old version, the cache is serving outdated content. Cache invalidation — telling caches to discard old copies and fetch fresh ones — is an important part of any content update process.
Cache troubleshooting
If you updated your website but visitors still see the old version, caching is the most likely cause. Ask: Was the cache cleared? How long until it expires? Is there a CDN cache in front of the server cache?
CDNs: global delivery networks
A CDN (Content Delivery Network) is a network of servers distributed across multiple geographic locations. When a visitor requests your website, the CDN serves content from the server closest to them. A visitor in Tokyo gets files from a Tokyo server rather than waiting for them to travel from New York.
CDNs improve speed for geographically distributed audiences, protect against traffic spikes by distributing load across many servers, and often include additional security features like DDoS protection. Even small websites benefit from CDN speed improvements.
Common CDN providers include Cloudflare, Fastly, AWS CloudFront, and Vercel Edge Network. Many modern hosting platforms include CDN functionality by default. If your hosting does not include a CDN and you have visitors from multiple regions, adding one is usually a straightforward and high-impact improvement.
The website launch and ownership checklist
Before any website launch, you should verify a checklist of items that go beyond visual design. Domain access and renewal should be documented. DNS records should be confirmed. SSL should be active and auto-renewing. Hosting account credentials should be accessible to the business. Analytics and conversion tracking should be installed and tested.
All forms should be tested with real submissions. Email delivery from the website should be verified. Mobile experience should be checked on actual devices. Redirects from old URLs should be in place. Backups should be configured and a restore should be tested. Third-party integrations should be verified.
After launch, the business should own credentials for the domain registrar, hosting provider, CMS admin, analytics platform, and any other critical service. Ownership should not depend on a single vendor, developer, or employee. Documentation should exist in a shared location.
This is not glamorous work, but it is the work that separates a smooth launch from a chaotic one. Most launch-day crises come from items on this checklist that were assumed to be handled but were never explicitly verified.
Case Study
The invisible redesign
Situation
A marketing team invested $25,000 in a website redesign with beautiful new visuals. After launch, their Google PageSpeed score dropped from 85 to 42. Organic traffic declined 30% over the following three months.
Analysis
The new design used unoptimized high-resolution images, loaded seven third-party fonts, included four analytics and marketing scripts, and had no caching configured. The site looked better but performed dramatically worse. Nobody had tested page speed before launch.
Takeaway
Visual quality and performance are not competing goals, but they require deliberate attention to both. Always measure page speed before and after any major website change.
Reflection Questions
- 1. Have you ever tested your website speed using a tool like Google PageSpeed Insights? What score did it receive?
- 2. Does your organization have a documented website launch checklist? If not, what items would you include based on this lesson?
Key Takeaways
- ✓Page speed directly affects revenue, conversion rates, and search engine ranking.
- ✓Caching stores pre-built copies for faster delivery but requires cache invalidation when content changes.
- ✓CDNs serve content from geographically close servers, improving speed for distributed audiences.
- ✓A systematic launch checklist prevents the most common launch-day failures.