axomega.com · measured 23 October 2026
On a phone, a visitor waits 4.9 seconds before your site is readable.
I loaded axomega.com the way a customer does — a mid-range phone, an ordinary 4G connection — and timed it. The page is 709 KB. 581 KB of that is one logo file, shown at 180 pixels wide.
None of this needs a rebuild. It needs the fat trimmed, three scripts taken off the critical path, and the result measured again to prove it moved. That is what this page prices.
Two numbers decide whether someone stays
How long until the page is readable, and how many bytes it takes to get there. Both were measured on this site, not estimated from a template. The red bar is now; the green mark is where it should be.
At 1.6 Mbps the logo alone spends 2.9 seconds downloading. Re-exported at the size it is actually displayed, the same logo is 9.9 KB — I made that file and weighed it, it is not an estimate.
Already healthy — I am not going to charge you to "fix" these
- Server response
- 85 msTTFB — time to first byte
- Readable on desktop
- 1.6 sunder the 2.5 s good mark
- Layout jumping
- 0.0005CLS — things moving mid-load
Where the 709 KB actually goes
Every byte the home page pulls on a first visit, measured with compression switched on — the way a real browser receives it.
- Logo PNG 581 KB
- Web fonts 70.5 KB
- HTML 28.9 KB
- Stylesheets 20.5 KB
- JavaScript 6.9 KB
- Manifest + API 0.7 KB
I tested the fix before quoting for it
Four runs of the same page on the same emulated phone. In two of them I blocked a file at the network level and re-timed the load.
| What I removed | Readable | Fully loaded | Browser frozen |
|---|---|---|---|
| Nothing — as it is today | 4.9 s | 5.3 s | 7.4 s |
| The logo | 4.4 s | 3.5 s | 6.3 s |
| Four scripts | 4.1 s | 4.9 s | 0.0 s |
| Logo and scripts | 3.9 s | 3.2 s | 0.0 s |
Removing one image takes 1.8 seconds off the load. Removing four small scripts — 19 KB between them — takes all 7.4 seconds of freezing out of the page. Note that even with both removed it lands at 3.9 s, not under 2.5: the stylesheets and fonts are still on the critical path. I am not going to pretend otherwise.
What a second is worth — on your numbers
Four things I do not know about your business, so you type them. Everything below is arithmetic on those four numbers. It is not a promise, and I have no idea whether a faster page will lift your conversion by the figure you enter.
- Extra conversions per month
- 2.4
- Extra revenue per month
- $2,160
- Over a year
- $25,920
- Your current selection pays for itself in
- —
How this is calculated: visits × conversion% = current conversions. Conversions × the improvement you typed = extra conversions. Multiplied by your visitor value. Payback compares that monthly figure against the top of your selected range.
What I would actually do
Eight pieces of work, tick the ones you want. Hours are ranges because I have measured the outside of this site, not the code that builds it. $60/hour, excluding GST — every price below is hours × that rate, so you can check the arithmetic.
- Hours
- 8 – 14 h
- Price, excluding GST
- $480 – $840
- Working days at 6 h/day
- 2 – 3 days
Recommended bundle: 4 items, 8 to 14 hours, $480 to $840.
Your selection
How it runs
Three steps, two of which need your approval before anything changes on your live site.
Measure, then agree
I take a full copy of the site to a staging address and re-run the same harness that produced this page. You see the numbers before any work starts. If the staging copy already performs differently from what is on this page, I tell you and the quote changes.
Change one thing at a time
Logo first, because it is the biggest and the safest. Then scripts, then fonts and stylesheets. After each step I re-measure and send you the before and after. You approve each step — nothing goes live without you seeing it.
Test it like a customer, then sign off
Forms submitted and received, every navigation link clicked, and a real test order through checkout wherever checkout exists. Run on a real phone as well as the emulator. Then the final measurement, in writing, including any step that did not help.
The questions you are probably about to ask
Will the site look any different when you are done?
No. A re-exported logo, a subset font and deferred scripts are invisible — the layout, colours and copy stay exactly as they are. If any change would alter what a visitor sees, you get a screenshot of the before and after at phone and desktop width before it goes anywhere near your live site.
Could this break something?
The scripts are the only real risk, because they drive animation. That is why they are tested on staging with the effects switched back on, not just by checking that the page loads. Forms get submitted, links get clicked, checkout gets a real test order. And it is a staging copy — your live site keeps working throughout.
Do I need a new host, or a new site?
No. Your server answers in 85 milliseconds, which is genuinely good — there is nothing to fix on that side. This is all about the files the page asks the browser to download. No replatforming, no theme replacement, no new plugin stack.
How long will it take?
Whatever you tick, at about six focused hours a day: 2 – 3 days. Work is delivered in small batches with a measurement after each, so you are never waiting a fortnight to see anything.
How will I know it actually worked?
The same test that produced this page, run again on the same emulated phone and connection, with both sets of numbers side by side. You get the raw numbers, not a summary percentage. If the improvement is small, the report will say it is small.
What if it does not get faster?
Then I write that down and say so, and you do not pay for the measurement and reporting work. I would rather hand you a null result you can trust than a story you cannot check. What you are buying is the attempt, properly measured — not a guaranteed number.
What does it cost to keep it fast?
Nothing ongoing from me. This is one-off work — no retainer, no monthly fee, no subscription plugin. The guardrails item exists so the next oversized photo cannot quietly land six months from now. A re-check in a year is a one-hour job if you want it.
Will this affect my Google rankings?
Page speed is one of many signals Google uses, and the things listed here are the same things Google's own tooling flags. Nothing in this work changes your URLs, your content, or your site structure, so there is no SEO risk in the usual sense — and no ranking promise from me either.