01M2GK19WM34E7WFYH23B5BVRG
Overall score
The website is fundamentally solid. Targeted improvements can raise the score further. Loading speed in particular offers room for improvement.
Browser runtime measurement
These values come from the real page build in the browser and show the differences between desktop and mobile.
Act now
HTML and CSS together reference 31 distinct images.
Recommendation: Optimise images, use lazy loading and remove unnecessary media.
Real user data (CrUX)
Based on anonymous Chrome user data from the last 28 days · Chrome users only · No Firefox/Safari
Likely LCP background image candidate
The largest visible content appears to be shaped by a CSS background image.
The element probably uses a background image via CSS.
Main causes
Actually loaded in the browser.
Top hosts by data volume
Largest requests
Total: 2.808,5 KB
Total: 2.808,7 KB
Recommendations
31 images adding up to around 1.98 MB. Large images, missing modern formats and missing lazy loading are a good lever here.
The real page load triggers 100 individual requests. Reduce unnecessary lazy loads, third parties and extra front-end files first.
6 external hosts are loaded during the real page load. That increases dependencies and connection overhead and often slows the page down.
js.stripe.com causes around 252.71 KB across 3 requests.
Recommendation: Reduce, bundle or defer third-party load.
younes.svg weighs around 387.17 KB.
Recommendation: Resize hero and above-the-fold images and compress them with modern formats.
The browser main thread was blocked for around 298 ms during page load (Total Blocking Time).
Recommendation: Reduce JavaScript load, defer heavy scripts and break up long tasks.
https://js.stripe.com/v3/ – 252.56 KB
File: v3 · Host: js.stripe.com
https://js.stripe.com/v3/
younes.svg – 387.17 KB
File: younes.svg · Host: huggingface.co
https://huggingface.co/front/assets/homepage/younes.svg
js.stripe.com – 252.71 KB across 3 requests
Host: js.stripe.com
100 requests during page load
younes.svg – 387.17 KB
File: younes.svg · Host: huggingface.co
https://huggingface.co/front/assets/homepage/younes.svg
Explained simply
These short texts put the most important measurements into plain language.
The server responds quickly.
Why it matters: TTFB stands for “time to first byte” — the time until the server returns the first data.
Technical value: 28 ms
The page is served compressed, so less data has to be transferred.
Why it matters: Compression reduces the transfer size of HTML, CSS and JavaScript.
Technical value: Content-Encoding: gzip
The browser is allowed to cache files, which can make repeat visits faster.
Why it matters: Browser caching prevents unchanged files from being downloaded over and over again.
Technical value: CSS: 2/2, JS: 1/2, images: 15/15, fonts: 10/10 | page cache: yes, CDN: cloudfront, origin: unknown | HTML Cache-Control: empty (normal for dynamic pages)
31 images were detected. Of those, 0 use lazy loading and 13 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: 12, WEBP: 3 (15 of 31 measured), measured image weight: 1.98 MB
2 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.
Why it matters: Many or large JavaScript files can delay a page’s rendering and interactivity.
Technical value: 2 external files, 0 data URI scripts, 301.73 KB
109 font files were detected. In addition, 0 external font services (e.g. Google Fonts) are embedded.
Why it matters: Many or large web fonts increase loading time and can cause visible layout delays.
Technical value: 109 font files, 0 external font services, groups: 6bdfa088-5a16-4108-8482-7dd3e04339ad (1), eebe9730-6100-405f-a29c-5a42b00bd10a (1), 4456da5f-718b-4e7d-a2b0-367a0ae7cfa5 (1), measured font weight: 236.31 KB
2 direct CSS files and 2 additional CSS dependencies were detected.
Why it matters: Many stylesheets or imported CSS files increase the number of loaded resources.
Technical value: Direct CSS files: 2, additional dependencies: 2, estimated CSS weight: 911.51 KB
The page loads content from 4 external hosts.
Why it matters: Every additional external domain increases dependencies and can affect loading time.
Technical value: cdn: 1, other: 1 — cdnjs.cloudflare.com, de5282c3ca0c.edge.sdk.awswaf.com, cdn-avatars.huggingface.co, cdn-uploads.huggingface.co
The first visible content appears after around 468 ms, the most important visible content after around 468 ms. That is a good result.
Why it matters: These values describe when users actually see the first and the most important content.
Technical value: FCP: 468 ms, LCP: 468 ms
Layout stability is good. The measured CLS value is 0.
Why it matters: CLS describes whether content shifts visibly while loading.
Technical value: CLS: 0
The real page load issues relatively many requests: 100 requests with around 2.80 MB.
Why it matters: This value shows the actual runtime load in the browser, not just static HTML indicators.
Technical value: 100 requests, 2.80 MB
Score breakdown
Speed
Cache quality by asset type
Impact of third-party services
1 assets detected
cdnjs.cloudflare.com
Ein CDN kann sinnvoll sein, erhöht aber trotzdem die Zahl externer Hosts.
1 assets detected
de5282c3ca0c.edge.sdk.awswaf.com
Externe Dienste erhöhen generell Abhängigkeiten und zusätzliche Verbindungen.
Externally loaded services in the browser
These services were actually contacted during the real page build in the browser.
17 requests · 280,5 KB
cdn-avatars.huggingface.co, js.stripe.com, de5282c3ca0c.edge.sdk.awswaf.com, m.stripe.network, m.stripe.com
Statically detected external hosts
These hosts were detected directly in HTML or CSS. Not every one of them was necessarily loaded during the real page build.
Statically detected third-party services by category
This classification is based on statically detected asset hosts and complements the real browser runtime measurement.
1 assets detected
cdnjs.cloudflare.com
1 assets detected
de5282c3ca0c.edge.sdk.awswaf.com
Largest requests during the real page build
This list shows the largest requests from the real browser run and helps you spot notable files and hosts faster.
Technical metrics
Measurement conditions
Connection timing (TTFB: 28 ms)
Tasks that blocked the browser main thread.
Details on individual metrics
In-depth values for assets, images, fonts, CSS and JavaScript. The most important groups are grouped thematically below.
This list shows the largest measured files from the asset check.
These are image files that are not referenced directly in the HTML, but in CSS via url(...) references.
Sample: 15 of 31 images were loaded and measured. Size and count refer only to these images.
Detected font files: 109, External font services: 0. External font services are e.g. Google Fonts or Adobe Typekit, from which concrete font files are only loaded later.
Only the first 40 entries are shown.
WordPress detection
Optimisation potential
These points are not critical, but can improve the performance, stability or clarity of the page structure.
28 of 28 images have no explicit dimensions and can cause layout shifts (CLS).
Recommendation: Set width and height attributes on img tags.
The browser issued 100 requests.
Recommendation: Above all, reduce or bundle tracking, builder assets, fonts and additional external services.
The real page load contacted 6 external hosts.
Recommendation: Reduce or bundle external scripts and third-party connections.
The inspected images add up to around 1.98 MB.
Recommendation: Resize and compress images and use modern formats.
younes.svg weighs around 387.17 KB.
Recommendation: Resize and compress this image specifically and serve it in a more modern format.
Images were detected, but no loading="lazy" on any image element.
Recommendation: Enable lazy loading for images outside the viewport.
Detected 109 font files totalling around 236.31 KB.
Recommendation: Load fewer font weights and serve fonts as efficiently as possible.
69 @font-face rules without font-display detected. Without font-display, text can stay invisible while loading (FOIT).
Recommendation: Add font-display: swap or optional to the @font-face rules.
The page loads from 4 external hosts but uses neither preconnect nor dns-prefetch.
Recommendation: Add preconnect or dns-prefetch for the most important external hosts in the HTML head.
Already done well
These points already stood out positively in the current scan.
The server response takes around 28 ms.
Detected compression: gzip.
The website is reachable over HTTPS.
The website is served over HTTP/2.
The website advertises HTTP/3 via the Alt-Svc header.
The website is reachable over IPv6.
Additional hints
Supplementary hints from the scan that can be useful for classification and technical assessment.
CSS pulls in 2 further stylesheet dependencies.
CSS references 109 additional font files.
No clear WordPress indicators were found in the HTML or the asset paths.
Waterfall
Detailed request waterfall from the browser run.
Raw data
Complete scan data as a machine-readable JSON file or tabular export.