Website speed optimization for sites that lose visitors on mobile

• ·You pay for ads, emails or social posts, and most of the visits arrive on phones, often on mobile data.
• ·PageSpeed Insights shows your mobile score in orange or red, or Search Console says your pages fail Core Web Vitals.
• ·The site grew one app, plugin, pixel or chat widget at a time, and nobody measured what each one costs.
• ·It runs on Shopify, WordPress, Wix, Webflow, a React or Next.js app, or something built in-house.

A slow site rarely has one cause. It’s usually a pile of small decisions: a huge image at the top, a font that holds back the text, three tracking scripts that load before the page, an intro animation that hides the content, a theme that ships code for features you don’t use.

A speed score tells you something is wrong and stops there. It doesn’t say what to fix first, and some fixes help one number while hurting another, so each change has to be measured on its own.

Every second a visitor stares at a blank or half-drawn screen is a chance to hit back. On paid traffic, you pay for that click either way.

Google counts Core Web Vitals, measured on real Chrome visitors, among its ranking signals. It’s one signal among many, and a failing page hands an edge to a competitor with similar content.

Slowness piles up. Each new app or script adds a little, so a site that is slow today gets slower unless someone keeps an eye on it.

• ·Visitors see your headline, product and price sooner, on the phones they use.
• ·You know what each script and app costs in load time, and you decide which ones earn their place.
• ·You get the measurements before and after, plus a short set of rules that keep the site fast when the next plugin or campaign arrives.

1. 01A written diagnosis in plain language: what slows down each key page, and the fix for each cause, ordered by impact and effort.
2. 02Measurements before and after: several test runs on mobile and desktop per key page, plus real-visitor data from Google when your site has enough traffic.
3. 03The fixes, done by me: in your theme, plugins, app settings or code, depending on the platform.
4. 04A list of what was removed, replaced or delayed, and why.
5. 05Rules for your team or agency, so the next plugin or campaign doesn’t undo the work.

1. Step 1: 01

   Short

   Pick the pages

   You name the pages that make you money, usually the home page, a landing or product page and the checkout or contact page, and give me access to the site and, if you have them, Search Console and analytics.

2. Step 2: 02

   Early

   Measure

   Repeated tests on each page, a look at everything each page loads, and real-visitor data from Google where it exists.

3. Step 3: 03

   Short

   Diagnosis

   You get the findings ordered by impact and effort. We agree on what I fix and what stays, such as a script your marketing depends on.

4. Step 4: 04

   Most of the work

   Fix

   One change at a time, each measured on a copy or preview of the site before it goes live.

5. Step 5: 05

   Short

   Check and hand over

   Final measurements on the live site, the rules document and a walkthrough with you or your team.

• ·Access to the site: admin on Shopify, WordPress, Wix or Webflow, or the code repository for a custom site.
• ·A way to try changes before they go live: a theme copy, a staging site or preview deployments.
• ·Search Console access, if you want real-visitor data in the report.
• ·The pages that matter and the things that must stay: tracking your marketing needs, animations your brand keeps.

My homepage scored 55 for mobile performance on Lighthouse, Google’s speed test. It has an animated intro, two languages and more than 300 tools behind it. After two rounds of work it scores between 96 and 100 on mobile, with a median of about 98, and 98 to 100 on desktop. I kept the animations and the design. Here is what changed, in plain words, roughly in order of impact.

I measured each change on a preview copy before it went live, kept what moved the numbers, dropped what didn’t and wrote down why, so the score doesn’t slide back with the next feature.

Test the homepage on PageSpeed Insights

The proof is the site you’re on. It’s public, so you can test it yourself instead of trusting a screenshot.

• arielton.com homepageOn this site

  The page from the case study above: animated, in two languages, with its intro kept.

• PageSpeed Insights for arielton.comExternal site

  Runs Google’s speed test on the live homepage. Scores move a few points between runs, which is why I report ranges.

How much does speed optimization cost?

It depends on the platform, how many pages matter and how much is slowing them down. Send me your site’s address and the pages that bring in money, and I reply with a written proposal and a price for that scope before any work starts.

How long does it take?

You see the diagnosis early, before most of the fixing starts. How long the fixes take depends on how many causes there are and how quickly changes can go live on your platform. The proposal gives dates for your scope.

My site runs on Shopify, WordPress or Wix. Can you still help?

Yes. On Shopify and WordPress I work on the theme, apps, plugins, images and scripts. On closed builders such as Wix, part of the weight belongs to the platform and nobody outside it can change that, so the diagnosis separates what you can fix from what you can’t.

I already have a developer or an agency. Why bring you in?

Speed work tends to lose to the next feature or campaign. I can make the fixes myself, or hand your developer the diagnosis and review their changes. Your developer or agency keeps ownership of the site in both cases.

What if the score doesn’t improve?

I measure before touching anything and after every change, and I undo changes that don’t help. I won’t promise a score of 100: lab scores vary between runs, and some costs, like a chat widget or a cookie banner, are business choices. You get the measured before and after in writing.