94/100
ExcellentRated higher than 95% of all scanned websites
The website is in very good shape. Minor optimisations are still possible. 6 points short of 100, most of them in Speed (3) and Caching (2).
Measured in the browser
- Main content visible
- 272 ms
- Good
- LCP
- Server response
- 589 ms
- Needs improvement
- TTFB
- Layout stable
- 0
- Good
- CLS
- Page weight
- 47 KB
- Good
- Main content visible
- 356 ms
- Good
- LCP
- Server response
- 589 ms
- Needs improvement
- TTFB
- Layout stable
- 0
- Good
- CLS
- Page weight
- 47 KB
- Good
How the page loads
Frames at original size Frames at original size
The times under the images are the moments the individual frames were captured. They are close to, but not exactly, the measured FCP and LCP values (Metrics tab), because frames are only taken at intervals.
Urgent issues
3 of 6
-
Server response can be improved
The server response takes around 589 ms. · Fix: Check caching and backend performance.
Show details
- Speed up the server response The server response takes around 589 ms. A full page cache, a faster backend and less server-side work will likely have the biggest effect.
- Slightly elevated TTFB Server response approx. 589 ms
Server response (TTFB): The server response has room for improvement and already delays page rendering noticeably.
Why it matters: TTFB stands for “time to first byte” — the time until the server returns the first data.
Technical value: 589 ms
≈ −3 points Needs improvement
-
Caching partly disabled
no-cache, private
Show details
- No clear page cache indicator No HIT/Age indicators detected
≈ −2 points Needs improvement
-
Optimise images
Lazy loading is not clearly detectable · 3 more findings · Fix: Enable lazy loading for images outside the viewport.
Show details
- Lazy loading is not clearly detectable Images were detected, but no loading="lazy" on any image element.
- No modern image formats detected No WebP or AVIF image files were detected in the HTML image sources. Recommendation: Use WebP or AVIF for images where possible.
- No modern image formats No WebP/AVIF detected
- No clear lazy loading No lazy loading indicators found
Images: 3 images were detected. Of those, 0 use lazy loading and 0 use modern formats such as WebP or AVIF.
Why it matters: Images are often the biggest performance factor. Lazy loading and modern formats help the most.
Technical value: SVG: 2 (2 of 3 measured), measured image weight: 7.44 KB
≈ −1 point Needs improvement
-
Streamline CSS and fonts
Additional CSS dependencies (1) and many web fonts (0) should be combined or reduced.
Show details
no score deduction Needs improvement
More notes2
-
Additional CSS dependencies detected
CSS pulls in 1 further stylesheet dependency.
Show details
Optional
-
WordPress not clearly detected
No clear WordPress indicators were found in the HTML or the asset paths.
Show details
Optional
-
The main thread runs smoothly
The Total Blocking Time is around 0 ms.
Good
-
Compression is active
Detected compression: Brotli.
Good
-
No Google Fonts from Google servers
No fonts were requested from Google servers while loading the page.
Good
-
HTTPS is active
The website is reachable over HTTPS.
Good
-
HTTP/2 is active
The website is served over HTTP/2.
Good
-
HTTP/3 is supported
The website advertises HTTP/3 via the Alt-Svc header.
Good
-
IPv6 is supported
The website is reachable over IPv6.
Good
-
Browser caching
The browser is allowed to cache files, which can make repeat visits faster.
Show details
Why it matters: Browser caching prevents unchanged files from being downloaded over and over again.
Technical value: CSS: 1/1, JS: 0/1, images: 2/2, fonts: unknown | page cache: no, CDN: cloudflare, origin: unknown | HTML Cache-Control: no-cache, private
Good
-
JavaScript
1 external JavaScript files were detected in the delivered HTML. Further scripts may only be loaded during the real page load through optimisation or lazy-load mechanisms.
Show details
Why it matters: Many or large JavaScript files can delay a page’s rendering and interactivity.
Technical value: 1 external files, 0 data URI scripts, 4.88 KB
Good
-
External services
No external services were detected – good for loading time and privacy.
Show details
Why it matters: Every additional external domain increases dependencies and can affect loading time.
Technical value: 0 external hosts
Good
-
Visible page rendering
The first visible content appears after around 272 ms, the most important visible content after around 272 ms. That is a good result.
Show details
Why it matters: These values describe when users actually see the first and the most important content.
Technical value: FCP: 272 ms, LCP: 272 ms
Good
-
Layout stability
Layout stability is good. The measured CLS value is 0.
Show details
Why it matters: CLS describes whether content shifts visibly while loading.
Technical value: CLS: 0
Good
-
Real browser requests
The number of real browser requests is manageable: 6 requests adding up to around 47.38 KB.
Show details
Why it matters: This value shows the actual runtime load in the browser, not just static HTML indicators.
Technical value: 6 requests, 47.38 KB
Good
Get notified when this page gets slower
Register for free – monitoring, alerts and more.
Scan history
686 public scans of this page
- Score delta
- ±0 Unchanged
- Compared with
- 8 Oct 2026 6:00 AM · Score: 94
-
94
8 Oct 2026 9:00 AMCurrently open
- 94
- 94
- 97
- 90
How fast is the page?
Lab = our browser run (Mobile, 390 px) · No real-visitor data available
Lab = our browser run (Desktop, 1440 px) · No real-visitor data available
| Metric | Lab | Rating |
|---|---|---|
| Main content visible LCPi | 272 ms | Good |
| First content FCPi | 272 ms | Good |
| Server response TTFBi | 589 ms | Needs improvement |
| Response to clicks | 0 ms TBTi | Good |
| Layout stable CLSi | 0 | Good |
| Requests | 6 | Good |
| Metric | Lab | Rating |
|---|---|---|
| Main content visible LCPi | 356 ms | Good |
| First content FCPi | 356 ms | Good |
| Server response TTFBi | 589 ms | Needs improvement |
| Response to clicks | 16 ms TBTi 1 long tasks | Good |
| Layout stable CLSi | 0 | Good |
| Requests | 6 | Good |
Main content is a block of text (<h1>, 310 × 73 px), not an image – it depends on server response, CSS and fonts.
Google PageSpeed score
Synthetic measurement from Google Lighthouse — measured independently of the turbometrics score.
Google rates this page as very fast. · Fetched on 7 Oct 2026 6:00 PM
Where does the page lose points?
Each category has up to 100 points and counts towards the overall score by weight (Speed 40%, Images 20%, Caching 18%, Technical 12%, WordPress 10%). Deductions in the list count within their category.
-
Speed
−8 ≈ −3 in the overall scoreServer response can be improvedServer response approx. 589 ms
-
Caching
−5 < 1 point in the overall scoreCaching partly disabledno-cache, private
-
Images
−4 < 1 point in the overall scoreNo modern image formatsNo WebP/AVIF detected
-
Caching
−4 < 1 point in the overall scoreNo clear page cache indicatorNo HIT/Age indicators detected
-
Images
−3 < 1 point in the overall scoreNo clear lazy loadingNo lazy loading indicators found
No deductions — all good.
What loads the most?
Mobile · 6 requests · 47 KB, of which 47 KB from turbometrics.io
Desktop · 6 requests · 47 KB, of which 47 KB from turbometrics.io
Server & connection
Connection timing (TTFB: 589 ms)
In detail
Response & caching – Needs improvement Browser caching on · Brotli
Cache quality by asset type
Images – Needs improvement 3 images, 7 KB
Largest images
Image types
Sample: 2 of 3 images were loaded and measured. Size and count refer only to these images.
- SVG 2 files 6.1 KB
Fonts – Needs improvement 0 files
CSS – Needs improvement 1 file · 1 via @import
Additional CSS dependencies
These are stylesheets referenced within other CSS files via @import references.
- CSS app-C_KP1Fga.css turbometrics.io ↗
JavaScript – Good 1 file
Detected JavaScript files
These are the external script sources detected in the directly delivered HTML. Dynamically loaded scripts are not fully included.
- JS tm.min.js turbometrics.io ↗
Loading sequence – Good 6 requests · 36 KB
Weight by type
Page build timing
Measured in the browser run: the times start with the request to the server. The TTFB here is therefore shorter than the check-server value above, which includes DNS, connection and TLS.
HTML & structure – Not rated 385 DOM elements · 57 KB of HTML
Waterfall
AI-generated recommendations AI
Written by an AI from the measurements of this scan. Check every suggestion before you apply it. The prioritised list with evidence is on the Overview tab. Here you get implementation steps to tick off.
Personalised AI recommendations
Scan your website and get an AI analysis with concrete measures – free with an account.
Register for free →- Unlimited analyses · Every scan, any time
- Prioritised findings · What really matters
- AI analysis · individual & automatic