wismar.de Website Information
Daily Unique Visits: 6,814
Daily Page Views: 34,070
Income Per Day: $85
Estimated Value: $51,000
This website is located in Germany and is using following IP address 213.178.85.24. See the complete list of popular websites hosted in Germany.
wismar.de is registered under .DE top-level domain. Please check other sites in .DE zone.
Website wismar.de is using the following name servers:
- ns2.advantic.net
- ns1.advantic.net
and is probably hosted by ennit server GmbH. See the full list of other websites hosted by ennit server GmbH.
The highest website wismar.de position in Alexa rank database was 46038 and the lowest rank position was 999450. Current position of wismar.de in Alexa rank database is 199959.
Desktop speed score of wismar.de (78/100) is better than the results of 65.98% of other sites and shows that the page desktop performance can be improved.
Mobile usability score of wismar.de (98/100) is better than the results of 55.61% of other sites and means that the page is mobile-friendly.
Mobile speed score of wismar.de (63/100) is better than the results of 61.76% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
wismar.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.
wismar.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
wismar.de server information
Servers Location
wismar.de desktop page speed rank
Last tested: 2018-02-06
wismar.de Desktop Speed Test Quick Summary
priority - 14Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 132.9KiB (30% reduction).
Compressing https://www.wismar.de/media/custom/2634_1137_1_m.JPG?1500458457 could save 33KiB (54% reduction).
Compressing https://www.wismar.de/media/custom/2634_7_1_m.JPG?1513840577 could save 29.8KiB (67% reduction).
Compressing https://www.wismar.de/media/custom/2634_690_1_m.JPG?1516871259 could save 13.1KiB (37% reduction).
Compressing https://www.wismar.de/media/custom/2634_9_1_m.PNG?1481885041 could save 7KiB (32% reduction).
Compressing https://www.wismar.de/layout/wismar/media/logo_wismar.png?__ts=1447323135 could save 4.8KiB (12% reduction).
Compressing https://www.wismar.de/media/custom/2634_1386_1_m.JPG?1514983006 could save 2.5KiB (21% reduction).
Compressing https://www.wismar.de/media/custom/2634_10_1_m.PNG?1458716514 could save 1.1KiB (16% reduction).
Compressing https://www.wismar.de/layout/wismar/media/flaggen.png?__ts=1453911372 could save 1KiB (27% reduction).
Compressing https://translate.googleapis.com/translate_static/img/te_ctrl3.gif could save 591B (42% reduction).
Compressing https://www.wismar.de/layout/wismar/media/lupe.png?__ts=1442307384 could save 492B (24% reduction).
Compressing https://www.wismar.de/layout/wismar/media/menu_pfeil_down.png could save 107B (28% reduction).
priority - 10Leverage 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://www.wismar.de/layout/wismar/media/bg_hauptbild_.png (expiration not specified)
https://www.wismar.de/layout/wismar/media/menu_pfeil_down.png (expiration not specified)
https://www.wismar.de/output/js/highslide/graphics/loader.white.gif (expiration not specified)
https://www.wismar.de/output/js/highslide/graphics…ines/rounded-white.png (expiration not specified)
https://www.wismar.de/output/js/highslide/highslide-with-gallery.packed.js (expiration not specified)
https://www.wismar.de/output/js/highslide/highslide.css (expiration not specified)
https://www.wismar.de/output/js/highslide/hs_config.js (expiration not specified)
https://www.wismar.de/output/js/ikiss/basic.js (expiration not specified)
https://www.wismar.de/output/js/ikiss/datepicker.min.js (expiration not specified)
https://www.wismar.de/output/js/jquery/jquery-1.7.1.min.js (expiration not specified)
https://www.wismar.de/output/js/jquery/jquery-migrate-1.2.1.js (expiration not specified)
https://www.wismar.de/output/js/jquery/jquery-ui-datepicker.min.js (expiration not specified)
https://www.wismar.de/output/js/jquery/jquery.ajaxQueue.js (expiration not specified)
https://www.wismar.de/output/js/jquery/jquery.autocomplete.css (expiration not specified)
https://www.wismar.de/output/js/jquery/jquery.autocomplete.pack.js (expiration not specified)
https://www.wismar.de/output/js/jquery/jquery.bgiframe.min.js (expiration not specified)
https://www.wismar.de/output/js/jquery/jquery.ui.datepicker-de.js (expiration not specified)
https://translate.googleapis.com/translate_static/css/translateelement.css (60 minutes)
https://translate.googleapis.com/translate_static/js/element/main.js (60 minutes)
priority - 2Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
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 11.9KiB (38% reduction).
Minifying https://www.wismar.de/output/js/jquery/jquery.autocomplete.pack.js could save 2.3KiB (35% reduction) after compression.
Minifying https://www.wismar.de/output/js/jquery/jquery-migrate-1.2.1.js could save 2.2KiB (40% reduction) after compression.
Minifying https://www.wismar.de/layout/wismar/js/jquery.easing.1.3.js?__ts=1442307384 could save 1.1KiB (58% reduction) after compression.
Minifying https://www.wismar.de/output/js/ikiss/basic.js could save 968B (36% reduction) after compression.
Minifying https://www.wismar.de/output/js/jquery/jquery.ajaxQueue.js could save 492B (50% reduction) after compression.
Minifying https://www.wismar.de/layout/wismar/js/jquery.flexnav.js?__ts=1442307384 could save 317B (17% reduction) after compression.
Minifying https://www.wismar.de/layout/wismar/js/hoverintent.js?__ts=1446622795 could save 188B (27% reduction) after compression.
Minifying https://www.wismar.de/output/js/jquery/jquery.ui.datepicker-de.js could save 106B (22% 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 2.2KiB (16% reduction).
Minifying https://www.wismar.de/output/js/highslide/highslide.css could save 772B (22% reduction) after compression.
Minifying https://www.wismar.de/output/js/jquery/jquery.autocomplete.css could save 142B (31% reduction) after compression.
wismar.de Desktop Resource Breakdown
Total Resources | 56 |
Number of Hosts | 7 |
Static Resources | 31 |
JavaScript Resources | 22 |
CSS Resources | 6 |
wismar.de mobile page speed rank
Last tested: 2018-02-08
wismar.de Mobile Speed Test Quick Summary
priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 17 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://www.wismar.de/layout/wismar/js/jquery-1.10.2.min.js?__ts=1442307384
https://www.wismar.de/layout/wismar/js/layout.js?__ts=1481540293
https://www.wismar.de/layout/wismar/js/hoverintent.js?__ts=1446622795
https://www.wismar.de/layout/wismar/js/jquery.easing.1.3.js?__ts=1442307384
https://www.wismar.de/layout/wismar/js/jquery.flexnav.js?__ts=1442307384
https://www.wismar.de/output/js/jquery/jquery-ui-datepicker.min.js
https://www.wismar.de/output/js/jquery/jquery.ui.datepicker-de.js
https://www.wismar.de/output/js/ikiss/datepicker.min.js
https://www.wismar.de/output/js/highslide/highslide-with-gallery.packed.js
https://www.wismar.de/output/js/highslide/hs_config.js
https://www.wismar.de/output/js/ikiss/basic.js
https://www.wismar.de/output/js/jquery/jquery-migrate-1.2.1.js
https://www.wismar.de/output/js/jquery/jquery.bgiframe.min.js
https://www.wismar.de/output/js/jquery/jquery.ajaxQueue.js
https://www.wismar.de/output/js/jquery/jquery.autocomplete.pack.js
https://www.wismar.de/layout/wismar/js/jquery.flex…min.js?__ts=1442307384
Optimize CSS Delivery of the following:
https://www.wismar.de/layout/wismar/fonts/font-awe…in.css?__ts=1447313564
https://www.wismar.de/output/js/highslide/highslide.css
https://www.wismar.de/output/js/jquery/jquery.autocomplete.css
priority - 15Leverage 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://www.wismar.de/layout/wismar/media/menu.png (expiration not specified)
https://www.wismar.de/layout/wismar/media/menu_pfeil_down.png (expiration not specified)
https://www.wismar.de/output/js/highslide/graphics/loader.white.gif (expiration not specified)
https://www.wismar.de/output/js/highslide/graphics…ines/rounded-white.png (expiration not specified)
https://www.wismar.de/output/js/highslide/highslide-with-gallery.packed.js (expiration not specified)
https://www.wismar.de/output/js/highslide/highslide.css (expiration not specified)
https://www.wismar.de/output/js/highslide/hs_config.js (expiration not specified)
https://www.wismar.de/output/js/ikiss/basic.js (expiration not specified)
https://www.wismar.de/output/js/ikiss/datepicker.min.js (expiration not specified)
https://www.wismar.de/output/js/jquery/jquery-1.7.1.min.js (expiration not specified)
https://www.wismar.de/output/js/jquery/jquery-migrate-1.2.1.js (expiration not specified)
https://www.wismar.de/output/js/jquery/jquery-ui-datepicker.min.js (expiration not specified)
https://www.wismar.de/output/js/jquery/jquery.ajaxQueue.js (expiration not specified)
https://www.wismar.de/output/js/jquery/jquery.autocomplete.css (expiration not specified)
https://www.wismar.de/output/js/jquery/jquery.autocomplete.pack.js (expiration not specified)
https://www.wismar.de/output/js/jquery/jquery.bgiframe.min.js (expiration not specified)
https://www.wismar.de/output/js/jquery/jquery.ui.datepicker-de.js (expiration not specified)
https://translate.googleapis.com/translate_static/css/translateelement.css (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 117.4KiB (34% reduction).
Compressing https://www.wismar.de/media/custom/2634_7_1_m.JPG?1513840577 could save 29.8KiB (67% reduction).
Compressing https://www.wismar.de/output/img.php?id=2634.36.1&fm=g&mfm=m could save 23.7KiB (20% reduction).
Compressing https://www.wismar.de/media/custom/2634_690_1_m.JPG?1516871259 could save 13.1KiB (37% reduction).
Compressing https://www.wismar.de/media/custom/2634_9_1_m.PNG?1481885041 could save 7KiB (32% reduction).
Compressing https://www.wismar.de/layout/wismar/media/logo_wismar.png?__ts=1447323135 could save 4.8KiB (12% reduction).
Compressing https://www.wismar.de/media/custom/2634_1386_1_m.JPG?1514983006 could save 2.5KiB (21% reduction).
Compressing https://www.wismar.de/media/custom/2634_10_1_m.PNG?1458716514 could save 1.1KiB (16% reduction).
Compressing https://www.wismar.de/layout/wismar/media/flaggen.png?__ts=1453911372 could save 1KiB (27% reduction).
Compressing https://translate.googleapis.com/translate_static/img/te_ctrl3.gif could save 591B (42% reduction).
Compressing https://www.wismar.de/layout/wismar/media/lupe.png?__ts=1442307384 could save 492B (24% reduction).
Compressing https://www.wismar.de/layout/wismar/media/menu.png could save 135B (38% reduction).
Compressing https://www.wismar.de/layout/wismar/media/menu_pfeil_down.png could save 107B (28% 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 11.9KiB (38% reduction).
Minifying https://www.wismar.de/output/js/jquery/jquery.autocomplete.pack.js could save 2.3KiB (35% reduction) after compression.
Minifying https://www.wismar.de/output/js/jquery/jquery-migrate-1.2.1.js could save 2.2KiB (40% reduction) after compression.
Minifying https://www.wismar.de/layout/wismar/js/jquery.easing.1.3.js?__ts=1442307384 could save 1.1KiB (58% reduction) after compression.
Minifying https://www.wismar.de/output/js/ikiss/basic.js could save 968B (36% reduction) after compression.
Minifying https://www.wismar.de/output/js/jquery/jquery.ajaxQueue.js could save 492B (50% reduction) after compression.
Minifying https://www.wismar.de/layout/wismar/js/jquery.flexnav.js?__ts=1442307384 could save 317B (17% reduction) after compression.
Minifying https://www.wismar.de/layout/wismar/js/hoverintent.js?__ts=1446622795 could save 188B (27% reduction) after compression.
Minifying https://www.wismar.de/output/js/jquery/jquery.ui.datepicker-de.js could save 106B (22% 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 2.3KiB (16% reduction).
Minifying https://www.wismar.de/output/js/highslide/highslide.css could save 772B (22% reduction) after compression.
Minifying https://www.wismar.de/output/js/jquery/jquery.autocomplete.css could save 142B (31% reduction) after compression.
wismar.de Mobile Resource Breakdown
Total Resources | 56 |
Number of Hosts | 7 |
Static Resources | 31 |
JavaScript Resources | 22 |
CSS Resources | 6 |
wismar.de mobile page usability
Last tested: 2018-02-08
wismar.de Mobile Usability Test Quick Summary
priority - 2Size 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.
<a href="#anker_sprachen" class="language_oben">Language</a>
is close to 2 other tap targets.<a href="/Quicknavigati…echt-Satzungen" class="nlk_off npt_first">Ortsrecht & Satzungen</a>
and 1 others are close to other tap targets.<a href="/Startseite/in…=2634.219&La=1">Welterbe Hanse…ge Geschichte!</a>
and 1 others are close to other tap targets.<input type="image" name="suchanfrage" class="lupe">
is close to 2 other tap targets.<span class="touch-button"></span>
is close to 1 other tap targets.<a href="#icon-1"></a>
is close to 1 other tap targets.<a href="#icon-1"></a>
is close to 1 other tap targets.The tap target
<a href="mailto:bsc@wismar.de">bsc@wismar.de</a>
and 1 others are close to other tap targets.wismar.de HTML validation
Errors
Internal encoding declaration “iso-8859-1” disagrees with the actual encoding of the document (“utf-8”).
"...itle> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <me..."
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”.
"...itle> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <me..."
Element “script” must not have attribute “charset” unless attribute “src” is also specified.
"...cript> <script type="text/javascript" charset="utf-8"> $(d..."
Malformed byte sequence: “d6”.
"......"
Malformed byte sequence: “fc”.
"......" Line: 171 Column: - 187
"......" Line: 173 Column: - 429
"......" Line: 208 Column: - 72
"......" Line: 208 Column: - 126
"......" Line: 223 Column: - 129
"......" Line: 226 Column: - 131
"......" Line: 227 Column: - 134
"......" Line: 244 Column: - 155
"......" Line: 244 Column: - 160
"......" Line: 245 Column: - 136
"......" Line: 356 Column: - 265
"......" Line: 390 Column: - 20
"......" Line: 404 Column: - 39
"......" Line: 404 Column: - 73
"......" Line: 414 Column: - 57
"......" Line: 414 Column: - 83
"......" Line: 448 Column: - 10
"......" Line: 450 Column: - 83
"......" Line: 487 Column: - 170
"......" Line: 510 Column: - 46
"......"
Malformed byte sequence: “e4”.
"......" Line: 171 Column: - 211
"......" Line: 356 Column: - 278
"......" Line: 390 Column: - 15
"......" Line: 390 Column: - 41
"......" Line: 402 Column: - 78
"......" Line: 402 Column: - 117
"......" Line: 403 Column: - 35
"......"
The “label” element may contain at most one “button”, “input”, “meter”, “output”, “progress”, “select”, or “textarea” descendant.
"... <input type="image" name="suchanfrage" src="/layout/wismar/media/lupe.png?__ts=1442307384" 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.
"... <input type="image" name="suchanfrage" src="/layout/wismar/media/lupe.png?__ts=1442307384" title="Los" alt="Los" class="lupe" /> ..."
Bad value “navigation” for attribute “role” on element “ul”.
"...> <ul id="rid_0" class="nlv_1" role='navigation'> <li..." Line: 224 Column: 3 - 54
"...ger</a> <ul id="rid_2634_3" class="nlv_2" role='navigation'> <l..." Line: 242 Column: 3 - 54
"...tik</a> <ul id="rid_2634_4" class="nlv_2" role='navigation'> <l..." Line: 254 Column: 3 - 54
"...rbe</a> <ul id="rid_2634_5" class="nlv_2" role='navigation'> <l..."
Malformed byte sequence: “a9”.
"......" Line: 388 Column: - 143
"......" Line: 395 Column: - 70
"......" Line: 395 Column: - 107
"......"
Malformed byte sequence: “a0”.
"......" Line: 395 Column: - 108
"......" Line: 448 Column: - 104
"......"
Malformed byte sequence: “f6”.
"......" Line: 397 Column: - 40
"......"
Malformed byte sequence: “dc”.
"......" Line: 402 Column: - 90
"......" Line: 403 Column: - 8
"......"
Element “h2” not allowed as child of element “span” in this context. (Suppressing further errors from this subtree.)
"....de"/> <h2>Intern..." Line: 396 Column: 4 - 7
"...bay"/> <h2>Urkund..." Line: 403 Column: 4 - 7
"...�ne"/> <h2>�bersi..."
Warnings
The “name” attribute is obsolete. Consider putting an “id” attribute on the nearest container instead.
"...pper"> <a name="seitenanfang"></a> ..." Line: 103 Column: 5 - 36
"...iel"> <a name="anker_hilfsnavigation"></a><s..." Line: 140 Column: 7 - 53
"...u"> <a name="anker_quickmenu" id="anker_quickmenu"></a><d..." Line: 190 Column: 8 - 62
"..."> <a name="anker_volltextsuche" id="anker_volltextsuche"></a><d..." Line: 218 Column: 6 - 52
"...div> <a name="anker_hauptmenu" id="anker_hauptmenu"></a><d..." Line: 281 Column: 10 - 62
"... <a name="anker_seiteninhalt" id="anker_seiteninhalt"></a><d..." Line: 285 Column: 4 - 18
"...ix"> <a name="nr_1"></a> ..." Line: 296 Column: 4 - 18
"...ix"> <a name="nr_2"></a> ..." Line: 317 Column: 6 - 20
"... <a name="nr_1"></a> ..." Line: 334 Column: 6 - 20
"... <a name="nr_2"></a> ..." Line: 351 Column: 6 - 20
"... <a name="nr_3"></a> ..." Line: 368 Column: 6 - 20
"... <a name="nr_4"></a> ..." Line: 474 Column: 15 - 59
"... <a name="anker_sprachen" id="anker_sprachen"></a> ..."
“label” element with multiple labelable descendants.
"...> <label for="such"> ..."
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).
"...tuelles"> <h1>Aktuel..." Line: 313 Column: 1 - 4
"...ltungen"> <h1>Verans..." Line: 382 Column: 1 - 4
"...rojekte"> <h1>Projek..."
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
"...> <section class="inhalt_ganzseitig"> ..."
The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.
"...tern_img"><img src="https://www.wismar.de/media/custom/2634_10_1_m.PNG?1458716514" alt="Bürgerservice" class="css_linkimg mt_none" border="0" width="203" height="197" /></a></..."
wismar.de similar domains
www.wismar.net
www.wismar.org
www.wismar.info
www.wismar.biz
www.wismar.us
www.wismar.mobi
www.ismar.de
www.wismar.de
www.qismar.de
www.wqismar.de
www.qwismar.de
www.aismar.de
www.waismar.de
www.awismar.de
www.sismar.de
www.wsismar.de
www.swismar.de
www.eismar.de
www.weismar.de
www.ewismar.de
www.wsmar.de
www.wusmar.de
www.wiusmar.de
www.wuismar.de
www.wjsmar.de
www.wijsmar.de
www.wjismar.de
www.wksmar.de
www.wiksmar.de
www.wkismar.de
www.wosmar.de
www.wiosmar.de
www.woismar.de
www.wimar.de
www.wiwmar.de
www.wiswmar.de
www.wiwsmar.de
www.wiemar.de
www.wisemar.de
www.wiesmar.de
www.widmar.de
www.wisdmar.de
www.widsmar.de
www.wizmar.de
www.wiszmar.de
www.wizsmar.de
www.wixmar.de
www.wisxmar.de
www.wixsmar.de
www.wiamar.de
www.wisamar.de
www.wiasmar.de
www.wisar.de
www.wisnar.de
www.wismnar.de
www.wisnmar.de
www.wisjar.de
www.wismjar.de
www.wisjmar.de
www.wiskar.de
www.wismkar.de
www.wiskmar.de
www.wismr.de
www.wismqr.de
www.wismaqr.de
www.wismqar.de
www.wismwr.de
www.wismawr.de
www.wismwar.de
www.wismsr.de
www.wismasr.de
www.wismsar.de
www.wismzr.de
www.wismazr.de
www.wismzar.de
www.wisma.de
www.wismae.de
www.wismare.de
www.wismaer.de
www.wismad.de
www.wismard.de
www.wismadr.de
www.wismaf.de
www.wismarf.de
www.wismafr.de
www.wismat.de
www.wismart.de
www.wismatr.de
wismar.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.
wismar.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.