Your Website Score is

Similar Ranking

18
STARTSEITE | ONMYLIST.DE
onmylist.de
18
STARTSEITE - PORTNER KUNSTSTOFFVERARBEITUNGS GMBH
portner.de
18
18
KAFFEEVOLLAUTOMATEN MIETEN, LEASEN ODER KAUFEN | CAFFIA LEIPZIG
caffia.de
18
KUNSTNET - KUNST-ONLINE GALERIE
kunstnet.de
18
AUTOUNFALL.INFO
autounfall.info
18
WEIHNACHTSDEKOBASTELN
weihnachtsdekobasteln.de

Latest Sites

50
ALITTLEDELIGHTFUL - BRINGING JOY TO SPACES
alittledelightful.com
48
21ST - BUSINESS NEWS
21stcenturyabe.org
48
TI - TRAVEL INFORMATION
travellinginfo.my.id
43
MÄNNERMAGAZIN ONLINE LIFESTYLE-MÄNNERMAGAZIN TAMBURELLO
tamburello-magazin.de
52
MIUI - INFORMATION ABOUT TECHNOLOGY NEWS
miuimyanmar.net
49
ILLUSTRATED TEA CUP - HEALTH, PARENTING, AND BEYOND
illustratedteacup.com

Top Technologies

Apache
Web Servers
WordPress
CMS
Google Font API
Font Scripts
Nginx
Web Servers
Font Awesome
Font Scripts
Yoast SEO
SEO
Google AdSense
Advertising Networks
Twitter Bootstrap
Web Frameworks

18 caffia.de Last Updated: 3 weeks

Success 39% of passed verification steps
Warning 23% of total warning
Errors 38% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 74%
Best Practices Desktop Score 75%
SEO Desktop Score 85%
Performance Mobile Score 75%
Best Practices Mobile Score 76%
SEO Mobile Score 85%
Page Authority Authority 29%
Domain Authority Domain Authority 15%
Moz Rank 2.9/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 63 Characters
KAFFEEVOLLAUTOMATEN MIETEN, LEASEN ODER KAUFEN | CAFFIA LEIPZIG
Meta Description 0 Characters
NO DATA
Effective URL 16 Characters
http://caffia.de
Excerpt Page content
Kaffeevollautomaten mieten, leasen oder kaufen | Caffia Leipzig Direkt zum Inhalt Schließen Notdienst Sollten unerwart...
Keywords Cloud Density
kaffee19 automaten10 ihre9 shopbereich7 image7 cappuccino7 mail6 captcha6 zeichen6 bild6
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
kaffee 19
automaten 10
ihre 9
shopbereich 7
image 7
cappuccino 7
mail 6
captcha 6
zeichen 6
bild 6
Google Preview Your look like this in google search result
KAFFEEVOLLAUTOMATEN MIETEN, LEASEN ODER KAUFEN | CAFFIA LEIP
http://caffia.de
Kaffeevollautomaten mieten, leasen oder kaufen | Caffia Leipzig Direkt zum Inhalt Schließen Notdienst Sollten unerwart...
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~107.22 KB
Code Size: ~79.04 KB
Text Size: ~28.18 KB Ratio: 26.28%

Estimation Traffic and Earnings

0
Unique Visits
Daily
0
Pages Views
Daily
$0
Income
Daily
0
Unique Visits
Monthly
0
Pages Views
Monthly
$0
Income
Monthly
0
Unique Visits
Yearly
0
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Avoid enormous network payloads Total size was 17,230 KiB
Large network payloads cost users real money and are highly correlated with long load times
First Contentful Paint 0.4 s
First Contentful Paint marks the time at which the first text or image is painted
Improve image delivery Est savings of 8,902 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Serve images in next-gen formats Est savings of 5,176 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Minimizes main-thread work 0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid an excessive DOM size 1,259 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Server Backend Latencies 10 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid serving legacy JavaScript to modern browsers Est savings of 11 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Largest Contentful Paint element 6,500 ms
This is the largest contentful element painted within the viewport
Max Potential First Input Delay 150 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Does not use HTTPS 66 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Avoid large layout shifts 2 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Avoid long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Total Blocking Time 100 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Initial server response time was short Root document took 450 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint 6.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Defer offscreen images Est savings of 34 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Reduce unused JavaScript Est savings of 116 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Render blocking requests Est savings of 190 ms
Requests are blocking the page's initial render, which may delay LCP
Time to Interactive 6.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Font display Est savings of 20 ms
Consider setting [font-display](https://developer.chrome.com/blog/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Eliminate render-blocking resources Est savings of 130 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid chaining critical requests 6 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Properly size images Est savings of 1,091 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
JavaScript execution time 0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Cumulative Layout Shift 0.039
Cumulative Layout Shift measures the movement of visible elements within the viewport
Legacy JavaScript Est savings of 11 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers
Efficiently encode images Est savings of 154 KiB
Optimized images load faster and consume less cellular data
Use video formats for animated content Est savings of 3,731 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes

Mobile

Mobile Screenshot
JavaScript execution time 0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Reduce unused JavaScript Est savings of 117 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Network Round Trip Times 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Largest Contentful Paint element 8,780 ms
This is the largest contentful element painted within the viewport
Speed Index 2.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid large layout shifts 2 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Eliminate render-blocking resources Est savings of 700 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Defer offscreen images Est savings of 96 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Max Potential First Input Delay 150 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Render blocking requests Est savings of 760 ms
Requests are blocking the page's initial render, which may delay LCP
Improve image delivery Est savings of 9,428 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Legacy JavaScript Est savings of 11 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers
Server Backend Latencies 10 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Total Blocking Time 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
Efficiently encode images Est savings of 154 KiB
Optimized images load faster and consume less cellular data
Time to Interactive 9.1 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Avoid enormous network payloads Total size was 17,231 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid chaining critical requests 6 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Largest Contentful Paint 8.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce initial server response time Root document took 610 ms
Keep the server response time for the main document short because all other requests depend on it
First Contentful Paint 1.5 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid serving legacy JavaScript to modern browsers Est savings of 11 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Font display Est savings of 20 ms
Consider setting [font-display](https://developer.chrome.com/blog/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
Document request latency Est savings of 530 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Serve images in next-gen formats Est savings of 5,176 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Properly size images Est savings of 2,515 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Use video formats for animated content Est savings of 3,731 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes
Avoid an excessive DOM size 1,259 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Cumulative Layout Shift 0.021
Cumulative Layout Shift measures the movement of visible elements within the viewport
Document uses legible font sizes 99.88% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Minimizes main-thread work 0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Does not use HTTPS 67 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Warning! Your title is not optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Warning! Not found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 22 Oct 2025 19:48:25 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Cache-Control: must-revalidate, no-cache, private
X-Drupal-Dynamic-Cache: UNCACHEABLE (response policy)
Content-language: de
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Expires: Sun, 19 Nov 1978 05:00:00 GMT
X-Generator: Drupal 10 (https://www.drupal.org)
X-Drupal-Cache: UNCACHEABLE (response policy)
X-Cache-Status: MISS
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records