LIMBURG.DE Stadt Limburg an der Lahn / Startseite

limburg.de Website Information

Daily Unique Visits: 4,003

Daily Page Views: 16,012

Income Per Day: $45

Estimated Value: $24,300

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

limburg.de is registered under .DE top-level domain. Please check other sites in .DE zone.

Website limburg.de is using the following name servers:

  • dns2.teliko.net
  • dns1.teliko.net

and is probably hosted by ennit server GmbH. See the full list of other websites hosted by ennit server GmbH.

The highest website limburg.de position in Alexa rank database was 20049 and the lowest rank position was 998510. Current position of limburg.de in Alexa rank database is 313530.

Desktop speed score of limburg.de (70/100) is better than the results of 50.91% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of limburg.de (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 limburg.de (59/100) is better than the results of 52.41% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

limburg.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.


limburg.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.


Domain: limburg.de
Status: connect

limburg.de server information

Servers Location

limburg.de desktop page speed rank

Last tested: 2015-09-09


Desktop Speed Medium
70/100

limburg.de Desktop Speed Test Quick Summary


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

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

Remove render-blocking JavaScript:

http://limburg.de/layout/limburg/js/jquery.min.js?__ts=1383059207
http://limburg.de/layout/limburg/js/jquery.easing.1.3.js?__ts=1383059207
http://limburg.de/layout/limburg/js/jquery.flexnav.js?__ts=1383059206
http://limburg.de/layout/limburg/js/jquery.tooltip…min.js?__ts=1427958340
http://limburg.de/layout/limburg/js/functions.js?__ts=1427976351
http://limburg.de/output/js/jquery/jquery.bgiframe.min.js
http://code.jquery.com/ui/1.8.21/jquery-ui.min.js
http://limburg.de/output/js/jquery/jquery.ajaxQueue.js
http://limburg.de/output/js/jquery/jquery.ui.datepicker-de.js
http://limburg.de/output/js/jquery/jquery.autocomplete.pack.js
http://limburg.de/output/js/highslide/highslide-with-gallery.packed.js
http://limburg.de/output/js/highslide/hs_config.js
http://translate.google.com/translate_a/element.js…leTranslateElementInit
http://limburg.de/layout/limburg/js/jquery.flexslider-min.js

Optimize CSS Delivery of the following:

http://code.jquery.com/ui/1.8.21/themes/base/jquery-ui.css
http://limburg.de/layout/limburg/layout.css?__ts=1427960946
http://limburg.de/layout/limburg/layout_320.css?__ts=1427975509
http://limburg.de/layout/limburg/layout_700.css?__ts=1429079443
http://limburg.de/layout/limburg/layout_1024.css?__ts=1427976327
http://limburg.de/layout/limburg/tooltipster.css?__ts=1427958831
http://fonts.googleapis.com/css?family=Gentium+Bas…00italic,700,700italic
http://code.jquery.com/ui/1.8.21/themes/base/jquery-ui.css
http://limburg.de/output/js/jquery/jquery.autocomplete.css
http://limburg.de/output/js/highslide/highslide.css
https://translate.googleapis.com/translate_static/css/translateelement.css

priority - 13Leverage 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:

http://limburg.de/layout/limburg/js/jquery.flexslider-min.js (expiration not specified)
http://limburg.de/layout/limburg/media/alternativbild.jpg (expiration not specified)
http://limburg.de/layout/limburg/media/bg_banderole.png (expiration not specified)
http://limburg.de/layout/limburg/media/bg_body.jpg (expiration not specified)
http://limburg.de/layout/limburg/media/bg_navigation.png (expiration not specified)
http://limburg.de/layout/limburg/media/bg_signet.png (expiration not specified)
http://limburg.de/layout/limburg/media/h4-strich.png (expiration not specified)
http://limburg.de/layout/limburg/media/schatten-links.png (expiration not specified)
http://limburg.de/layout/limburg/media/seitenanfang.png (expiration not specified)
http://limburg.de/layout/limburg/media/sprache.gif (expiration not specified)
http://limburg.de/media/custom/2212_2919_1_m.PNG (expiration not specified)
http://limburg.de/output/js/highslide/graphics/loader.white.gif (expiration not specified)
http://limburg.de/output/js/highslide/graphics/outlines/rounded-white.png (expiration not specified)
http://limburg.de/output/js/highslide/highslide-with-gallery.packed.js (expiration not specified)
http://limburg.de/output/js/highslide/highslide.css (expiration not specified)
http://limburg.de/output/js/highslide/hs_config.js (expiration not specified)
http://limburg.de/output/js/jquery/jquery.ajaxQueue.js (expiration not specified)
http://limburg.de/output/js/jquery/jquery.autocomplete.css (expiration not specified)
http://limburg.de/output/js/jquery/jquery.autocomplete.pack.js (expiration not specified)
http://limburg.de/output/js/jquery/jquery.bgiframe.min.js (expiration not specified)
http://limburg.de/output/js/jquery/jquery.ui.datepicker-de.js (expiration not specified)
https://piwik.advantic.de/piwik.js (expiration not specified)
https://www.gstatic.com/images/branding/product/1x/translate_24dp.png (50 minutes)
https://translate.googleapis.com/translate_static/css/translateelement.css (60 minutes)
https://translate.googleapis.com/translate_static/…ent/27/element_main.js (60 minutes)
https://translate.googleapis.com/translate_static/js/element/main.js (60 minutes)

priority - 12Optimize images

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

Optimize the following images to reduce their size by 111.6KiB (24% reduction).

Losslessly compressing http://limburg.de/media/custom/2212_2368_1_m.JPG?1426764196 could save 64KiB (81% reduction).
Losslessly compressing http://limburg.de/media/custom/2212_143_1_m.JPG?1364981523 could save 20.6KiB (61% reduction).
Compressing and resizing http://limburg.de/layout/limburg/media/alternativbild.jpg could save 17.6KiB (83% reduction).
Losslessly compressing http://limburg.de/layout/limburg/media/logo_stadt-…sw.png?__ts=1383059206 could save 2.5KiB (28% reduction).
Losslessly compressing http://limburg.de/layout/limburg/media/bg_banderole.png could save 2.4KiB (27% reduction).
Losslessly compressing http://limburg.de/output/img.php?id=2212.24.1&fm=r could save 795B (1% reduction).
Losslessly compressing http://limburg.de/output/img.php?id=2212.25.1&fm=r could save 795B (2% reduction).
Losslessly compressing http://limburg.de/output/img.php?id=2212.26.1&fm=r could save 795B (2% reduction).
Losslessly compressing http://limburg.de/output/img.php?id=2212.27.1&fm=r could save 795B (2% reduction).
Losslessly compressing http://limburg.de/media/custom/2212_2598_1_m.JPG?1431952804 could save 760B (11% reduction).
Losslessly compressing http://limburg.de/media/custom/2212_6_1_m.PNG?1383071385 could save 675B (3% reduction).

priority - 0Minify 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 2.8KiB (26% reduction).

Minifying http://code.jquery.com/ui/1.8.21/themes/base/jquery-ui.css could save 1.4KiB (26% reduction) after compression.
Minifying http://limburg.de/output/js/highslide/highslide.css could save 772B (22% reduction) after compression.
Minifying http://limburg.de/layout/limburg/tooltipster.css?__ts=1427958831 could save 597B (36% reduction) after compression.

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

Minifying http://limburg.de/layout/limburg/js/jquery.easing.1.3.js?__ts=1383059207 could save 1.1KiB (58% reduction) after compression.
Minifying https://translate.googleapis.com/translate_static/…ent/27/element_main.js could save 664B (1% reduction) after compression.

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 849B (8% reduction).

Minifying http://limburg.de/ could save 849B (8% reduction) after compression.

limburg.de Desktop Resource Breakdown

Total Resources65
Number of Hosts9
Static Resources35
JavaScript Resources18
CSS Resources11

limburg.de mobile page speed rank

Last tested: 2019-06-22


Mobile Speed Bad
59/100

limburg.de Mobile Speed Test Quick Summary


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

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

Remove render-blocking JavaScript:

https://www.limburg.de/layout/limburg/js/jquery.min.js?__ts=1383059207
https://www.limburg.de/layout/limburg/js/jquery.ea…1.3.js?__ts=1383059207
https://www.limburg.de/layout/limburg/js/jquery.flexnav.js?__ts=1383059206
https://www.limburg.de/layout/limburg/js/jquery.to…min.js?__ts=1427958340
https://www.limburg.de/layout/limburg/js/functions.js?__ts=1427976351
https://www.limburg.de/output/js/ikiss/basic.js
https://www.limburg.de/output/js/jquery/jquery.bgiframe.min.js
https://www.limburg.de/layout/limburg/js/jquery-ui….21.js?__ts=1529336803
https://www.limburg.de/output/js/jquery/jquery.ajaxQueue.js
https://www.limburg.de/output/js/jquery/jquery.ui.datepicker-de.js
https://www.limburg.de/output/js/jquery/jquery.autocomplete.pack.js
https://www.limburg.de/output/js/highslide/highslide-with-gallery.packed.js
https://www.limburg.de/output/js/highslide/hs_config.js
https://www.limburg.de/output/js/jplayer/jquery.jplayer.min.js
https://www.limburg.de/output/js/flowplayer/flowplayer.min.js

Optimize CSS Delivery of the following:

https://www.limburg.de/layout/limburg/jquery-ui.css?__ts=1529337001
https://www.limburg.de/layout/limburg/layout.css?__ts=1529335895
https://www.limburg.de/layout/limburg/layout_320.css?__ts=1427975509
https://www.limburg.de/layout/limburg/fonts/cabin.css?__ts=1529336356
https://www.limburg.de/layout/limburg/fonts/gentium.css?__ts=1529336356
https://www.limburg.de/output/js/jquery/jquery.autocomplete.css
https://www.limburg.de/output/js/highslide/highslide.css
https://www.limburg.de/output/js/jplayer/css/jplayer.blue.monday.min.css
https://www.limburg.de/output/js/flowplayer/skin/minimalist.css

priority - 22Leverage 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://piwik.advantic.de/piwik.js (expiration not specified)
https://www.limburg.de/layout/limburg/js/jquery.flexslider-min.js (expiration not specified)
https://www.limburg.de/layout/limburg/media/bg_body.jpg (expiration not specified)
https://www.limburg.de/layout/limburg/media/bg_navigation.png (expiration not specified)
https://www.limburg.de/layout/limburg/media/bg_signet.png (expiration not specified)
https://www.limburg.de/layout/limburg/media/h4-strich.png (expiration not specified)
https://www.limburg.de/layout/limburg/media/menu.png (expiration not specified)
https://www.limburg.de/layout/limburg/media/sprache.gif (expiration not specified)
https://www.limburg.de/layout/limburg/media/trenner.png (expiration not specified)
https://www.limburg.de/media/custom/2212_6632_1_t.JPG (expiration not specified)
https://www.limburg.de/media/custom/2212_6634_1_t.JPG (expiration not specified)
https://www.limburg.de/media/custom/2212_6_1_m.PNG (expiration not specified)
https://www.limburg.de/media/custom/2212_7369_1_g.JPG (expiration not specified)
https://www.limburg.de/media/custom/2212_7_1_m.PNG (expiration not specified)
https://www.limburg.de/output/js/flowplayer/flowplayer.min.js (expiration not specified)
https://www.limburg.de/output/js/flowplayer/skin/minimalist.css (expiration not specified)
https://www.limburg.de/output/js/highslide/graphics/loader.white.gif (expiration not specified)
https://www.limburg.de/output/js/highslide/graphic…ines/rounded-white.png (expiration not specified)
https://www.limburg.de/output/js/highslide/highslide-with-gallery.packed.js (expiration not specified)
https://www.limburg.de/output/js/highslide/highslide.css (expiration not specified)
https://www.limburg.de/output/js/highslide/hs_config.js (expiration not specified)
https://www.limburg.de/output/js/ikiss/basic.js (expiration not specified)
https://www.limburg.de/output/js/jplayer/css/jplayer.blue.monday.min.css (expiration not specified)
https://www.limburg.de/output/js/jplayer/jquery.jplayer.min.js (expiration not specified)
https://www.limburg.de/output/js/jquery/jquery.ajaxQueue.js (expiration not specified)
https://www.limburg.de/output/js/jquery/jquery.autocomplete.css (expiration not specified)
https://www.limburg.de/output/js/jquery/jquery.autocomplete.pack.js (expiration not specified)
https://www.limburg.de/output/js/jquery/jquery.bgiframe.min.js (expiration not specified)
https://www.limburg.de/output/js/jquery/jquery.ui.datepicker-de.js (expiration not specified)

priority - 13Optimize images

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

Optimize the following images to reduce their size by 124.1KiB (53% reduction).

Compressing https://www.limburg.de/media/custom/2212_1754_1_g.JPG?1406790151 could save 35.9KiB (68% reduction).
Compressing https://www.limburg.de/media/custom/2212_6166_1_m.JPG?1533116406 could save 29KiB (87% reduction).
Compressing https://www.limburg.de/media/custom/2212_7212_1_m.JPG?1554725490 could save 27.9KiB (85% reduction).
Compressing https://www.limburg.de/media/custom/2212_4089_1_m.JPG?1470382037 could save 8.9KiB (62% reduction).
Compressing https://www.limburg.de/media/custom/2212_7370_1_m.JPG?1561108174 could save 6.3KiB (24% reduction).
Compressing https://www.limburg.de/media/custom/2212_7371_1_m.JPG?1561111015 could save 5.3KiB (20% reduction).
Compressing https://www.limburg.de/media/custom/2212_7360_1_m.JPG?1560937342 could save 3.8KiB (20% reduction).
Compressing https://www.limburg.de/media/custom/2212_4567_1_m.JPG?1484231216 could save 3.2KiB (58% reduction).
Compressing https://www.limburg.de/media/custom/2212_6632_1_t.JPG could save 2.7KiB (17% reduction).
Compressing https://www.limburg.de/layout/limburg/media/bg_body.jpg could save 921B (18% reduction).
Compressing https://www.limburg.de/layout/limburg/media/lupe.png?__ts=1383059205 could save 195B (15% reduction).

priority - 0Minify 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 4.2KiB (44% reduction).

Minifying https://www.limburg.de/output/js/ikiss/basic.js could save 1.9KiB (45% reduction) after compression.
Minifying https://www.limburg.de/layout/limburg/js/jquery.ea…1.3.js?__ts=1383059207 could save 1.1KiB (58% reduction) after compression.
Minifying https://www.limburg.de/output/js/jquery/jquery.ajaxQueue.js could save 506B (51% reduction) after compression.
Minifying https://www.limburg.de/layout/limburg/js/jquery.flexnav.js?__ts=1383059206 could save 323B (41% reduction) after compression.
Minifying https://www.limburg.de/layout/limburg/js/functions.js?__ts=1427976351 could save 206B (30% reduction) after compression.
Minifying https://www.limburg.de/output/js/jquery/jquery.ui.datepicker-de.js could save 106B (22% reduction) after compression.
Minifying https://www.limburg.de/output/js/jquery/jquery.bgiframe.min.js could save 101B (16% reduction) after compression.

priority - 0Minify 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 4.1KiB (23% reduction).

Minifying https://www.limburg.de/layout/limburg/jquery-ui.css?__ts=1529337001 could save 1.5KiB (26% reduction) after compression.
Minifying https://www.limburg.de/layout/limburg/layout.css?__ts=1529335895 could save 932B (16% reduction) after compression.
Minifying https://www.limburg.de/output/js/highslide/highslide.css could save 772B (22% reduction) after compression.
Minifying https://www.limburg.de/layout/limburg/tooltipster.css?__ts=1427958831 could save 597B (36% reduction) after compression.
Minifying https://www.limburg.de/output/js/jquery/jquery.autocomplete.css could save 164B (34% reduction) after compression.
Minifying https://www.limburg.de/layout/limburg/fonts/gentium.css?__ts=1529336356 could save 117B (26% reduction) after compression.
Minifying https://www.limburg.de/layout/limburg/fonts/cabin.css?__ts=1529336356 could save 112B (26% reduction) after compression.

limburg.de Mobile Resource Breakdown

Total Resources67
Number of Hosts3
Static Resources31
JavaScript Resources17
CSS Resources13

limburg.de mobile page usability

Last tested: 2019-06-22


Mobile Usability Good
99/100

limburg.de 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="/Quicknavigati…erkl%C3%A4rung" class="csslink_intern">Mehr dazu in u…hutzerklärung.</a> is close to 1 other tap targets.

The tap target <a href="/Quicknavigation/Sitemap" class="nlk_off npt_last">Sitemap</a> is close to 2 other tap targets.

The tap target <input type="image" name="suchanfrage" class="lupe"> is close to 1 other tap targets.

The tap target <a href="/Quicknavigati…t=&amp;kuo=2&amp;sub=0" class="csslink_intern_img"></a> is close to 1 other tap targets.

limburg.de HTML validation

Errors

Internal encoding declaration “iso-8859-1” disagrees with the actual encoding of the document (“utf-8”).

Line: 5 Column: 7 - 80
"...le> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <m..."

Bad value “text/html; charset=iso-8859-1” for attribute “content” on element “meta”: “iso-8859-1” is not a preferred encoding name. The preferred label for this encoding is “windows-1252”.

Line: 5 Column: 7 - 80
"...le> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <m..."

Malformed byte sequence: “fc”.

Line: 148 Column: - 162
"......" Line: 170 Column: - 38
"......" Line: 278 Column: - 169
"......" Line: 292 Column: - 116
"......" Line: 375 Column: - 159
"......" Line: 382 Column: - 143
"......" Line: 386 Column: - 176
"......" Line: 386 Column: - 184
"......" Line: 390 Column: - 168
"......" Line: 390 Column: - 173
"......" Line: 426 Column: - 136
"......" Line: 459 Column: - 132
"......" Line: 460 Column: - 119
"......" Line: 477 Column: - 188
"......" Line: 530 Column: - 167
"......" Line: 534 Column: - 131
"......" Line: 590 Column: - 191
"......" Line: 590 Column: - 225
"......" Line: 678 Column: - 211
"......" Line: 678 Column: - 313
"......" Line: 678 Column: - 359
"......" Line: 684 Column: - 214
"......" Line: 686 Column: - 210
"......" Line: 714 Column: - 32
"......" Line: 714 Column: - 96
"......" Line: 749 Column: - 26
"......"

Malformed byte sequence: “e4”.

Line: 230 Column: - 107
"......" Line: 287 Column: - 150
"......" Line: 307 Column: - 138
"......" Line: 312 Column: - 126
"......" Line: 315 Column: - 164
"......" Line: 329 Column: - 176
"......" Line: 339 Column: - 141
"......" Line: 348 Column: - 135
"......" Line: 357 Column: - 188
"......" Line: 401 Column: - 136
"......" Line: 424 Column: - 172
"......" Line: 426 Column: - 142
"......" Line: 427 Column: - 136
"......" Line: 429 Column: - 156
"......" Line: 508 Column: - 170
"......" Line: 523 Column: - 195
"......" Line: 526 Column: - 173
"......" Line: 527 Column: - 157
"......" Line: 530 Column: - 175
"......" Line: 564 Column: - 139
"......" Line: 565 Column: - 290
"......" Line: 590 Column: - 202
"......" Line: 590 Column: - 236
"......" Line: 714 Column: - 112
"......" Line: 714 Column: - 125
"......"

The “label” element may contain at most one “button”, “input”, “meter”, “output”, “progress”, “select”, or “textarea” descendant.

Line: 249 Column: 19 - 147
"... <input type="image" name="suchanfrage" src="/layout/limburg/media/lupe.png?__ts=1383059205" title="Los" alt="Los" class="lupe" /> ..." Line: 584 Column: 22 - 150
"... <input type="image" name="suchanfrage" src="/layout/limburg/media/lupe.png?__ts=1383059205" title="Los" alt="Los" class="lupe" /> ..."

Any “input” descendant of a “label” element with a “for” attribute must have an ID value that matches that “for” attribute.

Line: 249 Column: 19 - 147
"... <input type="image" name="suchanfrage" src="/layout/limburg/media/lupe.png?__ts=1383059205" title="Los" alt="Los" class="lupe" /> ..." Line: 584 Column: 22 - 150
"... <input type="image" name="suchanfrage" src="/layout/limburg/media/lupe.png?__ts=1383059205" title="Los" alt="Los" class="lupe" /> ..."

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

Line: 250 Column: 19 - 34
"... <div class="cb"></div>..." Line: 585 Column: 22 - 37
"... <div class="cb"></div>..."

Malformed byte sequence: “d6”.

Line: 264 Column: - 150
"......" Line: 528 Column: - 200
"......"

Malformed byte sequence: “c4”.

Line: 266 Column: - 129
"......" Line: 378 Column: - 134
"......"

Bad value “navigation” for attribute “role” on element “ul”.

Line: 259 Column: 2 - 48
"... <ul id="rid_0" class="nlv_1" role='navigation'> <li..."

Malformed byte sequence: “f6”.

Line: 313 Column: - 135
"......" Line: 414 Column: - 155
"......" Line: 491 Column: - 134
"......" Line: 505 Column: - 184
"......" Line: 521 Column: - 139
"......" Line: 714 Column: - 12
"......" Line: 749 Column: - 17
"......"

Malformed byte sequence: “dc”.

Line: 462 Column: - 112
"......"

Malformed byte sequence: “df”.

Line: 480 Column: - 148
"......" Line: 501 Column: - 186
"......" Line: 523 Column: - 154
"......" Line: 523 Column: - 185
"......" Line: 562 Column: - 145
"......"

Duplicate ID “anker_volltextsuche”.

Line: 577 Column: 16 - 70
"... <a name="anker_volltextsuche" id="anker_volltextsuche"></a> ..."

Duplicate ID “such”.

Line: 583 Column: 22 - 263
"... <input type="text" name="qs" id="such" class="suchfeld" onblur="(this.value == '') &amp;&amp; (this.value = 'Webseite durchsuchen')" onfocus="(this.value == 'Webseite durchsuchen') &amp;&amp; (this.value = '')" value="Webseite durchsuchen" /> ..."

Element “script” must not have attribute “charset” unless attribute “src” is also specified.

Line: 788 Column: 4 - 50
".../div> <script type="text/javascript" charset="utf-8"> ..."

Warnings

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

Line: 96 Column: 4 - 30
"...<body> <a name="start" id="start"></a> ..." Line: 98 Column: 11 - 42
"... <h2><a name="anker_hilfsnavigation"></a>Hi..." Line: 225 Column: 10 - 56
"... <a name="anker_quickmenu" id="anker_quickmenu"></a> ..." Line: 242 Column: 13 - 67
"... <a name="anker_volltextsuche" id="anker_volltextsuche"></a> ..." Line: 257 Column: 16 - 62
"... <a name="anker_hauptmenu" id="anker_hauptmenu"></a> ..." Line: 577 Column: 16 - 70
"... <a name="anker_volltextsuche" id="anker_volltextsuche"></a> ..." Line: 639 Column: 10 - 62
"... <a name="anker_seiteninhalt" id="anker_seiteninhalt"></a> ..." Line: 676 Column: 1 - 21
"...g"></div> <a name="a1" id="a1"></a><h..." Line: 721 Column: 7 - 27
"...iv> </div><a name="a2" id="a2"></a><h..." Line: 729 Column: 6 - 20
"...t"> <a name="nr_1"></a> ..." Line: 746 Column: 6 - 20
"...t"> <a name="nr_2"></a> ..." Line: 762 Column: 6 - 20
"...t"> <a name="nr_3"></a> ..." Line: 771 Column: 7 - 27
".../p> </div><a name="a3" id="a3"></a><a..." Line: 771 Column: 32 - 52
"...="a3"></a><a name="a4" id="a4"></a><a..." Line: 771 Column: 57 - 77
"...="a4"></a><a name="a5" id="a5"></a><a..." Line: 771 Column: 82 - 102
"...="a5"></a><a name="a6" id="a6"></a><a..." Line: 771 Column: 107 - 127
"...="a6"></a><a name="a7" id="a7"></a><a..." Line: 771 Column: 132 - 152
"...="a7"></a><a name="a8" id="a8"></a><a..." Line: 771 Column: 157 - 177
"...="a8"></a><a name="a9" id="a9"></a><a..." Line: 771 Column: 182 - 204
"...="a9"></a><a name="a10" id="a10"></a><a..." Line: 771 Column: 209 - 231
"..."a10"></a><a name="a11" id="a11"></a><a..." Line: 771 Column: 236 - 258
"..."a11"></a><a name="a12" id="a12"></a><a..." Line: 771 Column: 263 - 285
"..."a12"></a><a name="a13" id="a13"></a><a..." Line: 771 Column: 290 - 312
"..."a13"></a><a name="a14" id="a14"></a><a..." Line: 771 Column: 317 - 339
"..."a14"></a><a name="a15" id="a15"></a><a..." Line: 771 Column: 344 - 366
"..."a15"></a><a name="a16" id="a16"></a><a..." Line: 771 Column: 371 - 393
"..."a16"></a><a name="a17" id="a17"></a><a..." Line: 771 Column: 398 - 420
"..."a17"></a><a name="a18" id="a18"></a><a..." Line: 771 Column: 425 - 447
"..."a18"></a><a name="a19" id="a19"></a><a..." Line: 771 Column: 452 - 474
"..."a19"></a><a name="a20" id="a20"></a><a..." Line: 771 Column: 479 - 501
"..."a20"></a><a name="a21" id="a21"></a> ..."

“label” element with multiple labelable descendants.

Line: 247 Column: 16 - 33
"... <label for="such"> ..." Line: 582 Column: 19 - 36
"... <label for="such"> ..."

The first occurrence of ID “anker_volltextsuche” was here.

Line: 242 Column: 13 - 67
"... <a name="anker_volltextsuche" id="anker_volltextsuche"></a> ..."

The first occurrence of ID “such” was here.

Line: 248 Column: 19 - 260
"... <input type="text" name="qs" id="such" class="suchfeld" onblur="(this.value == '') &amp;&amp; (this.value = 'Webseite durchsuchen')" onfocus="(this.value == 'Webseite durchsuchen') &amp;&amp; (this.value = '')" value="Webseite durchsuchen" /> ..."

The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.

Line: 629 Column: 135 - 289
"...tern_img"><img src="http://www.limburg.de/media/custom/2212_5611_1_m.JPG?1515740566" alt="uwz15583" class="css_linkimg mt_none" border="0" width="155" height="83" /></a></..." Line: 630 Column: 144 - 298
"...tern_img"><img src="http://www.limburg.de/media/custom/2212_4567_1_m.JPG?1484231216" alt="Interamt" class="css_linkimg mt_none" border="0" width="155" height="83" /></a></..." Line: 631 Column: 135 - 303
"...tern_img"><img src="http://www.limburg.de/media/custom/2212_6166_1_m.JPG?1533116406" alt="Neuer Verwaltungssitz?" class="css_linkimg mt_none" border="0" width="155" height="83" /></a></..." Line: 632 Column: 138 - 309
"...tern_img"><img src="http://www.limburg.de/media/custom/2212_4089_1_m.JPG?1470382037" alt="Masterplan Mobilit&auml;t" class="css_linkimg mt_none" border="0" width="155" height="83" /></a></..." Line: 642 Column: 187 - 349
"...tern_img"><img src="http://www.limburg.de/media/custom/2212_4442_1_k.JPG?1480580025" alt="Kostenloses WLAN" border="0" class="css_linkimg mt_none" width="150" height="83" /></a></..." Line: 651 Column: 114 - 276
"...tern_img"><img src="http://www.limburg.de/media/custom/2212_2294_1_k.JPG?1424681696" alt="Fairtrade-Stadt" border="0" class="css_linkimg mt_none" width="150" height="105" /></a></..." Line: 652 Column: 102 - 264
"...tern_img"><img src="http://www.limburg.de/media/custom/2212_2729_1_k.JPG?1435752040" alt="Stellenangebote" border="0" class="css_linkimg mt_none" width="113" height="113" /></a></..." Line: 671 Column: 111 - 304
"...tern_img"><img src="http://www.limburg.de/media/custom/2212_1754_1_g.JPG?1406790151" alt="Externer Link: http://www.telekom.de/schneller" border="0" class="css_linkimg mt_none" width="150" height="450" /></a></..."

limburg.de similar domains

Similar domains:
www.limburg.com
www.limburg.net
www.limburg.org
www.limburg.info
www.limburg.biz
www.limburg.us
www.limburg.mobi
www.imburg.de
www.limburg.de
www.pimburg.de
www.lpimburg.de
www.plimburg.de
www.oimburg.de
www.loimburg.de
www.olimburg.de
www.kimburg.de
www.lkimburg.de
www.klimburg.de
www.lmburg.de
www.lumburg.de
www.liumburg.de
www.luimburg.de
www.ljmburg.de
www.lijmburg.de
www.ljimburg.de
www.lkmburg.de
www.likmburg.de
www.lomburg.de
www.liomburg.de
www.liburg.de
www.linburg.de
www.limnburg.de
www.linmburg.de
www.lijburg.de
www.limjburg.de
www.likburg.de
www.limkburg.de
www.limurg.de
www.limvurg.de
www.limbvurg.de
www.limvburg.de
www.limgurg.de
www.limbgurg.de
www.limgburg.de
www.limhurg.de
www.limbhurg.de
www.limhburg.de
www.limnurg.de
www.limbnurg.de
www.limbrg.de
www.limbyrg.de
www.limbuyrg.de
www.limbyurg.de
www.limbhrg.de
www.limbuhrg.de
www.limbjrg.de
www.limbujrg.de
www.limbjurg.de
www.limbirg.de
www.limbuirg.de
www.limbiurg.de
www.limbug.de
www.limbueg.de
www.limbureg.de
www.limbuerg.de
www.limbudg.de
www.limburdg.de
www.limbudrg.de
www.limbufg.de
www.limburfg.de
www.limbufrg.de
www.limbutg.de
www.limburtg.de
www.limbutrg.de
www.limbur.de
www.limburf.de
www.limburgf.de
www.limburv.de
www.limburgv.de
www.limburvg.de
www.limburt.de
www.limburgt.de
www.limburb.de
www.limburgb.de
www.limburbg.de
www.limbury.de
www.limburgy.de
www.limburyg.de
www.limburh.de
www.limburgh.de
www.limburhg.de

limburg.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.


limburg.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.