HUG-GE.CH HUG - Hôpitaux universitaires de Genève

hug-ge.ch Website Information

Daily Unique Visits: 11,892

Daily Page Views: 59,460

Income Per Day: $149

Estimated Value: $89,400

This website is located in Switzerland and is using following IP address 129.195.247.50. See the complete list of popular websites hosted in Switzerland.

hug-ge.ch is registered under .CH top-level domain. Please check other sites in .CH zone.

Website hug-ge.ch is using the following name servers:

  • NS1.hcuge.ch
  • NS2.hcuge.ch

and is probably hosted by SWITCH. See the full list of other websites hosted by SWITCH.

The highest website hug-ge.ch position in Alexa rank database was 34517 and the lowest rank position was 982354. Current position of hug-ge.ch in Alexa rank database is 114572.

Desktop speed score of hug-ge.ch (82/100) is better than the results of 74.03% of other sites and shows that the page is performing great on desktop computers.

Mobile usability score of hug-ge.ch (96/100) is better than the results of 46.59% of other sites and means that the page is mobile-friendly.

Mobile speed score of hug-ge.ch (72/100) is better than the results of 79.79% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

hug-ge.ch 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.


hug-ge.ch 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.


Requests of this client are not permitted. Please use https://www.nic.ch/whois/ for queries.

hug-ge.ch server information

Servers Location

hug-ge.ch desktop page speed rank

Last tested: 2017-06-04


Desktop Speed Medium
82/100

hug-ge.ch Desktop Speed Test Quick Summary


priority - 7Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 72.6KiB (59% reduction).

Compressing http://www.hug-ge.ch/sites/interhug/files/googlean…cs/analytics.js?oqx30p could save 17.3KiB (58% reduction).
Compressing http://www.hug-ge.ch/sites/all/libraries/piwik/piwik.js could save 11.7KiB (59% reduction).
Compressing http://www.hug-ge.ch/sites/interhug/files/images/share/facebook.svg could save 7.7KiB (58% reduction).
Compressing http://www.hug-ge.ch/sites/interhug/files/images/share/twitter.svg could save 7.7KiB (58% reduction).
Compressing http://www.hug-ge.ch/sites/interhug/files/images/share/youtube.svg could save 7.7KiB (58% reduction).
Compressing http://www.hug-ge.ch/sites/interhug/files/images/share/googleplus.svg could save 7.7KiB (58% reduction).
Compressing http://www.hug-ge.ch/sites/interhug/files/images/share/linkedin.svg could save 7.6KiB (58% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/hug/js/behaviours.js could save 3.1KiB (68% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/hug/js/init.min.js could save 2.3KiB (70% reduction).

priority - 6Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 7 blocking script resources and 8 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://www.hug-ge.ch/sites/interhug/files/js/js_dV…Oe2JqXsSGw3I4Wunee0.js
http://www.hug-ge.ch/sites/interhug/files/js/js_Ah…X3vWEShkA2r9he2D64s.js
http://www.hug-ge.ch/sites/interhug/files/js/js_sM…hI1II1TO1nq1NCGTHBg.js
http://www.hug-ge.ch/sites/interhug/files/js/js_fn…uQWhi5DMIlgQlazgm-A.js
http://www.hug-ge.ch/sites/interhug/files/js/js_ri…wPjsT-NHgnqRNg1KFbk.js
http://www.hug-ge.ch/sites/interhug/files/js/js_4k…8dgijelwGU5rqE3ZjlM.js
http://www.hug-ge.ch/sites/all/themes/hug/js/init.min.js

Optimize CSS Delivery of the following:

http://www.hug-ge.ch/sites/interhug/files/css/css_…xu4WO-qwma6Xer30m4.css
http://www.hug-ge.ch/sites/interhug/files/css/css_…Cq0Lyv1YnyoEj3kxiU.css
http://www.hug-ge.ch/sites/interhug/files/css/css_…wfvwjwbw5ZeoS5Jk8k.css
http://www.hug-ge.ch/sites/interhug/files/css/css_…1x2dQDZG6JXbM5tyYc.css
http://www.hug-ge.ch/sites/interhug/files/css/css_…pcpg-DhFt2fdYViv24.css
http://www.hug-ge.ch/sites/interhug/files/css/css_…7ob93Ustichh2-2KYk.css
http://www.hug-ge.ch/sites/interhug/files/css/css_…XkaSm6pcBJLjLgUCjQ.css
http://www.hug-ge.ch/sites/interhug/files/css/css_…0lR4bT9OdnXSGQ6DEI.css

priority - 5Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 47.5KiB (43% reduction).

Compressing http://www.hug-ge.ch/sites/interhug/files/zoom/zoom-oncologie-mai2013.jpg could save 23.8KiB (37% reduction).
Compressing https://www.gstatic.com/gmeviewer/images/MyMaps_Icons003.png could save 3.1KiB (36% reduction).
Compressing and resizing http://www.hug-ge.ch/sites/interhug/files/styles/s…_web.jpg?itok=pwPLRuTl could save 2.6KiB (66% reduction).
Compressing and resizing http://www.hug-ge.ch/sites/interhug/files/styles/s…x200.jpg?itok=PIOvYNQ9 could save 2.3KiB (64% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/logo.png could save 1.3KiB (19% reduction).
Compressing https://www.gstatic.com/mapspro/images/google-my-maps-logo-small-001.png could save 1.2KiB (41% reduction).
Compressing and resizing http://www.hug-ge.ch/sites/interhug/files/styles/s…-act.jpg?itok=nxIcaA7H could save 1.1KiB (64% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/hug/img/loupe.png could save 970B (68% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img/loupe.png could save 970B (68% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/hug/img/icon/icon_url.png could save 952B (87% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img/home.png could save 939B (75% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img…ite/left_arrow_blc.png could save 937B (90% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img…hare-googleplus-16.png could save 908B (61% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img/homepage/slider_vert.png could save 893B (35% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img…e/share-twitter-16.png could save 888B (64% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/hug/img/plus-green.png could save 875B (89% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img…/share-linkedin-16.png could save 873B (63% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img…/share-facebook-16.png could save 869B (69% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img/fleche.png could save 868B (85% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img…e/share-youtube-16.png could save 851B (59% reduction).
Compressing https://www.gstatic.com/gmeviewer/images/selection_2x-000.png could save 617B (22% reduction).

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 10.3KiB (20% reduction).

Minifying http://www.hug-ge.ch/sites/interhug/files/js/js_dV…Oe2JqXsSGw3I4Wunee0.js could save 5.4KiB (17% reduction) after compression.
Minifying http://www.hug-ge.ch/sites/all/themes/hug/js/behaviours.js could save 1.5KiB (35% reduction).
Minifying http://www.hug-ge.ch/sites/interhug/files/js/js_fn…uQWhi5DMIlgQlazgm-A.js could save 1.2KiB (12% reduction) after compression.
Minifying http://www.hug-ge.ch/sites/interhug/files/js/js_ri…wPjsT-NHgnqRNg1KFbk.js could save 1.1KiB (44% reduction) after compression.
Minifying http://www.hug-ge.ch/sites/interhug/files/js/js_sM…hI1II1TO1nq1NCGTHBg.js could save 1,011B (41% reduction) after compression.

priority - 0Leverage 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://maps.googleapis.com/maps/api/js?v=3.27&cli…visualization,geometry (30 minutes)

hug-ge.ch Desktop Resource Breakdown

Total Resources125
Number of Hosts19
Static Resources98
JavaScript Resources33
CSS Resources11

hug-ge.ch mobile page speed rank

Last tested: 2017-05-25


Mobile Speed Medium
72/100

hug-ge.ch Mobile Speed Test Quick Summary


priority - 24Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 7 blocking script resources and 8 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://www.hug-ge.ch/sites/interhug/files/js/js_dV…Oe2JqXsSGw3I4Wunee0.js
http://www.hug-ge.ch/sites/interhug/files/js/js_Ah…X3vWEShkA2r9he2D64s.js
http://www.hug-ge.ch/sites/interhug/files/js/js_sM…hI1II1TO1nq1NCGTHBg.js
http://www.hug-ge.ch/sites/interhug/files/js/js_fn…uQWhi5DMIlgQlazgm-A.js
http://www.hug-ge.ch/sites/interhug/files/js/js_ri…wPjsT-NHgnqRNg1KFbk.js
http://www.hug-ge.ch/sites/interhug/files/js/js_4k…8dgijelwGU5rqE3ZjlM.js
http://www.hug-ge.ch/sites/all/themes/hug/js/init.min.js

Optimize CSS Delivery of the following:

http://www.hug-ge.ch/sites/interhug/files/css/css_…xu4WO-qwma6Xer30m4.css
http://www.hug-ge.ch/sites/interhug/files/css/css_…Cq0Lyv1YnyoEj3kxiU.css
http://www.hug-ge.ch/sites/interhug/files/css/css_…wfvwjwbw5ZeoS5Jk8k.css
http://www.hug-ge.ch/sites/interhug/files/css/css_…1x2dQDZG6JXbM5tyYc.css
http://www.hug-ge.ch/sites/interhug/files/css/css_…pcpg-DhFt2fdYViv24.css
http://www.hug-ge.ch/sites/interhug/files/css/css_…7ob93Ustichh2-2KYk.css
http://www.hug-ge.ch/sites/interhug/files/css/css_…XkaSm6pcBJLjLgUCjQ.css
http://www.hug-ge.ch/sites/interhug/files/css/css_…0lR4bT9OdnXSGQ6DEI.css

priority - 7Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 72.5KiB (59% reduction).

Compressing http://www.hug-ge.ch/sites/interhug/files/googlean…cs/analytics.js?oqeqv6 could save 17.2KiB (58% reduction).
Compressing http://www.hug-ge.ch/sites/all/libraries/piwik/piwik.js could save 11.7KiB (59% reduction).
Compressing http://www.hug-ge.ch/sites/interhug/files/images/share/facebook.svg could save 7.7KiB (58% reduction).
Compressing http://www.hug-ge.ch/sites/interhug/files/images/share/twitter.svg could save 7.7KiB (58% reduction).
Compressing http://www.hug-ge.ch/sites/interhug/files/images/share/youtube.svg could save 7.7KiB (58% reduction).
Compressing http://www.hug-ge.ch/sites/interhug/files/images/share/googleplus.svg could save 7.7KiB (58% reduction).
Compressing http://www.hug-ge.ch/sites/interhug/files/images/share/linkedin.svg could save 7.6KiB (58% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/hug/js/behaviours.js could save 3.1KiB (68% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/hug/js/init.min.js could save 2.3KiB (70% reduction).

priority - 5Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 45KiB (39% reduction).

Compressing http://www.hug-ge.ch/sites/interhug/files/zoom/zoom-oncologie-mai2013.jpg could save 23.8KiB (37% reduction).
Compressing https://www.gstatic.com/gmeviewer/images/MyMaps_Icons2x003.png could save 6.7KiB (35% reduction).
Compressing https://www.gstatic.com/gmeviewer/images/MyMaps_Icons003.png could save 3.1KiB (36% reduction).
Compressing https://www.gstatic.com/mapspro/images/google-my-maps-logo-small-2x-001.png could save 2.6KiB (43% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/logo.png could save 1.3KiB (19% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/hug/img/icon/icon_url.png could save 952B (87% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img…ite/left_arrow_blc.png could save 937B (90% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img…hare-googleplus-16.png could save 908B (61% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img…e/share-twitter-16.png could save 888B (64% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img…/share-linkedin-16.png could save 873B (63% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img…/share-facebook-16.png could save 869B (69% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img/fleche.png could save 868B (85% reduction).
Compressing http://www.hug-ge.ch/sites/all/themes/interhug/img…e/share-youtube-16.png could save 851B (59% reduction).
Compressing https://www.gstatic.com/gmeviewer/images/selection_2x-000.png could save 617B (22% reduction).

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 10.3KiB (20% reduction).

Minifying http://www.hug-ge.ch/sites/interhug/files/js/js_dV…Oe2JqXsSGw3I4Wunee0.js could save 5.4KiB (17% reduction) after compression.
Minifying http://www.hug-ge.ch/sites/all/themes/hug/js/behaviours.js could save 1.5KiB (35% reduction).
Minifying http://www.hug-ge.ch/sites/interhug/files/js/js_fn…uQWhi5DMIlgQlazgm-A.js could save 1.2KiB (12% reduction) after compression.
Minifying http://www.hug-ge.ch/sites/interhug/files/js/js_ri…wPjsT-NHgnqRNg1KFbk.js could save 1.1KiB (44% reduction) after compression.
Minifying http://www.hug-ge.ch/sites/interhug/files/js/js_sM…hI1II1TO1nq1NCGTHBg.js could save 1,011B (41% reduction) after compression.

priority - 1Leverage 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://maps.googleapis.com/maps/api/js?v=3.27&cli…visualization,geometry (30 minutes)

hug-ge.ch Mobile Resource Breakdown

Total Resources124
Number of Hosts19
Static Resources99
JavaScript Resources33
CSS Resources11

hug-ge.ch mobile page usability

Last tested: 2017-05-25


Mobile Usability Good
96/100

hug-ge.ch Mobile Usability Test Quick Summary


priority - 3Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 421 CSS pixels wide, but the viewport is only 412 CSS pixels wide. The following elements fall outside the viewport:

The element <div id="last-updated">Dernière mise…r : 24/05/2017</div> falls outside the viewport.

priority - 0Size 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.

The tap target <div class="nJjxad-bEDTcc-…-n0tgWb-Q4BLdf"></div> is close to 1 other tap targets.
The tap target <div class="nJjxad-m9bMae-…-n0tgWb-Q4BLdf"></div> is close to 1 other tap targets.
The tap target <a href="//www.google.c…erms_maps.html">Terms</a> is close to 3 other tap targets.
The tap target <div class="VIpgJd-bMcfAe">5 mi</div> is close to 3 other tap targets.
The tap target <a href="https://www.fa…itaires.geneve"></a> and 4 others are close to other tap targets.
The tap target <a href="https://plus.g…VIDEOHUG/posts"></a> is close to 1 other tap targets.

hug-ge.ch HTML validation

Errors

Bad value “last-modified” for attribute “http-equiv” on element “meta”.

Line: 40 Column: 5 - 74
"... <meta http-equiv="last-modified" content="2018-05-29@10:44:12 CEST" /> <..."

When the attribute “xml:lang” in no namespace is specified, the element must also have the attribute “lang” present with the same value.

Line: 114 Column: 67 - 138
"...en first"><a href="https://www.hug-ge.ch/en/" class="language-link" xml:lang="en">en</a>..." Line: 115 Column: 28 - 103
"...t active"><a href="https://www.hug-ge.ch/" class="language-link active" xml:lang="fr">fr</a>..."

Element “div” not allowed as child of element “span” in this context. (Suppressing further errors from this subtree.)

Line: 248 Column: 22 - 51
"... <span><div class=" slideshowtextbg"> <di..." Line: 259 Column: 22 - 51
"... <span><div class=" slideshowtextbg"> <di..." Line: 270 Column: 22 - 60
"... <span><div class="zoom_vert slideshowtextbg"> <di..." Line: 283 Column: 22 - 51
"... <span><div class=" slideshowtextbg"> <di..."

Attribute “datatype” not allowed on element “span” at this point.

Line: 411 Column: 72 - 184
"...-content"><span class="date-display-single" property="dc:date" datatype="xsd:dateTime" content="2018-08-14T00:00:00+02:00">14 Aoû..." Line: 414 Column: 72 - 184
"...-content"><span class="date-display-single" property="dc:date" datatype="xsd:dateTime" content="2018-08-24T00:00:00+02:00">24 Aoû..." Line: 417 Column: 105 - 216
"...ay-range"><span class="date-display-start" property="dc:date" datatype="xsd:dateTime" content="2018-08-27T00:00:00+02:00">27 Aoû..." Line: 417 Column: 239 - 348
"...</span> - <span class="date-display-end" property="dc:date" datatype="xsd:dateTime" content="2018-08-29T00:00:00+02:00">29 Aoû..." Line: 420 Column: 72 - 184
"...-content"><span class="date-display-single" property="dc:date" datatype="xsd:dateTime" content="2018-08-28T00:00:00+02:00">28 Aoû..."

Attribute “content” not allowed on element “span” at this point.

Line: 411 Column: 72 - 184
"...-content"><span class="date-display-single" property="dc:date" datatype="xsd:dateTime" content="2018-08-14T00:00:00+02:00">14 Aoû..." Line: 414 Column: 72 - 184
"...-content"><span class="date-display-single" property="dc:date" datatype="xsd:dateTime" content="2018-08-24T00:00:00+02:00">24 Aoû..." Line: 417 Column: 105 - 216
"...ay-range"><span class="date-display-start" property="dc:date" datatype="xsd:dateTime" content="2018-08-27T00:00:00+02:00">27 Aoû..." Line: 417 Column: 239 - 348
"...</span> - <span class="date-display-end" property="dc:date" datatype="xsd:dateTime" content="2018-08-29T00:00:00+02:00">29 Aoû..." Line: 420 Column: 72 - 184
"...-content"><span class="date-display-single" property="dc:date" datatype="xsd:dateTime" content="2018-08-28T00:00:00+02:00">28 Aoû..."

Element “dl” is missing a required child element.

Line: 718 Column: 1 - 4
"... <dl> <dd>8 hôpi..."

Element “dl” is missing a required instance of child element “dd”.

Line: 722 Column: 1 - 5
"...isse</dt> </dl> </d..."

Bad value “100%” for attribute “width” on element “iframe”: Expected a digit but saw “%” instead.

Line: 733 Column: 8 - 151
"..."> <p><iframe frameborder="0" height="300" scrolling="no" src="https://www.google.com/maps/d/u/0/embed?mid=1MC3u7tffYwZl0mvwYypVJgq2ABU" width="100%"></ifra..." Line: 744 Column: 8 - 151
"..."> <p><iframe frameborder="0" height="300" scrolling="no" src="https://www.google.com/maps/d/u/0/embed?mid=17GwwjGu3uGi21mgYL9KsYTXdz28" width="100%"></ifra..."

The “frameborder” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 733 Column: 8 - 151
"..."> <p><iframe frameborder="0" height="300" scrolling="no" src="https://www.google.com/maps/d/u/0/embed?mid=1MC3u7tffYwZl0mvwYypVJgq2ABU" width="100%"></ifra..." Line: 744 Column: 8 - 151
"..."> <p><iframe frameborder="0" height="300" scrolling="no" src="https://www.google.com/maps/d/u/0/embed?mid=17GwwjGu3uGi21mgYL9KsYTXdz28" width="100%"></ifra..."

The “scrolling” attribute on the “iframe” element is obsolete. Use CSS instead.

Line: 733 Column: 8 - 151
"..."> <p><iframe frameborder="0" height="300" scrolling="no" src="https://www.google.com/maps/d/u/0/embed?mid=1MC3u7tffYwZl0mvwYypVJgq2ABU" width="100%"></ifra..." Line: 744 Column: 8 - 151
"..."> <p><iframe frameborder="0" height="300" scrolling="no" src="https://www.google.com/maps/d/u/0/embed?mid=17GwwjGu3uGi21mgYL9KsYTXdz28" width="100%"></ifra..."

The “align” attribute on the “img” element is obsolete. Use CSS instead.

Line: 832 Column: 58 - 372
"...-the-net"><img align="left" alt="Ce site respecte les principes de la charte HONcode de HON" height="31" hspace="2" src="https://www.honcode.ch/HONcode/Seal/French/HONConduct923172_s2.gif" style="border: 0; float: left; margin: 2px;" title="Ce site respecte les principes de la charte HONcode de HON" vspace="2" width="69" /><br />..."

The “hspace” attribute on the “img” element is obsolete. Use CSS instead.

Line: 832 Column: 58 - 372
"...-the-net"><img align="left" alt="Ce site respecte les principes de la charte HONcode de HON" height="31" hspace="2" src="https://www.honcode.ch/HONcode/Seal/French/HONConduct923172_s2.gif" style="border: 0; float: left; margin: 2px;" title="Ce site respecte les principes de la charte HONcode de HON" vspace="2" width="69" /><br />..."

The “vspace” attribute on the “img” element is obsolete. Use CSS instead.

Line: 832 Column: 58 - 372
"...-the-net"><img align="left" alt="Ce site respecte les principes de la charte HONcode de HON" height="31" hspace="2" src="https://www.honcode.ch/HONcode/Seal/French/HONConduct923172_s2.gif" style="border: 0; float: left; margin: 2px;" title="Ce site respecte les principes de la charte HONcode de HON" vspace="2" width="69" /><br />..."

Warnings

The “name” attribute is obsolete. Consider putting an “id” attribute on the nearest container instead.

Line: 102 Column: 90 - 108
"...cript> <a name="HautPage"></a> <..."

The “banner” role is unnecessary for element “header”.

Line: 105 Column: 3 - 36
"...iner"> <header id="header" role="banner"> <..."

Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.

Line: 122 Column: 1 - 65
"...lock --> <section id="block-menu-block-15" class="block block-menu-block"> <di..." Line: 146 Column: 1 - 54
"...obox"> <section id="block-block-1" class="block block-block"> ..." Line: 235 Column: 1 - 67
"...ider"> <section id="block-views-hug-zoom-block" class="block block-views"> ..." Line: 353 Column: 1 - 75
"...i-tabs1"> <section id="block-views-hug-actualites-block-1" class="block block-views"> ..." Line: 401 Column: 1 - 71
"...i-tabs2"> <section id="block-views-hug-agenda-block-1" class="block block-views"> ..." Line: 314 Column: 5 - 52
"... <section id="main" role="main" class="clearfix"> ..." Line: 512 Column: 1 - 70
"...cond"> <section id="block-block-13" class="block block-block social-network"> ..." Line: 713 Column: 1 - 55
"...oter"> <section id="block-block-36" class="block block-block"> ..." Line: 729 Column: 1 - 55
"...lock --> <section id="block-block-37" class="block block-block"> ..." Line: 740 Column: 1 - 55
"...lock --> <section id="block-block-38" class="block block-block"> ..." Line: 759 Column: 1 - 81
"...oter"> <section id="block-block-2" class="block block-block hug-reseaux-sociaux-footer"> ..." Line: 770 Column: 1 - 86
"...lock --> <section id="block-menu-block-14" class="block block-menu-block bloc-nos-engagements"> <di..." Line: 787 Column: 1 - 65
"...lock --> <section id="block-menu-block-16" class="block block-menu-block"> <di..." Line: 804 Column: 1 - 80
"...lock --> <section id="block-menu-block-1" class="block block-menu-block hug-menu-footer"> <di..." Line: 828 Column: 1 - 64
"...oter"> <section id="block-block-19" class="block block-block bloc-hon"> ..." Line: 839 Column: 1 - 86
"...lock --> <section id="block-menu-block-13" class="block block-menu-block bloc-nos-engagements"> <di..."

Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).

Line: 329 Column: 5 - 8
"...ent"> <h1>Bienve..."

The “complementary” role is unnecessary for element “aside”.

Line: 467 Column: 11 - 82
"... <aside id="sidebar-first" role="complementary" class="sidebar clearfix"> ..." Line: 509 Column: 11 - 83
"... <aside id="sidebar-second" role="complementary" class="sidebar clearfix"> ..."

The “contentinfo” role is unnecessary for element “footer”.

Line: 756 Column: 3 - 58
"...8</div> <footer id="footer" role="contentinfo" class="clearfix"> <..."

hug-ge.ch similar domains

Similar domains:
www.hug-ge.com
www.hug-ge.net
www.hug-ge.org
www.hug-ge.info
www.hug-ge.biz
www.hug-ge.us
www.hug-ge.mobi
www.ug-ge.ch
www.hug-ge.ch
www.bug-ge.ch
www.hbug-ge.ch
www.bhug-ge.ch
www.gug-ge.ch
www.hgug-ge.ch
www.ghug-ge.ch
www.yug-ge.ch
www.hyug-ge.ch
www.yhug-ge.ch
www.uug-ge.ch
www.huug-ge.ch
www.uhug-ge.ch
www.jug-ge.ch
www.hjug-ge.ch
www.jhug-ge.ch
www.nug-ge.ch
www.hnug-ge.ch
www.nhug-ge.ch
www.hg-ge.ch
www.hyg-ge.ch
www.huyg-ge.ch
www.hhg-ge.ch
www.huhg-ge.ch
www.hhug-ge.ch
www.hjg-ge.ch
www.hujg-ge.ch
www.hig-ge.ch
www.huig-ge.ch
www.hiug-ge.ch
www.hu-ge.ch
www.huf-ge.ch
www.hugf-ge.ch
www.hufg-ge.ch
www.huv-ge.ch
www.hugv-ge.ch
www.huvg-ge.ch
www.hut-ge.ch
www.hugt-ge.ch
www.hutg-ge.ch
www.hub-ge.ch
www.hugb-ge.ch
www.hubg-ge.ch
www.huy-ge.ch
www.hugy-ge.ch
www.huh-ge.ch
www.hugh-ge.ch
www.hugge.ch
www.hug-e.ch
www.hug-fe.ch
www.hug-gfe.ch
www.hug-fge.ch
www.hug-ve.ch
www.hug-gve.ch
www.hug-vge.ch
www.hug-te.ch
www.hug-gte.ch
www.hug-tge.ch
www.hug-be.ch
www.hug-gbe.ch
www.hug-bge.ch
www.hug-ye.ch
www.hug-gye.ch
www.hug-yge.ch
www.hug-he.ch
www.hug-ghe.ch
www.hug-hge.ch
www.hug-g.ch
www.hug-gw.ch
www.hug-gew.ch
www.hug-gwe.ch
www.hug-gs.ch
www.hug-ges.ch
www.hug-gse.ch
www.hug-gd.ch
www.hug-ged.ch
www.hug-gde.ch
www.hug-gr.ch
www.hug-ger.ch
www.hug-gre.ch

hug-ge.ch 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.


hug-ge.ch 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.