GRUENE.BERLIN Bündnis 90 / DIE GRÜNEN Berlin

gruene.berlin Website Information

Daily Unique Visits: 1,087

Daily Page Views: 2,174

Income Per Day: $7

Estimated Value: $1,680

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

gruene.berlin is registered under .BERLIN top-level domain. Please check other sites in .BERLIN zone.

Website gruene.berlin is using the following name servers:

  • ns-de.1and1-dns.de
  • ns-de.1and1-dns.org
  • ns-de.1and1-dns.biz
  • ns-de.1and1-dns.com

and is probably hosted by Hetzner Online GmbH. See the full list of other websites hosted by Hetzner Online GmbH.

The highest website gruene.berlin position in Alexa rank database was 32652 and the lowest rank position was 997367. Current position of gruene.berlin in Alexa rank database is 659480.

Desktop speed score of gruene.berlin (51/100) is better than the results of 24.87% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of gruene.berlin (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.

Mobile speed score of gruene.berlin (48/100) is better than the results of 30.32% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

gruene.berlin 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.


gruene.berlin 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.


Domain Name: gruene.berlin
Registry Domain ID: D0000039419-BERLIN
Registrar WHOIS Server: whois.ionos.com
Registrar URL: https://ionos.com
Updated Date: 2021-06-17T10:00:36Z
Creation Date: 2014-03-18T10:03:26Z
Registry Expiry Date: 2023-03-18T10:03:26Z
Registrar: 1&1 Internet SE
Registrar IANA ID: 83
Registrar Abuse Contact Email: abuse@ionos.com
Registrar Abuse Contact Phone: +1.6105601459
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: helium.ns.hetzner.de
Name Server: hydrogen.ns.hetzner.com
Name Server: oxygen.ns.hetzner.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of Whois database: 2022-10-23T15:02:30Z

gruene.berlin server information

Servers Location

gruene.berlin desktop page speed rank

Last tested: 2019-02-15


Desktop Speed Bad
51/100

gruene.berlin Desktop Speed Test Quick Summary


priority - 95Optimize images

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

Optimize the following images to reduce their size by 925.8KiB (65% reduction).

Compressing https://gruene.berlin/sites/gruene.berlin/themes/gb2016/css/images/alex.jpg could save 645.1KiB (85% reduction).
Compressing and resizing https://gruene.berlin/sites/gruene.berlin/files/st…olge.jpg?itok=fcagFo0I could save 105.6KiB (76% reduction).
Compressing and resizing https://gruene.berlin/sites/gruene.berlin/files/st…zeit.jpg?itok=5x2YJeR5 could save 79.3KiB (70% reduction).
Compressing https://gruene.berlin/sites/gruene.berlin/files/st…4933.jpg?itok=7vwdrX_X could save 51.7KiB (23% reduction).
Compressing https://gruene.berlin/sites/gruene.berlin/files/st…logo.jpg?itok=zhnMcesx could save 23.4KiB (24% reduction).
Compressing https://gruene.berlin/sites/gruene.berlin/files/st…dien.png?itok=F3RoAn-j could save 11.8KiB (30% reduction).
Compressing https://gruene.berlin/sites/gruene.berlin/files/st…934b.jpg?itok=3oJqMw6v could save 3.3KiB (28% reduction).
Compressing https://gruene.berlin/sites/gruene.berlin/files/st…er_o.jpg?itok=0rEhy0vv could save 2.8KiB (26% reduction).
Compressing https://gruene.berlin/sites/gruene.berlin/files/st…ag16.jpg?itok=eCLXYFNA could save 2.3KiB (22% reduction).
Compressing https://gruene.berlin/files/logo_1.png could save 470B (21% reduction).

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

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

Remove render-blocking JavaScript:

https://gruene.berlin/sites/gruene.berlin/files/js…yXuKekr2jbdDptsM5Oc.js
https://gruene.berlin/sites/gruene.berlin/files/js…Ae-kyRpZMAJ_Ikxi88Y.js
https://gruene.berlin/sites/gruene.berlin/files/js…4psmY52iKslnBp_kK6I.js
https://gruene.berlin/sites/gruene.berlin/files/js…ynhNj9r1NzjIlRLoNpA.js
https://gruene.berlin/sites/gruene.berlin/files/js…SE2F1SGF2ngr3uFPjpU.js

Optimize CSS Delivery of the following:

https://gruene.berlin/modules/system/system.base.css?pj04tb
https://gruene.berlin/modules/system/system.menus.css?pj04tb
https://gruene.berlin/modules/system/system.messages.css?pj04tb
https://gruene.berlin/modules/system/system.theme.css?pj04tb
https://gruene.berlin/sites/all/modules/simplenews/simplenews.css?pj04tb
https://gruene.berlin/modules/comment/comment.css?pj04tb
https://gruene.berlin/sites/all/modules/date/date_api/date.css?pj04tb
https://gruene.berlin/sites/all/modules/date/date_…epicker.1.7.css?pj04tb
https://gruene.berlin/modules/field/theme/field.css?pj04tb
https://gruene.berlin/modules/node/node.css?pj04tb
https://gruene.berlin/sites/all/modules/panopoly_m…opoly-magic.css?pj04tb
https://gruene.berlin/sites/all/modules/panopoly_m…opoly-modal.css?pj04tb
https://gruene.berlin/modules/user/user.css?pj04tb
https://gruene.berlin/sites/all/modules/webform_co…nfirm_email.css?pj04tb
https://gruene.berlin/sites/all/modules/calendar/c…ar_multiday.css?pj04tb
https://gruene.berlin/sites/all/modules/views/css/views.css?pj04tb
https://gruene.berlin/sites/all/modules/ckeditor/css/ckeditor.css?pj04tb
https://gruene.berlin/sites/all/modules/entity_emb…ntity_embed.css?pj04tb
https://gruene.berlin/sites/all/modules/ctools/css/ctools.css?pj04tb
https://gruene.berlin/sites/all/modules/panels/css/panels.css?pj04tb
https://gruene.berlin/sites/all/libraries/shariff/…ff.complete.css?pj04tb
https://gruene.berlin/sites/all/modules/eu_cookie_…_compliance.css?pj04tb
https://gruene.berlin/sites/all/modules/quicktabs/css/quicktabs.css?pj04tb
https://gruene.berlin/sites/all/libraries/superfis…s/superfish.css?pj04tb
https://gruene.berlin/sites/all/libraries/superfis…smallscreen.css?pj04tb
https://gruene.berlin/sites/all/libraries/superfish/style/spring.css?pj04tb
https://gruene.berlin/sites/all/themes/adaptivethe…s/at.layout.css?pj04tb
https://gruene.berlin/sites/gruene.berlin/themes/g…global.base.css?pj04tb
https://gruene.berlin/sites/gruene.berlin/themes/g…obal.styles.css?pj04tb
https://gruene.berlin/sites/gruene.berlin/files/ad…sive.layout.css?pj04tb
https://gruene.berlin/sites/gruene.berlin/themes/g…sive.custom.css?pj04tb
https://gruene.berlin/sites/gruene.berlin/themes/g…ive.desktop.css?pj04tb

priority - 2Minify 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 18.4KiB (25% reduction).

Minifying https://gruene.berlin/sites/gruene.berlin/files/js…ynhNj9r1NzjIlRLoNpA.js could save 5.8KiB (35% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/files/js…Ae-kyRpZMAJ_Ikxi88Y.js could save 5.6KiB (46% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/files/js…yXuKekr2jbdDptsM5Oc.js could save 5.2KiB (13% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/files/js…4psmY52iKslnBp_kK6I.js could save 1.3KiB (49% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/files/js…SE2F1SGF2ngr3uFPjpU.js could save 426B (21% reduction) after compression.

priority - 1Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 13.8KiB (37% reduction).

Minifying https://gruene.berlin/sites/gruene.berlin/themes/g…obal.styles.css?pj04tb could save 5.2KiB (34% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/themes/g…global.base.css?pj04tb could save 2.7KiB (62% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/themes/g…sive.custom.css?pj04tb could save 894B (73% reduction) after compression.
Minifying https://gruene.berlin/modules/system/system.base.css?pj04tb could save 825B (44% reduction) after compression.
Minifying https://gruene.berlin/sites/all/modules/calendar/c…ar_multiday.css?pj04tb could save 752B (22% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/themes/g…ch.portrait.css?pj04tb could save 408B (73% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/themes/g…h.landscape.css?pj04tb could save 405B (72% reduction) after compression.
Minifying https://gruene.berlin/sites/all/modules/panopoly_m…opoly-modal.css?pj04tb could save 375B (13% reduction) after compression.
Minifying https://gruene.berlin/sites/all/modules/date/date_api/date.css?pj04tb could save 341B (29% reduction) after compression.
Minifying https://gruene.berlin/sites/all/modules/panopoly_m…opoly-magic.css?pj04tb could save 299B (27% reduction) after compression.
Minifying https://gruene.berlin/modules/system/system.theme.css?pj04tb could save 290B (24% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/themes/g…t.landscape.css?pj04tb could save 260B (86% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/themes/g…et.portrait.css?pj04tb could save 260B (86% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/themes/g…ive.desktop.css?pj04tb could save 226B (91% reduction) after compression.
Minifying https://gruene.berlin/modules/user/user.css?pj04tb could save 162B (24% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/files/ad…sive.layout.css?pj04tb could save 156B (14% reduction) after compression.
Minifying https://gruene.berlin/sites/all/themes/adaptivethe…s/at.layout.css?pj04tb could save 141B (40% reduction) after compression.
Minifying https://gruene.berlin/modules/system/system.menus.css?pj04tb could save 140B (22% reduction) after compression.
Minifying https://gruene.berlin/sites/all/modules/date/date_…epicker.1.7.css?pj04tb could save 108B (12% reduction) after compression.
Minifying https://gruene.berlin/sites/all/modules/entity_emb…ntity_embed.css?pj04tb could save 105B (50% reduction) after compression.

gruene.berlin Desktop Resource Breakdown

Total Resources66
Number of Hosts2
Static Resources62
JavaScript Resources7
CSS Resources36

gruene.berlin mobile page speed rank

Last tested: 2019-02-15


Mobile Speed Bad
48/100

gruene.berlin Mobile Speed Test Quick Summary


priority - 82Optimize images

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

Optimize the following images to reduce their size by 797.3KiB (56% reduction).

Compressing https://gruene.berlin/sites/gruene.berlin/themes/gb2016/css/images/alex.jpg could save 645.1KiB (85% reduction).
Compressing https://gruene.berlin/sites/gruene.berlin/files/st…4933.jpg?itok=7vwdrX_X could save 51.7KiB (23% reduction).
Compressing https://gruene.berlin/sites/gruene.berlin/files/st…zeit.jpg?itok=5x2YJeR5 could save 28.5KiB (26% reduction).
Compressing https://gruene.berlin/sites/gruene.berlin/files/st…olge.jpg?itok=fcagFo0I could save 27.9KiB (21% reduction).
Compressing https://gruene.berlin/sites/gruene.berlin/files/st…logo.jpg?itok=zhnMcesx could save 23.4KiB (24% reduction).
Compressing https://gruene.berlin/sites/gruene.berlin/files/st…dien.png?itok=F3RoAn-j could save 11.8KiB (30% reduction).
Compressing https://gruene.berlin/sites/gruene.berlin/files/st…934b.jpg?itok=3oJqMw6v could save 3.3KiB (28% reduction).
Compressing https://gruene.berlin/sites/gruene.berlin/files/st…er_o.jpg?itok=0rEhy0vv could save 2.8KiB (26% reduction).
Compressing https://gruene.berlin/sites/gruene.berlin/files/st…ag16.jpg?itok=eCLXYFNA could save 2.3KiB (22% reduction).
Compressing https://gruene.berlin/files/logo_1.png could save 470B (21% reduction).

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

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

Remove render-blocking JavaScript:

https://gruene.berlin/sites/gruene.berlin/files/js…yXuKekr2jbdDptsM5Oc.js
https://gruene.berlin/sites/gruene.berlin/files/js…Ae-kyRpZMAJ_Ikxi88Y.js
https://gruene.berlin/sites/gruene.berlin/files/js…4psmY52iKslnBp_kK6I.js
https://gruene.berlin/sites/gruene.berlin/files/js…ynhNj9r1NzjIlRLoNpA.js
https://gruene.berlin/sites/gruene.berlin/files/js…SE2F1SGF2ngr3uFPjpU.js

Optimize CSS Delivery of the following:

https://gruene.berlin/modules/system/system.base.css?pj04tb
https://gruene.berlin/modules/system/system.menus.css?pj04tb
https://gruene.berlin/modules/system/system.messages.css?pj04tb
https://gruene.berlin/modules/system/system.theme.css?pj04tb
https://gruene.berlin/sites/all/modules/simplenews/simplenews.css?pj04tb
https://gruene.berlin/modules/comment/comment.css?pj04tb
https://gruene.berlin/sites/all/modules/date/date_api/date.css?pj04tb
https://gruene.berlin/sites/all/modules/date/date_…epicker.1.7.css?pj04tb
https://gruene.berlin/modules/field/theme/field.css?pj04tb
https://gruene.berlin/modules/node/node.css?pj04tb
https://gruene.berlin/sites/all/modules/panopoly_m…opoly-magic.css?pj04tb
https://gruene.berlin/sites/all/modules/panopoly_m…opoly-modal.css?pj04tb
https://gruene.berlin/modules/user/user.css?pj04tb
https://gruene.berlin/sites/all/modules/webform_co…nfirm_email.css?pj04tb
https://gruene.berlin/sites/all/modules/calendar/c…ar_multiday.css?pj04tb
https://gruene.berlin/sites/all/modules/views/css/views.css?pj04tb
https://gruene.berlin/sites/all/modules/ckeditor/css/ckeditor.css?pj04tb
https://gruene.berlin/sites/all/modules/entity_emb…ntity_embed.css?pj04tb
https://gruene.berlin/sites/all/modules/ctools/css/ctools.css?pj04tb
https://gruene.berlin/sites/all/modules/panels/css/panels.css?pj04tb
https://gruene.berlin/sites/all/libraries/shariff/…ff.complete.css?pj04tb
https://gruene.berlin/sites/all/modules/eu_cookie_…_compliance.css?pj04tb
https://gruene.berlin/sites/all/modules/quicktabs/css/quicktabs.css?pj04tb
https://gruene.berlin/sites/all/libraries/superfis…s/superfish.css?pj04tb
https://gruene.berlin/sites/all/libraries/superfis…smallscreen.css?pj04tb
https://gruene.berlin/sites/all/libraries/superfish/style/spring.css?pj04tb
https://gruene.berlin/sites/all/themes/adaptivethe…s/at.layout.css?pj04tb
https://gruene.berlin/sites/gruene.berlin/themes/g…global.base.css?pj04tb
https://gruene.berlin/sites/gruene.berlin/themes/g…obal.styles.css?pj04tb
https://gruene.berlin/sites/gruene.berlin/files/ad…sive.layout.css?pj04tb
https://gruene.berlin/sites/gruene.berlin/themes/g…sive.custom.css?pj04tb
https://gruene.berlin/sites/gruene.berlin/themes/g…h.landscape.css?pj04tb

priority - 2Minify 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 18.4KiB (25% reduction).

Minifying https://gruene.berlin/sites/gruene.berlin/files/js…ynhNj9r1NzjIlRLoNpA.js could save 5.8KiB (35% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/files/js…Ae-kyRpZMAJ_Ikxi88Y.js could save 5.6KiB (46% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/files/js…yXuKekr2jbdDptsM5Oc.js could save 5.2KiB (13% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/files/js…4psmY52iKslnBp_kK6I.js could save 1.3KiB (49% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/files/js…SE2F1SGF2ngr3uFPjpU.js could save 426B (21% reduction) after compression.

priority - 1Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 13.8KiB (37% reduction).

Minifying https://gruene.berlin/sites/gruene.berlin/themes/g…obal.styles.css?pj04tb could save 5.2KiB (34% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/themes/g…global.base.css?pj04tb could save 2.7KiB (62% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/themes/g…sive.custom.css?pj04tb could save 894B (73% reduction) after compression.
Minifying https://gruene.berlin/modules/system/system.base.css?pj04tb could save 825B (44% reduction) after compression.
Minifying https://gruene.berlin/sites/all/modules/calendar/c…ar_multiday.css?pj04tb could save 752B (22% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/themes/g…ch.portrait.css?pj04tb could save 408B (73% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/themes/g…h.landscape.css?pj04tb could save 405B (72% reduction) after compression.
Minifying https://gruene.berlin/sites/all/modules/panopoly_m…opoly-modal.css?pj04tb could save 375B (13% reduction) after compression.
Minifying https://gruene.berlin/sites/all/modules/date/date_api/date.css?pj04tb could save 341B (29% reduction) after compression.
Minifying https://gruene.berlin/sites/all/modules/panopoly_m…opoly-magic.css?pj04tb could save 299B (27% reduction) after compression.
Minifying https://gruene.berlin/modules/system/system.theme.css?pj04tb could save 290B (24% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/themes/g…t.landscape.css?pj04tb could save 260B (86% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/themes/g…et.portrait.css?pj04tb could save 260B (86% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/themes/g…ive.desktop.css?pj04tb could save 226B (91% reduction) after compression.
Minifying https://gruene.berlin/modules/user/user.css?pj04tb could save 162B (24% reduction) after compression.
Minifying https://gruene.berlin/sites/gruene.berlin/files/ad…sive.layout.css?pj04tb could save 156B (14% reduction) after compression.
Minifying https://gruene.berlin/sites/all/themes/adaptivethe…s/at.layout.css?pj04tb could save 141B (40% reduction) after compression.
Minifying https://gruene.berlin/modules/system/system.menus.css?pj04tb could save 140B (22% reduction) after compression.
Minifying https://gruene.berlin/sites/all/modules/date/date_…epicker.1.7.css?pj04tb could save 108B (12% reduction) after compression.
Minifying https://gruene.berlin/sites/all/modules/entity_emb…ntity_embed.css?pj04tb could save 105B (50% reduction) after compression.

gruene.berlin Mobile Resource Breakdown

Total Resources66
Number of Hosts2
Static Resources62
JavaScript Resources7
CSS Resources36

gruene.berlin mobile page usability

Last tested: 2019-02-15


Mobile Usability Good
99/100

gruene.berlin Mobile Usability Test Quick Summary


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 <a href="/datenschutzerklärung">Datenschutzerklärung</a> and 4 others are close to other tap targets.
The tap target <button type="button" class="agree-button">Ich stimme zu</button> and 1 others are close to other tap targets.

gruene.berlin HTML validation

Errors

Stray start tag “html”.

Line: 6 Column: 23 - 48
"...E 8]><!--><html lang="de" dir="ltr"><!--<!..."

Bad value “” for attribute “name” on element “input”: Must not be empty.

Line: 89 Column: 7 - 97
"...n"> <input type="submit" id="edit-submit-suche" name="" value="Anwenden" class="form-submit" /> </..."

An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.

Line: 502 Column: 200 - 374
"...tem even"><img class="image-style-3col" src="https://gruene.berlin/sites/gruene.berlin/files/styles/3col/public/2015_banner_soziale-medien.png?itok=F3RoAn-j" width="233" height="222" /></figu..."

Attribute “rel” not allowed on element “div” at this point.

Line: 543 Column: 1 - 60
"..._blank"> <div id="872010" rel="text" class="cr_ipe_item ui-sortable"> <labe..." Line: 547 Column: 1 - 60
"...> </div> <div id="872011" rel="text" class="cr_ipe_item ui-sortable"> <labe..." Line: 551 Column: 1 - 70
"...> </div> <div id="872007" rel="email" class="cr_ipe_item ui-sortable musthave"> <labe..." Line: 555 Column: 1 - 82
"...> </div> <div id="872012" rel="checkbox" class="cr_ipe_item checkbox ui-sortable musthave"> <labe..." Line: 559 Column: 1 - 79
"...> </div> <div id="872013" rel="button" class="cr_ipe_item ui-sortable submit_container"> <butt..."

Duplicate ID “872012”.

Line: 556 Column: 25 - 78
"...itemname"><input id="872012" name="[]" value="" type="checkbox"> Ich a..."

The “itemprop” attribute was specified, but the element is not a property of any item.

Line: 28 Column: 1 - 63
"...seite" /> <meta itemprop="name" content="Bündnis 90/DIE GRÜNEN Berlin" /> <meta..."

Warnings

Document uses the Unicode Private Use Area(s), which should not be used in publicly exchanged documents. (Charmod C073)

Line: 71 Column: - 114
"...licken">&#xf002;</span></div> ..."

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

Line: 94 Column: 5 - 55
".../div> <header id="header" class="clearfix" role="banner"> ..."

The “main” role is unnecessary for element “main”.

Line: 154 Column: 7 - 67
"...x"> <main id="content-column" class="content-column" role="main"> ..."

The “article” role is unnecessary for element “article”.

Line: 174 Column: 3 - 82
"... > <article id="node-14244" class="node node-page article clearfix" role="article"> ..." Line: 418 Column: 7 - 114
"...t"> <article id="node-81439" class="node node-banner node-promoted node-teaser article clearfix" role="article"> ..." Line: 441 Column: 7 - 114
"...t"> <article id="node-11412" class="node node-banner node-promoted node-teaser article clearfix" role="article"> ..." Line: 469 Column: 7 - 100
"...t"> <article id="node-13045" class="node node-banner node-teaser article clearfix" role="article"> ..." Line: 492 Column: 7 - 100
"...t"> <article id="node-12487" class="node node-banner node-teaser article clearfix" role="article"> ..."

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

Line: 174 Column: 3 - 82
"... > <article id="node-14244" class="node node-page article clearfix" role="article"> ..." Line: 418 Column: 7 - 114
"...t"> <article id="node-81439" class="node node-banner node-promoted node-teaser article clearfix" role="article"> ..." Line: 469 Column: 7 - 100
"...t"> <article id="node-13045" class="node node-banner node-teaser article clearfix" role="article"> ..."

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

Line: 524 Column: 11 - 66
"... <footer id="footer" class="clearfix" role="contentinfo"> ..."

The first occurrence of ID “872012” was here.

Line: 555 Column: 1 - 82
"...> </div> <div id="872012" rel="checkbox" class="cr_ipe_item checkbox ui-sortable musthave"> <labe..."

This document appears to be written in German. Consider adding “lang="de"” (or variant) to the “html” start tag.

Line: 2 Column: 16 - 6
"...TYPE html> <html> <!--[..."

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: 444 Column: 15 - 37
"... <h1 class="node-title"> ..." Line: 495 Column: 15 - 37
"... <h1 class="node-title"> ..." Line: 164 Column: 51 - 70
"... <h1 id="page-title"> ..."

gruene.berlin similar domains

Similar domains:
www.gruene.com
www.gruene.net
www.gruene.org
www.gruene.info
www.gruene.biz
www.gruene.us
www.gruene.mobi
www.ruene.berlin
www.gruene.berlin
www.fruene.berlin
www.gfruene.berlin
www.fgruene.berlin
www.vruene.berlin
www.gvruene.berlin
www.vgruene.berlin
www.truene.berlin
www.gtruene.berlin
www.tgruene.berlin
www.bruene.berlin
www.gbruene.berlin
www.bgruene.berlin
www.yruene.berlin
www.gyruene.berlin
www.ygruene.berlin
www.hruene.berlin
www.ghruene.berlin
www.hgruene.berlin
www.guene.berlin
www.geuene.berlin
www.greuene.berlin
www.geruene.berlin
www.gduene.berlin
www.grduene.berlin
www.gdruene.berlin
www.gfuene.berlin
www.grfuene.berlin
www.gtuene.berlin
www.grtuene.berlin
www.grene.berlin
www.gryene.berlin
www.gruyene.berlin
www.gryuene.berlin
www.grhene.berlin
www.gruhene.berlin
www.grhuene.berlin
www.grjene.berlin
www.grujene.berlin
www.grjuene.berlin
www.griene.berlin
www.gruiene.berlin
www.griuene.berlin
www.grune.berlin
www.gruwne.berlin
www.gruewne.berlin
www.gruwene.berlin
www.grusne.berlin
www.gruesne.berlin
www.grusene.berlin
www.grudne.berlin
www.gruedne.berlin
www.grudene.berlin
www.grurne.berlin
www.gruerne.berlin
www.grurene.berlin
www.gruee.berlin
www.gruebe.berlin
www.gruenbe.berlin
www.gruebne.berlin
www.gruehe.berlin
www.gruenhe.berlin
www.gruehne.berlin
www.grueje.berlin
www.gruenje.berlin
www.gruejne.berlin
www.grueme.berlin
www.gruenme.berlin
www.gruemne.berlin
www.gruen.berlin
www.gruenw.berlin
www.gruenew.berlin
www.gruenwe.berlin
www.gruens.berlin
www.gruenes.berlin
www.gruense.berlin
www.gruend.berlin
www.gruened.berlin
www.gruende.berlin
www.gruenr.berlin
www.gruener.berlin
www.gruenre.berlin

gruene.berlin 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.


gruene.berlin 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.