Your Website Score is

Similar Ranking

35
EMPFEHLUNGEN & INSPIRATIONEN FÜR PRODUKTE & DIENSTLEISTUNGEN | PRODUKTORAMA.DE
produktorama.de
35
SORTIMENT - SWEET SENSATION LIFESTYLE BOUTIQUE
sweetsensation.ch
35
DANHAUS – DAS ENERGIESPARHAUS UND FERTIGHAUS
danhaus.de
34
INTERNET APOTHEKE - PRODUKTSUCHMASCHINE - INET-APOTHEKE.COM
inet-apotheke.com
34
TICKETS - CONCERT, SPORT & THEATRE TICKETS | VIAGOGO THE TICKET MARKETPLACE
viagogo.de
34
BOS-FAHRZEUGE - EINSATZFAHRZEUGE UND WACHEN WELTWEIT
bos-fahrzeuge.info
34
TIPPS FÜR KMU UND STARTUP - UNTERNEHMER.DE
unternehmer.de

Latest Sites

23
SPARMC - SPAR MC – SPAR WIE SIE – SPAR WIE DU UND ICH. DAS IST UNSERE VORSTELLUNG VON GRATIS, KOSTENLOS UND SPAREN
sparmc.de
23
PHILOSOPHISCH-ETHISCHE-REZENSIONEN DES 20. UND 21. JAHRHUNDERTS MIT EINEM SCHWERPUNKTTHEMA PRO BUCH
philosophisch-ethische-rezensionen.de
38
REGIONALES BRANCHENBUCH CIIITY.DE
ciiity.de
31
MIETWERKSTATT-PORTAL - DEIN PORTAL FÜR MIETWERKSTÄTTEN
mietwerkstatt-portal.de
10
WERBEGROSSHANDEL - KASSEL - TEXTILIEN VON JAMES & NICHOLSON - SCHILDER - WERBEBANNER - FAHRZEUGBESCHRIFTUNG - KASSEL
werbegrosshandel.de
49
WEBSITE PRÜFEN - BERICHT ÜBER DEN SEO WERT DEINER WEBSITE
website-pruefen.de
24
SEO AGENTUR REGENSBURG | SEITE 1 BEI GOOGLE
positiondigital.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
CloudFlare
CDN

35 danhaus.de Last Updated: 4 weeks

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

Desktop

Mobile

Performance Desktop Score 89%
Best Practices Desktop Score 100%
SEO Desktop Score 92%
PWA Desktop Score 25%
Performance Mobile Score 61%
Best Practices Mobile Score 92%
SEO Mobile Score 92%
PWA Mobile Score 33%
Page Authority Authority 39%
Domain Authority Domain Authority 32%
Moz Rank 3.9/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 44 Characters
DANHAUS – DAS ENERGIESPARHAUS UND FERTIGHAUS
Meta Description 146 Characters
Danhaus – der führende Fertighaushersteller für effiziente Energiesparhäuser im skandinavischen Stil ? als KfW-55, -40 oder -40 Plus Effizienzhaus
Effective URL 22 Characters
https://www.danhaus.de
Excerpt Page content
Danhaus – das Energiesparhaus und Fertighaus Toggle navigation Häuser Die Danhaus Polarserie Aktionen Bildergalerie ...
Keywords Cloud Density
danhaus68 musterhaus18 haus16 auch10 unsere9 energie9 straße8 vertriebsbüro7 nach7 unseren6
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
danhaus 68
musterhaus 18
haus 16
auch 10
unsere 9
energie 9
straße 8
vertriebsbüro 7
nach 7
unseren 6
Google Preview Your look like this in google search result
DANHAUS – DAS ENERGIESPARHAUS UND FERTIGHAUS
https://www.danhaus.de
Danhaus – der führende Fertighaushersteller für effiziente Energiesparhäuser im skandinavischen Stil ? als KfW-55, -40 oder -40 Plus Effizienzhaus
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~63.34 KB
Code Size: ~46.62 KB
Text Size: ~16.72 KB Ratio: 26.40%

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
Enable text compression Potential savings of 8 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Eliminate render-blocking resources Potential savings of 540 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Efficiently encode images Potential savings of 10 KiB
Optimized images load faster and consume less cellular data
Server Backend Latencies 0 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
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
JavaScript execution time 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts 2 elements found
These DOM elements contribute most to the CLS of the page
Avoid enormous network payloads Total size was 6,983 KiB
Large network payloads cost users real money and are highly correlated with long load times
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Defer offscreen images Potential savings of 105 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid chaining critical requests 10 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
Uses efficient cache policy on static assets 2 resources found
A long cache lifetime can speed up repeat visits to your page
Serve images in next-gen formats Potential savings of 1,909 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
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
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid an excessive DOM size 1,236 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)
Keep request counts low and transfer sizes small 107 requests • 6,983 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Initial server response time was short Root document took 140 ms
Keep the server response time for the main document short because all other requests depend on it
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
Reduce unused CSS Potential savings of 21 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Reduce unused JavaScript Potential savings of 67 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Time to Interactive 1.4 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint 1.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Cumulative Layout Shift 0.148
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
Avoid serving legacy JavaScript to modern browsers Potential savings of 8 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Properly size images Potential savings of 2,264 KiB
Serve images that are appropriately-sized to save cellular data and improve load time

Mobile

Mobile Screenshot
Largest Contentful Paint 20.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Server Backend Latencies 0 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
Reduce unused CSS Potential savings of 22 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Initial server response time was short Root document took 100 ms
Keep the server response time for the main document short because all other requests depend on it
Eliminate render-blocking resources Potential savings of 1,750 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Serve images in next-gen formats Potential savings of 1,909 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Tap targets are not sized appropriately 98% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements
Avoid serving legacy JavaScript to modern browsers Potential savings of 8 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
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
First Meaningful Paint 3.7 s
First Meaningful Paint measures when the primary content of a page is visible
Max Potential First Input Delay 220 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid large layout shifts 4 elements found
These DOM elements contribute most to the CLS of the page
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Document uses legible font sizes 99.91% 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
JavaScript execution time 0.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 2.8 s
First Contentful Paint marks the time at which the first text or image is painted
Total Blocking Time 180 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid long main-thread tasks 6 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 66 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Cumulative Layout Shift 0.128
Cumulative Layout Shift measures the movement of visible elements within the viewport
Defer offscreen images Potential savings of 972 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 1,720 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 4.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Efficiently encode images Potential savings of 10 KiB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 8 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Avoid chaining critical requests 10 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
Keep request counts low and transfer sizes small 103 requests • 6,965 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Minimize main-thread work 2.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive 13.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Avoid an excessive DOM size 1,175 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)
Avoid enormous network payloads Total size was 6,965 KiB
Large network payloads cost users real money and are highly correlated with long load times
Uses efficient cache policy on static assets 2 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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

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
Congratulations! Your description is 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
Warning! Your website is not SSL secured (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
Congratulations! Your Domain Authority is good
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


						
DNS Records DNS Resource Records associated with a hostname
View DNS Records