Your Website Score is

Similar Ranking

18
STARTSEITE | ONMYLIST.DE
onmylist.de
18
503 SERVICE TEMPORARILY UNAVAILABLE
triumph-lifttechnik.de
18
18
KAFFEEVOLLAUTOMATEN MIETEN, LEASEN ODER KAUFEN | CAFFIA LEIPZIG
caffia.de
18
AUTOUNFALL.INFO
autounfall.info
18
WEIHNACHTSDEKOBASTELN
weihnachtsdekobasteln.de
18
NEMESO - NEW MEDIA SOLUTIONS | INTERNET SERVICE PROVIDER BERLIN
nemeso.de

Latest Sites

26
HERZLICH WILLKOMMEN AUF RECASTGAMING.DE
recastgaming.de
93
BIEDERMEIERGITARRE - GITARRENMUSIK IM FRÜHEN 19. JAHRHUNDERT
biedermeiergitarre.jimdofree.com
31
GESCHICHTE ABITURVORBEREITUNG 2023 - GESCHICHTE KOMPAKT
geschichte-abitur.de
58
MARKETBUSINESSTIMES - AN INITIATIVE TOWARDS THE MODERN WORLD
marketbusinesstimes.com
14
HOME - MALEREIBETRIEB OLEJNIK
malereibetrieb.eu
22
HOME-OFFICE EINRICHTEN - INSPIRATION, TIPPS, WISSENSWERTES
homeoffice-einrichten.de
4
REISESUCHMASCHINE – VOM FLUG BIS ZUR PAUSCHALREISE
reisesuchmaschine.net

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 65%
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 cappuccino7 image7 unsere6 kakao6 wasserautomaten6 mail6
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
cappuccino 7
image 7
unsere 6
kakao 6
wasserautomaten 6
mail 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: ~100.74 KB
Code Size: ~74.19 KB
Text Size: ~26.55 KB Ratio: 26.35%

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
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
Minimize third-party usage Third-party code blocked the main thread for 20 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
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
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
Reduce unused JavaScript Est savings of 108 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
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
Max Potential First Input Delay 160 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
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
First Contentful Paint 0.4 s
First Contentful Paint marks the time at which the first text or image is painted
Does not use HTTPS 65 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
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
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)
Initial server response time was short Root document took 40 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid an excessive DOM size 1,205 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.018
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint 6.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid enormous network payloads Total size was 17,200 KiB
Large network payloads cost users real money and are highly correlated with long load times
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
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
Time to Interactive 6.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Legacy JavaScript Est savings of 38 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/articles/baseline-and-polyfills) features, unless you know you must support legacy browsers
Total Blocking Time 130 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index 0.7 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Efficiently encode images Est savings of 154 KiB
Optimized images load faster and consume less cellular data
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
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
Properly size images Est savings of 1,091 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint element 6,420 ms
This is the largest contentful element painted within the viewport
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

Mobile

Mobile Screenshot
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
Minimizes main-thread work 1.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Properly size images Est savings of 2,515 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Minimize third-party usage Third-party code blocked the main thread for 30 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
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
Avoid large layout shifts 1 layout shift 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)
Legacy JavaScript Est savings of 38 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/articles/baseline-and-polyfills) features, unless you know you must support legacy browsers
Speed Index 3.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint element 55,200 ms
This is the largest contentful element painted within the viewport
Eliminate render-blocking resources Est savings of 710 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
JavaScript execution time 0.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid long main-thread tasks 4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoid enormous network payloads Total size was 17,201 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Efficiently encode images Est savings of 154 KiB
Optimized images load faster and consume less cellular data
Defer offscreen images Est savings of 62 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid an excessive DOM size 1,205 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
Max Potential First Input Delay 310 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
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
Total Blocking Time 290 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 40 ms
Keep the server response time for the main document short because all other requests depend on it
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
First Contentful Paint 1.5 s
First Contentful Paint marks the time at which the first text or image is painted
Document uses legible font sizes 99.97% 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
Time to Interactive 58.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint 55.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Cumulative Layout Shift 0.101
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
Reduce unused JavaScript Est savings of 108 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity

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: Thu, 22 May 2025 18:48:22 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: MISS
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: HIT
X-Cache-Status: MISS
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records