⚡ 90+ PageSpeed target
Slow pages lose rankings, ad spend and customers — often before the design is even seen. The Dotted Tech engineers measurable speed: mobile PageSpeed scores of 90+, LCP under 1.5 seconds and Core Web Vitals that hold up in field data, not just in a lab test.
Avg. Score After
34→98
LCP Reduction
-82%
Conversion Lift
+31%
One URL, one email. We run the free test, hand over the 25-point audit and tell you honestly whether speed work is worth doing on your site right now.
A performance engineer at The Dotted Tech has your URL and is running the free speed test now. You will receive the 25-point audit, your current Core Web Vitals and a fixed-price plan within 24 hours.
Speed optimization for every stack we build and inherit
These are mobile scores measured in PageSpeed Insights before work started and after deployment, with the Core Web Vitals that moved fastest. Switch between the two states to see the difference.
Numbers animate — toggle both states to compare.
4,200 products · heavy app stack · 71% mobile traffic
LCP
6.8s
CLS
0.34
Page Weight
4.8MB
1,100 SKUs · subscription checkout · paid social traffic
LCP
5.1s
INP
480ms
Requests
138
340 pages · 9,000 organic sessions/month · heavy lead forms
LCP
7.4s
CLS
0.41
Page Weight
6.1MB
Authenticated dashboards · 3 regions · enterprise SSO
LCP
4.4s
INP
390ms
Requests
97
34 → 98
Average mobile score
-82%
Average LCP time
-87%
Page weight
+31%
Checkout conversions
Real PageSpeed test · Fixed price · 24h audit
Speed is not a vanity metric. It shapes how Google crawls your site, how long visitors stay, and how many of them finish a purchase or request a quote — which is why Core Web Vitals optimization sits alongside SEO and conversion work, not behind it.
Core Web Vitals have been part of Google's page experience signals since 2021. They act as a tie-breaker when two pages answer the same query equally well — and the page that loads in 1.2s usually wins the click regardless.
Slow, resource-heavy pages consume more of your crawl budget. Cleaning up render-blocking assets helps Google reach and index more of your commercial pages in the same crawl window.
Google indexes the mobile version of your site first. A desktop score of 92 with a mobile score of 34 means the version Google evaluates is the slow one.
Faster pages produce lower bounce and longer dwell time — behavioural signals that support rankings over months, not overnight.
WORKED EXAMPLE · CRESTLINE LEGAL
Mobile score 27 → 99, LCP 7.4s → 0.9s. Organic sessions grew +44% in 90 days on unchanged content, and form submissions rose +27%.
| Load Time | Mobile Bounce | Conversion Impact |
|---|---|---|
| 1s | ~9% | Baseline |
| 2s | ~24% | -7% vs baseline |
| 3s | ~38% | -14% vs baseline |
| 5s | ~53% | -25% vs baseline |
Directional benchmarks drawn from widely cited industry research (Google mobile abandonment data on 1–5s loads; the 100ms-and-conversions studies from retail and travel). Your own numbers come from your analytics.
Move the sliders to match your site. The estimate applies the widely cited rule that each additional second of load time reduces conversions by roughly 7%, starting from a 1.5s baseline.
EST. MONTHLY REVENUE LOST
$0
RECOVERABLE ANNUALLY
$0
Based on 120,000 visits, $85 average value and 3.5s load time (≈13% conversion loss vs a 1.5s baseline).
Real speed work happens at eight layers. Installing a caching plugin fixes one or two of them — which is why most sites plateau in the sixties and never reach the 90+ range Google calls good.
AVIF and WebP delivery, responsive srcsets, correct dimensions, lazy loading below the fold and eager loading for the LCP element.
Bundle splitting, tree shaking, deferring third-party tags and removing abandoned app scripts that block the main thread.
Inlining above-the-fold critical CSS, deferring the rest and eliminating unused rules so first paint happens instantly.
Self-hosted fonts, preload with font-display: swap and size-adjust fallback metrics to keep CLS at zero.
Full-page caching at the edge with correct bypass rules for carts, sessions and logged-in users, so the origin is barely touched.
Query tuning, indexing, object caching, PHP and runtime upgrades, plus compression and modern protocol configuration.
Targeted fixes for LCP, INP and CLS using real field data from CrUX rather than a single lab run on a fast connection.
Synthetic and real-user monitoring with alerts, so the next theme update or new app does not undo the gains.
Not sure which layer is holding your score down?
Short, measurable and staged. You see the audit within 24 hours, the first fixes within 48, and verification against real users over the following 28 days.
We measure your mobile and desktop scores, LCP element, TTFB, page weight and every blocking third-party script, then rank the fixes by impact versus effort.
Quick wins ship within 48 hours: images, fonts, caching and script deferral. Deeper work follows on a staging clone — CSS restructure, bundle splitting, query and server tuning.
We deploy with tracking and consent scripts verified, then re-measure PageSpeed Insights and Core Web Vitals field data, with 28 days of monitoring and rollback available throughout.
We agree the score and Core Web Vitals targets in writing before work starts. If we cannot reach them on the templates we quoted, we continue without additional fees. If a later theme update or new app regresses performance, the first 30 days of regression fixes are on us.
Real PageSpeed test · Fixed price · No design changes
No simulated numbers. This tool calls Google's PageSpeed Insights API and reports the same Lighthouse measurements Google itself uses — your performance score, Core Web Vitals and the largest opportunities, taken from a real page load.
Measured, not estimated
Google loads your page in a real Chrome instance and returns Lighthouse scores with a timestamp and version.
Mobile or desktop
Mobile is what Google indexes first, so start there.
Field data when it exists
If Google has enough real-user traffic for your URL, the Chrome UX Report metrics are shown alongside the lab run.
Privacy
The URL is sent to Google's public API from your browser. We do not store it here — only the audit form does that.
HOW THIS WORKS
The test needs the page to be publicly reachable — no logins, staging locks or local URLs. A full run usually takes 20–40 seconds, because Google is actually loading your site.
What you will get back:
Results come straight from Google's API and are never generated locally. If the API cannot be reached, you will see that — not an invented score.
● Google is loading your page in a real Chrome instance and measuring it. This normally takes 20–40 seconds.
Keep this tab open — the request is running from your browser directly to Google.
We would rather show you this message than an invented score.
Measuring
—
Lighthouse lab measurement. Field data below is what real visitors experienced.
Google returned the diagnostics for this URL but no performance score, which usually means the run was interrupted on their side. The measurements below are still real.
"Our product pages went from 6.8s to 1.2s on mobile and checkout conversions rose 31% in the first month. The score was the scoreboard — the revenue was the point."
Danika Kerr
Head of Ecommerce, Denby & Co.
"Nothing about the design changed, but organic sessions grew 44% in three months on the same content. We had been blaming our rankings on keyword strategy for a year."
Liam Prescott
Marketing Director, Crestline Legal
"They staged everything and proved it before touching production. Paid social costs per purchase dropped noticeably within two weeks — the same budget simply converted better."
Marta Whelan
Founder, Harvest Kitchen
The questions we get asked on almost every free speed test call.
Want to see your own numbers first?
Run the real PageSpeed test, see your before-and-after potential, then let The Dotted Tech do the engineering. 90+ mobile target, fixed price, no design regressions.
No obligation · NDA on request · 24-hour audit
The Dotted Tech
PageSpeed · Core Web Vitals