Your Site Is a Fossil. Google Moved On.

Bob called me on a Tuesday. His remodeling site had not booked him a job in months, and he could not figure out why. It looked fine to him. He built it back in 2015, paid good money for it then, and never touched it again. Why would he? It still looked fine.

So we pulled it up on his phone and just watched it load. One second. Three. Six. Nine. Nine seconds before the page was usable. By second three, most buyers are already gone. Bob did not have a design problem. He had a speed problem he could not see, and Google could see it just fine. His site was not broken. It just stopped keeping up.

Old. Slow. Skipped. Left behind.

Here is the part that stings. It is not Bob's fault. He built a site for the web the way it was in 2015, and the web sped up without him. I have built more than ten thousand sites, and I watch this happen every week. So let me put the old machine on the table and show you exactly what is quietly costing you jobs.

TL;DR (the short answer)

A site built in 2015 was built for a slower web. Google has since made speed and stability a ranking signal through Core Web Vitals, and buyers on phones leave fast when a page drags or jumps. Your old site fails that test quietly, so it ranks lower and loses jobs while it still looks fine to you. A light, static rebuild loads in under a second and passes the test clean.

3 Things to Remember

The Web Sped Up. Your Site Didn't.

In 2015 a four-second load was normal. Nobody blinked. Then phones took over, buyers got impatient, and Google started rewarding the sites that showed up fast. The bar for what counts as fast has moved almost every year since. Your site did not get slower on its own. The standard moved, and your site stayed put.

That is the trap with an old build. It feels frozen in time, but the grade against it keeps getting harder. The old theme, the stacked plugins, the big unoptimized images that were fine in 2015 are all still there, loading all at once, on a phone, for a buyer who counts the seconds. Nothing on your site changed. Everything around it did.

The mistake: Leaving the old theme, stacked plugins, and heavy images in place because the site still "works." Working and winning are not the same thing.

The fix: Rebuild light and static, so the page ships finished on the first byte and loads the heavy stuff only as the buyer scrolls to it.

The payoff: The page shows up before the buyer loses patience, so more of them stay long enough to call.

Not sure what an old build is doing to your speed? Have the AI pin down exactly what is dragging it down, in order, using only free tools.

Act as a website performance engineer. My site was built years ago on [WordPress / Wix / an old custom theme] and it feels dated and slow. In plain English for a non-technical owner:
1. The parts of an older build most likely dragging my speed down today (old theme, stacked plugins, unoptimized images, heavy scripts)
2. How to tell which one is hurting me most, using only free tools
3. Why standards like Core Web Vitals make an old site score worse every year, even when I change nothing
4. The three changes that would speed it up the fastest, in order
Keep it specific and skip the jargon.

Google Grades a Test You Can't See.

Google measures three things on every page, and it does it whether you asked or not. How fast the page paints. How fast it responds when you tap. How much it jumps around while it loads. It calls them Core Web Vitals, and they have been a ranking signal since 2021.

Here is the cruel part. You never see the score. There is no red envelope in the mail, no call from Google telling you that you failed. You just see the phone ring a little less each month and you blame the market. Meanwhile your buyer is grading the exact same three things without knowing the name for any of them. A slow, jumpy page loses the ranking and the buyer at the same time, and you never see the report card.

You do not have to take my word for the score. Here is what those three grades feel like to a buyer, and what each one costs you. Nudge each slider and watch it turn into jobs.

A Slow Score Is Lost Jobs, Not a Tech Problem.

A developer will show you a page speed number and a wall of jargon: largest contentful paint, cumulative layout shift, time to first byte. Ignore all of it. None of those words book work. The only number that matters is the buyer who left before your page loaded, and the job that went to whoever loaded faster. Speed is not a report card. It is revenue.

Run the math on your own shop. If you would book two hundred jobs a year at full speed and a slow, jumpy page quietly loses a quarter of them, that is fifty jobs gone. Not to a better pitch. Not to a lower price. Gone before your page even finished loading. That is the most expensive thing on your whole site, and it does not show up on a single invoice.

Want your own grade in dollars instead of tech scores? Paste your homepage into this and let the model translate the whole thing into jobs.

Act like a Google Core Web Vitals grader, but translate everything into money, not tech scores. My site is [PASTE YOUR HOMEPAGE URL]. Tell me in plain English: 1) how my page likely scores on loading, responsiveness, and layout stability, 2) what each of those actually means for a buyer trying to use my site, 3) roughly how many jobs a slow, shifting, laggy page like this loses in a year, 4) the 3 fixes that would matter most. No developer jargon, talk to me like a business owner.

I Didn't Wait for Google to Tell Me.

When an Old Site Is Actually Fine.

I rip on old sites for a living, and I will still give it to you straight. An aging site is not always the wrong call.

If it is a brand new venture or a hobby, nobody is buying yet, and no jobs are on the line, a slow load does not cost you much. If you are a writer who needs one clean page of text, you do not need speed engineering. And plenty of internal tools run slow behind a login where no buyer ever sees them, and that is fine.

Now be honest about your situation. If you run a business and you want it to grow, none of that is you. You have buyers on phones deciding in three seconds, and a site built for 2015 that keeps sliding down the results. The fix is the same one that worked for Bob: build light and static. It is also why a heavy WordPress site and a page that loads too slow both leave money on the table.

Pass the Test You're Already Taking.

You do not need to learn what Core Web Vitals means. You need a site that passes them clean, loads in under a second, and holds still while it loads. That is the whole job. Buy it once, or lease it and we manage everything for you. Easy.

Bob's new site loads in under a second now. The phone started ringing again inside a month, and he never had to understand a single line of what changed. He just stopped failing a test he could not see. Not sure whether to patch your old site or start fresh? Ask first.

Act as a straight-talking web strategist. My current site is [your URL], built around [year] on [platform], and it is slow. Help me decide honestly:
1. Whether a site this old is worth patching, or better rebuilt from scratch
2. What a clean, static rebuild would fix that patching an old build never will
3. What I would gain in speed, rankings, and booked jobs from a site that loads in under a second
4. The questions to ask any developer before I pay them a dime
Talk to me like a business owner, not an engineer.

Take a Test Drive →

FAQ