Your Website Score is

Similar Ranking

18
STARTSEITE | ONMYLIST.DE
onmylist.de
18
18
HERZLICH WILLKOMMEN BEI CAFFIA LEIPZIG
caffia.de
18
BUSINESSTECHTIME
businesstechtime.com
18
AUTOUNFALL.INFO
autounfall.info
18
CAFÉ~ELOQUENT | DIE ONLINE KAFFEEPAUSE
cafe-eloquent.de
18
WEIHNACHTSDEKOBASTELN
weihnachtsdekobasteln.de

Latest Sites

22
SEO AGENTUR FÜR KLEINE UND MITTLERE UNTERNEHMEN ???? ENVAL
enval.de
19
AKTIEN LERNEN BUCH – BUCH TIPPS FÜR FINANZIELLE FREIHEIT
buchtipps.info
14
SCHICHTWERKSTATT.DE
schichtwerkstatt.de
25
BIONTECH
biontech.com
35
SORTIMENT - SWEET SENSATION LIFESTYLE BOUTIQUE
sweetsensation.ch
19
FOTO-NOVAK - KOSTBARE MOMENTE UND DARK ART | FOTO-NOVAK
foto-novak.de

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 cafe-eloquent.de Last Updated: 1 week

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

Desktop

Mobile

Performance Desktop Score 95%
Best Practices Desktop Score 96%
SEO Desktop Score 85%
Performance Mobile Score 32%
Best Practices Mobile Score 100%
SEO Mobile Score 85%
Page Authority Authority 26%
Domain Authority Domain Authority 15%
Moz Rank 2.6/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 38 Characters
CAFÉ~ELOQUENT | DIE ONLINE KAFFEEPAUSE
Meta Description 0 Characters
NO DATA
Effective URL 28 Characters
https://www.cafe-eloquent.de
Excerpt Page content
Café~Eloquent | Die Online Kaffeepause Café~Eloquent Suchen Primäres Menü Zum Inhalt springen Unsere Redaktion Beruf / Business Text...
Keywords Cloud Density
oder37 sich36 nicht34 auch31 eine30 sind25 werden20 können19 wird17 über15
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
oder 37
sich 36
nicht 34
auch 31
eine 30
sind 25
werden 20
können 19
wird 17
über 15
Google Preview Your look like this in google search result
CAFÉ~ELOQUENT | DIE ONLINE KAFFEEPAUSE
https://www.cafe-eloquent.de
Café~Eloquent | Die Online Kaffeepause Café~Eloquent Suchen Primäres Menü Zum Inhalt springen Unsere Redaktion Beruf / Business Text...
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~143.56 KB
Code Size: ~82.76 KB
Text Size: ~60.8 KB Ratio: 42.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
Avoid large layout shifts 5 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)
Server Backend Latencies 70 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 28 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
Avoid enormous network payloads Total size was 9,625 KiB
Large network payloads cost users real money and are highly correlated with long load times
Cumulative Layout Shift 0.041
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid an excessive DOM size 4,703 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)
Reduce unused JavaScript Potential savings of 194 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Properly size images Potential savings of 4,836 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint element 920 ms
This is the largest contentful element painted within the viewport
Minimizes main-thread work 1.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Total Blocking Time 60 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Reduce unused CSS Potential savings of 53 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
First Contentful Paint 0.4 s
First Contentful Paint marks the time at which the first text or image is painted
Serve images in next-gen formats Potential savings of 4,726 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Serve static assets with an efficient cache policy 109 resources found
A long cache lifetime can speed up repeat visits to your page
Minify CSS Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes
Max Potential First Input Delay 100 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Network Round Trip Times 10 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
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
Initial server response time was short Root document took 600 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid long main-thread tasks 3 long tasks 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 40 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
Speed Index 2.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Efficiently encode images Potential savings of 778 KiB
Optimized images load faster and consume less cellular data
Minify JavaScript Potential savings of 6 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Largest Contentful Paint 0.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Time to Interactive 3.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Defer offscreen images Potential savings of 3,622 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Mobile

Mobile Screenshot
First Contentful Paint 2.0 s
First Contentful Paint marks the time at which the first text or image is painted
Cumulative Layout Shift 0.295
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minify CSS Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes
Avoid enormous network payloads Total size was 5,301 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid chaining critical requests 27 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
Total Blocking Time 870 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Largest Contentful Paint 7.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce unused CSS Potential savings of 54 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Document uses legible font sizes 100% 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
Reduce initial server response time Root document took 640 ms
Keep the server response time for the main document short because all other requests depend on it
Efficiently encode images Potential savings of 207 KiB
Optimized images load faster and consume less cellular data
Avoid long main-thread tasks 13 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Reduce unused JavaScript Potential savings of 193 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Time to Interactive 19.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Defer offscreen images Potential savings of 3,920 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Serve static assets with an efficient cache policy 103 resources found
A long cache lifetime can speed up repeat visits to your page
Speed Index 7.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Server Backend Latencies 20 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 440 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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)
Serve images in next-gen formats Potential savings of 2,852 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Eliminate render-blocking resources Potential savings of 460 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Reduce JavaScript execution time 2.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Reduce the impact of third-party code Third-party code blocked the main thread for 910 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
Largest Contentful Paint element 7,120 ms
This is the largest contentful element painted within the viewport
Minimize main-thread work 6.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Properly size images Potential savings of 84 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Minify JavaScript Potential savings of 6 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Avoid an excessive DOM size 4,703 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)
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
First Meaningful Paint 2.1 s
First Meaningful Paint measures when the primary content of a page is visible

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
Congratulations! Your title is optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've 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.
Broken Links
Congratulations! You not have broken links View links

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/2 200 
link: ; rel="https://api.w.org/", ; rel="alternate"; type="application/json", ; rel=shortlink
set-cookie: mc_session_ids[default]=0355f32fcf3b8af9c6a76f3cdde8936151fb0e07; expires=Sat, 18-May-2024 00:29:20 GMT; Max-Age=300; path=/; secure; HttpOnly
set-cookie: mc_session_ids[multi][0]=21b8e4b8ea80c4b781e9f5585afb6fc5f5a8a2e3; expires=Sat, 18-May-2024 00:29:20 GMT; Max-Age=300; path=/
set-cookie: mc_session_ids[multi][1]=296ad496fdd0b9351b0468c29157a7250faa0874; expires=Sat, 18-May-2024 00:29:20 GMT; Max-Age=300; path=/
set-cookie: mc_session_ids[multi][2]=ea1c91e9b9c5c0c6ec19d3a27749598b188a1ff0; expires=Sat, 18-May-2024 00:29:20 GMT; Max-Age=300; path=/
set-cookie: mc_session_ids[multi][3]=3205c77329768de7b6cb7c11afe4b0354f0c085e; expires=Sat, 18-May-2024 00:29:20 GMT; Max-Age=300; path=/
set-cookie: mc_session_ids[multi][4]=99841d098b645c815f6d2fb352772dd2abeae1b8; expires=Sat, 18-May-2024 00:29:20 GMT; Max-Age=300; path=/
vary: Accept-Encoding,User-Agent
content-type: text/html; charset=UTF-8
date: Sat, 18 May 2024 00:24:20 GMT
server: Apache
DNS Records DNS Resource Records associated with a hostname
View DNS Records