What we offer

NEW CASE
Antana

We create digital solutions that work for businesses

Become a clientBecome a client
Give us a call +38 (066) 35-14-529

Let's take the first step towards your website — write to us

Close
Tools

Website Speed Audit

SEO and marketing

You may also like

Site speed: TTFB, weight, caching and a 0–100 score.

We measure your server’s real response: DNS, connection, TLS, TTFB, page weight, compression and caching. No third-party APIs.

Free audit

Is your site slow? We’ll show what exactly slows it down

A tool checks one thing. We’ll go through your whole site for free and send a report: what’s holding you back in Google and what to fix first.

  • Indexing and technical errors
  • Speed and Core Web Vitals
  • Meta tags, structured data, duplicates
  • A fix plan, by priority
Learn more: Website speed optimisation

Report in 1–2 business days. No strings attached — if everything’s fine, we’ll say so.

By clicking the button you agree to the privacy policy

The metrics that define speed

Google does not look at total load time but at three specific measurements.

LCP When the largest element appears, usually the hero image. Under 2.5 seconds is good.
INP How quickly the page responds to a tap. It replaced the old FID metric in 2024.
CLS How much the layout jumps while loading. That button escaping from under your finger is this metric.
TTFB Time to the first byte from the server. It shows whether the problem is hosting or your own code.

What slows a site down most

In practice the first two items deliver more improvement than everything else combined.

Uncompressed images A four-megabyte camera photo in the header. The same shot in webp weighs ten times less with no visible loss.
Too many third-party scripts Analytics, chat, pixel, review widget. Each pulls its own code and half of them block rendering.
Slow hosting With a TTFB above one second, optimising images changes nothing. The problem starts before loading does.
No caching On every visit the server rebuilds the page. Caching turns that work into serving a ready file.
Fonts without a strategy Text stays invisible while the font loads. One CSS property makes it appear immediately.

Why the score jumps between runs

The test is synthetic The tool simulates a slow phone and network. Real visitors see different numbers, often better ones.
First-visit cache The first run after a change is always worse because nothing is cached yet. Compare the second and third.
Third parties lag If a chat or pixel is slow at that moment, the score drops although your site did not change.
Look at field data Search Console has a Core Web Vitals section with figures from real visitors. It beats any one-off test.

Read more on the blog

How to Test Website Speed: TTFB, Core Web Vitals, and Practical Fixes A practical speed-testing guide covering TTFB, LCP, INP, CLS, lab versus field data, common bottlenecks and a prioritised optimisation plan. How to Speed Up a Website: 12 Ways to Improve Loading Performance PageSpeed is red and the mobile site feels slow? Learn how to find the real bottleneck and prioritise the fixes that matter.
Rate this tool
It tells us what to improve first
Be the first to rate 5.0 of 5 0 votes

FAQ

What is TTFB and what value is good?
TTFB is time to first byte — how long the server thought before it started sending the page. Under 200 ms is excellent, under 400 ms is fine, over 800 ms means something needs fixing: weak hosting, heavy database queries or missing caching. TTFB has nothing to do with design — it is purely a server matter.
How is this different from PageSpeed Insights?
PageSpeed renders the page in a browser and measures Core Web Vitals — deeper, but slower and dependent on a third-party service. Our audit measures what is visible from the server side: network phases, code weight, compression, caching and resource composition. It is a fast technical check that immediately reveals blunt mistakes such as disabled gzip.
What gives the biggest speed gain?
In our experience the order is: enable gzip or brotli compression, convert images to webp and add lazy loading, cache static files for a month or more, move to HTTP/2 or HTTP/3, and take blocking scripts out of the head with defer. These steps cost a few hours of work and deliver more than any cosmetic tweak.
Telegram Viber Call us