Web Development
Website Speed and Conversions: What We Fixed on Our Own Site After a PageSpeed Score of 49
Web DevelopmentWhy speed affects sales, not just rankings
People do not wait for slow pages, especially on a phone and a mobile network. A page that takes many seconds to become usable loses some visitors before they read a word, and Google uses page experience as one of many signals.
We tell clients this all the time, so when our own homepage scored 49 on mobile PageSpeed Insights, we treated it as a real problem and not an embarrassment to hide.
What the report said
The mobile report showed a total blocking time of about 25.9 seconds and a total page weight of roughly 58 MB. Total blocking time is how long the page is stuck and cannot respond to a tap. Nearly 26 seconds is far outside the range Google considers good.
The culprit was not clever code. It was media. Our homepage has autoplaying reels of client work, and on phones more than ten videos were downloading and decoding at the same moment, whether or not anyone had scrolled down to see them.
Fix 1: Only load what is on screen
We built a small component that holds back a video's file until it is close to the viewport. Nothing loads at first paint; each video starts loading when you scroll near it. On our page that alone removed most of the wasted downloading and the worst of the freezing.
Fix 2: Send smaller files
- Images: we converted work samples from JPG and PNG to WebP at the size they actually display. That took about 8.9 MB of images down to roughly 1 MB, with no visible loss of quality.
- Videos: we re-encoded every clip at a lower bitrate, scaled them to their display size, and removed audio from clips that always play muted. Our video weight dropped from about 73 MB to about 19 MB.
The whole assets folder went from 73 MB to 21 MB.
Fix 3: Keep the phone experience honest
We also lowered how hard our animated background works on phones and capped its pixel density, so the effect looks the same but does not drain the device. Fast animations matter too: we tightened our intro so the page is usable sooner.
A checklist you can use on your own site
- Run PageSpeed Insights on mobile, not desktop, and read the "opportunities" list.
- Check the total page weight. Anything over a few MB on a marketing page deserves questions.
- Lazy-load anything below the fold, especially video.
- Serve images in modern formats (WebP or AVIF) at the size they are shown.
- Compress video, and do not autoplay heavy clips on mobile.
- Re-test after each change so you know what actually helped.
If you want this done for your site, that is exactly what our website development team does.
Frequently asked questions
What is a good PageSpeed score?
Google treats 90 to 100 as good, 50 to 89 as needs improvement and below 50 as poor. Aim for green on mobile, where most of your visitors are.
What is total blocking time?
It measures how long the main thread of the browser is busy so that taps and scrolling feel stuck. Lower is better; a few hundred milliseconds or less is a healthy target.
Does page speed affect SEO?
Page experience is one of many ranking signals, and it also affects how many visitors stay long enough to convert, so it matters for both.
What usually slows websites down?
Large images and video, too many third-party scripts and heavy animation. Media is the most common culprit, as it was on our own site.