Speed Is a Revenue Line, Not a Tech Detail
Slow pages can frustrate visitors and affect business results. Google/SOASTA research published in March 2017 estimated a 32% relative increase in mobile bounce probability when page-load time rose from one to three seconds. That historical estimate is not a current universal benchmark or a measured result for your site; measure the impact on your own visitors and conversions.
Measure Before You Touch Anything
Run your key pages — homepage, top landing pages, checkout or contact — through PageSpeed Insights and record three numbers: Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (stability). Test mobile, not desktop; mobile is where your customers are and where the problems live. Note the specific opportunities the report lists — they are your work order, in priority order.
Images: The Biggest Win, Almost Always
Unoptimized images cause the majority of small-business speed problems. The fixes, in order of impact:
- Convert to modern formats — WebP or AVIF instead of PNG/JPEG, typically 30–70 percent smaller
- Resize to display dimensions — a 4000-pixel photo in a 600-pixel slot is pure waste
- Compress — tools like Squoosh or ShortPixel reach quality levels no visitor can distinguish
- Lazy-load below-the-fold images — browsers do this natively with one attribute
- Set explicit width and height — prevents layout shift as images load
Scripts, Fonts and the Quiet Killers
Third-party scripts accumulate like barnacles: chat widgets, analytics duplicates, social pixels, heatmap tools installed for a one-week test three years ago. Audit ruthlessly — every script must justify its cost in milliseconds or be removed. Limit font families and weights, self-host where possible, and use font-display: swap so text renders immediately. Each removed script is found speed at zero cost.
Open your browser’s network tab, reload your homepage, sort by size and by time. The offenders name themselves: usually a hero image and two forgotten scripts.
Hosting and Caching: The Foundation
No amount of front-end tuning rescues a slow server. A time-to-first-byte above 600 milliseconds is a reason to investigate, not proof that hosting is the cause. TTFB includes redirects, DNS and connection setup as well as response waiting time; Google’s web.dev guidance suggests 800 milliseconds or less as a rough target. Diagnose the contributing phases, backend work and cache behavior before choosing a fix. Enable server and browser caching, use a CDN so assets serve from locations near your visitors, and move off bargain shared hosting if the business depends on the site. These are fixed monthly costs that protect every visit, every day.
Keep It Fast: The Maintenance Habit
Speed degrades by accumulation — new images, new plugins, new scripts added without checking cost. Set a quarterly speed review: re-test key pages, compare against your recorded baseline, and fix regressions before they compound. Treat every new addition to the site as having a speed budget to justify.
Conclusion
Fast sites follow the same recipe: measure honestly, fix images first, evict unused scripts, and put the site on proper hosting with caching. The achievable improvement and timeline depend on the site’s baseline, bottlenecks and implementation; measure before and after each change. Nadouri Digital LLC audits and fixes site speed as part of our optimization services — copy and performance together, because neither works alone.