hygi.de Website Information
Daily Unique Visits: 3,660
Daily Page Views: 14,640
Income Per Day: $41
Estimated Value: $22,140
This website is located in Germany and is using following IP address 188.138.67.155. See the complete list of popular websites hosted in Germany.
hygi.de is registered under .DE top-level domain. Please check other sites in .DE zone.
Website hygi.de is using the following name servers:
- ns.udag.net
- ns.udag.de
- ns.udag.org
and is probably hosted by ScaleUp Technologies GmbH & Co. KG. See the full list of other websites hosted by ScaleUp Technologies GmbH & Co. KG.
The highest website hygi.de position in Alexa rank database was 8194 and the lowest rank position was 865179. Current position of hygi.de in Alexa rank database is 342890.
Desktop speed score of hygi.de (92/100) is better than the results of 90.97% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of hygi.de (95/100) is better than the results of 39.69% of other sites and means that the page is mobile-friendly.
Mobile speed score of hygi.de (71/100) is better than the results of 78.26% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
hygi.de Alexa Rank
The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.
hygi.de whois
WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.
Status: connect
hygi.de server information
Servers Location
hygi.de desktop page speed rank
Last tested: 2018-10-08
hygi.de Desktop Speed Test Quick Summary
priority - 4Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://siegel.ausgezeichnet.org/asset/images/widgets/bg-embed-m.png (15 minutes)
https://siegel.ausgezeichnet.org/asset/images/widgets/logo-embed-m.png (15 minutes)
https://siegel.ausgezeichnet.org/asset/images/widgets/rating-5-cent-m.png (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-KM7WKS (15 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://cdn.stickyadstv.com/one-shot/empty.gif? (2 hours)
https://www.google-analytics.com/analytics.js (2 hours)
https://cdn.hygi.eu/images/cms/seal/seal-shop-4.png (4 hours)
priority - 3Reduce server response time
In our test, your server responded in 0.48 seconds.
priority - 1Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 5.2KiB (66% reduction).
Compressing and resizing https://www.hygi.de/images/newsletter/nl-banner-icon3@2x.png could save 1.4KiB (54% reduction).
Compressing https://www.hygi.de/images/icons/deutschland_30.jpg could save 996B (71% reduction).
Compressing https://www.hygi.de/images/icons/austria_30.jpg could save 995B (71% reduction).
Compressing https://cotads.adscale.de/ads/pixel/1by1.png?uid=424921539039221628 could save 252B (78% reduction).
hygi.de Desktop Resource Breakdown
| Total Resources | 209 |
| Number of Hosts | 46 |
| Static Resources | 152 |
| JavaScript Resources | 13 |
| CSS Resources | 3 |
hygi.de mobile page speed rank
Last tested: 2018-10-08
hygi.de Mobile Speed Test Quick Summary
priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
priority - 6Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://siegel.ausgezeichnet.org/asset/images/widgets/bg-embed-m.png (15 minutes)
https://siegel.ausgezeichnet.org/asset/images/widgets/logo-embed-m.png (15 minutes)
https://siegel.ausgezeichnet.org/asset/images/widgets/rating-5-cent-m.png (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-KM7WKS (15 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://cdn.hygi.eu/images/cms/seal/seal-shop-9.png (4 hours)
priority - 3Reduce server response time
In our test, your server responded in 0.39 seconds.
priority - 1Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 9KiB (46% reduction).
Compressing https://cdn.hygi.eu/images/cms/brand-logo/m_floors…401c3eecaa78c19880.jpg could save 2.3KiB (63% reduction).
Compressing https://cdn.hygi.eu/images/cms/brand-logo/m_sonax_…30f5dc56e46610bd4a.jpg could save 1.3KiB (56% reduction).
Compressing https://cdn.hygi.eu/images/cms/pageAction-productG…71a1091d681a8b1388.jpg could save 981B (30% reduction).
Compressing https://www.hygi.de/images/newsletter/nl-banner-icon3@2x.png could save 757B (30% reduction).
Compressing https://cdn.hygi.eu/images/cms/pageAction-productG…cd81ee995dc4d95be4.jpg could save 732B (29% reduction).
Compressing https://cdn.hygi.eu/images/cms/brand-logo/m_braban…3883a6e1fcaa6a20c8.jpg could save 192B (15% reduction).
hygi.de Mobile Resource Breakdown
| Total Resources | 125 |
| Number of Hosts | 23 |
| Static Resources | 100 |
| JavaScript Resources | 13 |
| CSS Resources | 3 |
hygi.de mobile page usability
Last tested: 2018-10-08
hygi.de Mobile Usability Test Quick Summary
priority - 4Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
<div class="site-cart">0 Warenkorb 0,…te zur Auswahl</div> is close to 1 other tap targets.<div class="site-cart">0 Warenkorb 0,…te zur Auswahl</div> and 1 others are close to other tap targets.<a href="/cart" class="cart-flyout-header toggle">0 Warenkorb 0,…(ohne Rabatt)</a> is close to 1 other tap targets.<li id="metaAccount" class="level-1 nav-it…light dropdown">Mein Konto</li> and 1 others are close to other tap targets.<li id="metaAccount" class="level-1 nav-it…light dropdown">Mein Konto</li> and 3 others are close to other tap targets.<a href="/account" class="level-1 nav-item-link">Mein Konto</a> and 1 others are close to other tap targets.<button class="toggle-offcanvas">Kategorien</button> is close to 1 other tap targets.<li class="slick-active">1</li> and 2 others are close to other tap targets.<button id="slick-slide-control70" type="button">1</button> is close to 2 other tap targets.<button id="slick-slide-control71" type="button">2</button> and 1 others are close to other tap targets.The tap target
<a href="https://www.hy…er?stid=PG1025">Abfallkörbe & Abfalleimer</a> is close to 2 other tap targets.The tap target
<a href="https://www.hy…ittel-reiniger">Reinigungsmittel</a> and 7 others are close to other tap targets.The tap target
<a href="/account">Mein Konto</a> and 15 others are close to other tap targets.hygi.de HTML validation
Errors
Using the “meta” element to specify the document-wide default language is obsolete. Consider specifying the language on the root element instead.
"...tel"> <meta http-equiv="content-language" content="de"> <..."
Bad value “Pragma” for attribute “http-equiv” on element “meta”.
"..."de"> <meta http-equiv="Pragma" content="no-cache"> <..."
Bad value “Expires” for attribute “http-equiv” on element “meta”.
"...che"> <meta http-equiv="Expires" content="-1"> <..."
CSS: “font-size”: only “0” can be a “unit”. You must put a unit after your number.
"...font-size:28 + px!..." Line: 45 Column: 48636 - 48637
"...font-size:24}.prod..." Line: 45 Column: 57103 - 57112
"...nt-size:18!important;paddi..."
CSS: Parse Error.
"... + px!important}.page-hero .he..."
Attribute “name” not allowed on element “link” at this point.
"...yle> <link rel="preload" name="proxima-cond-regular" href="https://cdn.hygi.eu/fonts/typo/1132243/317fd159-159d-4870-a01f-ef9d5a71d5b3.woff2?v3037" as="font" type="font/woff2"> <..." Line: 52 Column: 5 - 38
"...ff2"> <link rel="preload" name="proxima-cond-bold" href="https://cdn.hygi.eu/fonts/typo/1132267/b5a71150-9cc6-412c-a234-f1c2cbcd738f.woff2?v3037" as="font" type="font/woff2"> <..." Line: 54 Column: 5 - 38
"...ff2"> <link rel="preload" name="hygi-icons" href="https://cdn.hygi.eu/fonts/icons/hygi-icons.woff2?v3037" as="font" type="font/woff2"> <..."
Saw “<?”. Probable cause: Attempt to use an XML processing instruction in HTML. (XML processing instructions are not supported in HTML.)
"...y: none"> <?xml version="1..."
Element “div” not allowed as child of element “h3” in this context. (Suppressing further errors from this subtree.)
"...> <div class="toggle-nav"> ..."
Element “notifications” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.)
"... <notifications group="global" position="top center" classes="hygi-notify"> ..."
Element “modal” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.)
"... <modal name="comparisonListDialog" class="dialog-full" header="Ihre hygi.de Vergleichsliste"> ..."
Bad value “auto” for attribute “width” on element “img”: Expected a digit but saw “a” instead.
"... <img width="auto" height="150" src="https://cdn.hygi.eu/images/cms/seal/seal-shop-3.png" alt="Kundenbewertungen"> ..."
Warnings
The “banner” role is unnecessary for element “header”.
"... <header class="site-header" role="banner"> ..."
The “main” role is unnecessary for element “main”.
"... <main class="main-content mainContent" id="mainContent" role="main"> ..."
Article lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all articles.
"... <article class="image-teaser"> <..." Line: 1456 Column: 13 - 42
"... <article class="image-teaser"> <..." Line: 1471 Column: 13 - 42
"... <article class="image-teaser"> <..." Line: 1483 Column: 13 - 42
"... <article class="image-teaser"> <..." Line: 1495 Column: 13 - 42
"... <article class="image-teaser"> <..."
Attribute “:class” is not serializable as XML 1.0.
"... <div class="alert" :class="props.item.type"> ..."
Attribute “@click” is not serializable as XML 1.0.
"... <button class="btn text close-block" @click="props.close"> ..."
The “type” attribute is unnecessary for JavaScript resources.
".../script> <script type="text/javascript"> i..."
hygi.de similar domains
www.hygi.net
www.hygi.org
www.hygi.info
www.hygi.biz
www.hygi.us
www.hygi.mobi
www.ygi.de
www.hygi.de
www.bygi.de
www.hbygi.de
www.bhygi.de
www.gygi.de
www.hgygi.de
www.ghygi.de
www.yygi.de
www.hyygi.de
www.yhygi.de
www.uygi.de
www.huygi.de
www.uhygi.de
www.jygi.de
www.hjygi.de
www.jhygi.de
www.nygi.de
www.hnygi.de
www.nhygi.de
www.hgi.de
www.htgi.de
www.hytgi.de
www.htygi.de
www.hggi.de
www.hyggi.de
www.hhgi.de
www.hyhgi.de
www.hhygi.de
www.hugi.de
www.hyugi.de
www.hyi.de
www.hyfi.de
www.hygfi.de
www.hyfgi.de
www.hyvi.de
www.hygvi.de
www.hyvgi.de
www.hyti.de
www.hygti.de
www.hybi.de
www.hygbi.de
www.hybgi.de
www.hyyi.de
www.hygyi.de
www.hyhi.de
www.hyghi.de
www.hyg.de
www.hygu.de
www.hygiu.de
www.hygui.de
www.hygj.de
www.hygij.de
www.hygji.de
www.hygk.de
www.hygik.de
www.hygki.de
www.hygo.de
www.hygio.de
www.hygoi.de
hygi.de Ping
Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.
hygi.de TRACEROUTE
Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.