wom.de Website Information
Daily Unique Visits: 1,163
Daily Page Views: 2,326
Income Per Day: $7
Estimated Value: $1,680
wom.de is registered under .DE top-level domain. Please check other sites in .DE zone.
No name server records were found.
and is probably hosted by PlusServer GmbH. See the full list of other websites hosted by PlusServer GmbH.
The highest website wom.de position in Alexa rank database was 12630 and the lowest rank position was 994314. Current position of wom.de in Alexa rank database is 616563.
Desktop speed score of wom.de (83/100) is better than the results of 76.15% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of wom.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 wom.de (62/100) is better than the results of 59.44% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
wom.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.
wom.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
wom.de server information
Servers Location
wom.de desktop page speed rank
Last tested: 2018-01-25
wom.de Desktop Speed Test Quick Summary
priority - 10Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 7 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://wom.de/js/jquery/jquery.min.js?d=ID1689
https://wom.de/js/vendor.min.js?d=ID1689
https://wom.de/js/common.min.js?d=ID1689
https://wom.de/js/modules.min.js?d=ID1689
https://wom.de/js/pages.min.js?d=ID1689
https://wom.de/js/main.min.js?d=ID1689
Optimize CSS Delivery of the following:
priority - 3Leverage 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.google-analytics.com/analytics.js (2 hours)
https://wom.de/cmsimage/id/1243025 (24 hours)
https://wom.de/cmsimage/id/1243630 (24 hours)
https://wom.de/cmsimage/id/1244718 (24 hours)
https://wom.de/cmsimage/id/1244719 (24 hours)
https://wom.de/cmsimage/id/1244796 (24 hours)
https://wom.de/cmsimage/id/1244799 (24 hours)
priority - 2Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 22.6KiB (21% reduction).
Compressing https://wom.de/cmsimage/id/1243025 could save 3.4KiB (25% reduction).
Compressing https://wom.de/cmsimage/id/1244799 could save 3.3KiB (21% reduction).
Compressing https://wom.de/cmsimage/id/1244719 could save 2.3KiB (20% reduction).
Compressing https://wom.de/cmsimage/id/1244718 could save 2KiB (16% reduction).
Compressing https://media1.jpc.de/image/h90/front/0/0889854364823.jpg could save 515B (17% reduction).
Compressing https://media1.jpc.de/image/h90/front/0/0075597937336.jpg could save 439B (20% reduction).
Compressing https://media1.jpc.de/image/h90/front/0/4015698013979.jpg could save 431B (37% reduction).
Compressing https://media3.jpc.de/image/h90/front/0/8714092755626.jpg could save 430B (17% reduction).
Compressing https://media2.jpc.de/image/h90/front/0/4015698013986.jpg could save 423B (35% reduction).
Compressing https://media2.jpc.de/image/h90/front/0/0819873016243.jpg could save 405B (12% reduction).
Compressing https://media1.jpc.de/image/h90/front/0/0602567131120.jpg could save 401B (20% reduction).
Compressing https://media3.jpc.de/image/h90/front/0/0819873016373.jpg could save 399B (12% reduction).
Compressing https://media1.jpc.de/image/h90/front/0/0888072024649.jpg could save 393B (21% reduction).
Compressing https://media3.jpc.de/image/h90/front/0/4015698938913.jpg could save 392B (22% reduction).
Compressing https://media2.jpc.de/image/h90/front/0/0819873010791.jpg could save 388B (15% reduction).
Compressing https://media1.jpc.de/image/h90/front/0/0000007830296.jpg could save 385B (17% reduction).
Compressing https://media3.jpc.de/image/h90/front/0/5053792500635.jpg could save 382B (18% reduction).
Compressing https://media1.jpc.de/image/h90/front/0/0190295722968.jpg could save 380B (28% reduction).
Compressing https://media2.jpc.de/image/h90/front/0/0889853112913.jpg could save 379B (18% reduction).
Compressing https://media2.jpc.de/image/h90/front/0/5414940006650.jpg could save 379B (21% reduction).
Compressing https://media1.jpc.de/image/h90/front/0/0889854013325.jpg could save 377B (16% reduction).
Compressing https://media1.jpc.de/image/h90/front/0/0819873010111.jpg could save 375B (18% reduction).
Compressing https://media3.jpc.de/image/h90/front/0/4050538232851.jpg could save 361B (18% reduction).
priority - 2Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
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 1.4KiB (15% reduction).
priority - 0Enable 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 1.2KiB (53% reduction).
wom.de Desktop Resource Breakdown
Total Resources | 55 |
Number of Hosts | 9 |
Static Resources | 44 |
JavaScript Resources | 9 |
CSS Resources | 1 |
wom.de mobile page speed rank
Last tested: 2017-05-21
wom.de Mobile Speed Test Quick Summary
priority - 48Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 3 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://ajax.googleapis.com/ajax/libs/jquery/1.11.2/jquery.min.js
https://wom.de/js/main.min.js?d=ID1333
Optimize CSS Delivery of the following:
priority - 8Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 5Leverage 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.google-analytics.com/analytics.js (2 hours)
https://wom.de/cmsimage/id/1242883 (24 hours)
https://wom.de/cmsimage/id/1242884 (24 hours)
https://wom.de/cmsimage/id/1242885 (24 hours)
https://wom.de/cmsimage/id/1243025 (24 hours)
https://wom.de/cmsimage/id/1243245 (24 hours)
https://wom.de/cmsimage/id/1243247 (24 hours)
priority - 3Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 20.5KiB (25% reduction).
Compressing https://wom.de/cmsimage/id/1243025 could save 3.4KiB (25% reduction).
Compressing https://wom.de/cmsimage/id/1243247 could save 3.3KiB (23% reduction).
Compressing https://wom.de/cmsimage/id/1242885 could save 3.2KiB (23% reduction).
Compressing https://wom.de/cmsimage/id/1242884 could save 2.8KiB (20% reduction).
Compressing https://wom.de/cmsimage/id/1242883 could save 2.5KiB (24% reduction).
Compressing https://media3.jpc.de/image/h145/front/0/0889854364915.jpg could save 680B (11% reduction).
Compressing https://media1.jpc.de/image/h145/front/0/0190295924911.jpg could save 532B (16% reduction).
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 1.4KiB (15% reduction).
priority - 0Enable 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 1.2KiB (53% reduction).
wom.de Mobile Resource Breakdown
Total Resources | 54 |
Number of Hosts | 10 |
Static Resources | 41 |
JavaScript Resources | 5 |
CSS Resources | 1 |
wom.de mobile page usability
Last tested: 2017-05-21
wom.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.
<a href="/poprock/chart…2?chartsmode=1">Pop/Rock Top 100</a>
is close to 1 other tap targets.The tap target
<a href="https://wom.de…ad-datenschutz">Datenschutzerklärung</a>
and 1 others are close to other tap targets.wom.de HTML validation
Errors
Attribute “xmlns:fb” not allowed here.
"...E 9]><!--> <html class="no-js" lang="de" xmlns:fb="https://www.facebook.com/2008/fbml" > <!--<..."
A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.
"...head> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> <..."
Bad value “screen, projection, print” for attribute “media” on element “link”: Deprecated media type “projection”. For guidance, see the Media Types section in the current Media Queries specification.
"... <link href="/css/9f8630/wom.css" media="screen, projection, print" rel="stylesheet" type="text/css"> ..."
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
"...ager --> <img src="/images/common/loading.svg" style="display:none" /> ..."
Attribute “autocorrect” not allowed on element “input” at this point.
"...rm"> <input type="search" name="fastsearch" class="field" value="" placeholder="  Suchbegriff eingeben" required autocomplete="off" autocorrect="off" /> ..."
“=” in an unquoted attribute value. Probable causes: Attributes running together or a URL query string in an unquoted attribute value.
"...-url= data-hnum="8620204" id="..." Line: 503 Column: - 102
"...-url= data-hnum="7672302" id="..." Line: 555 Column: - 102
"...-url= data-hnum="5941256" id="..." Line: 607 Column: - 102
"...-url= data-hnum="1561269" id="..." Line: 662 Column: - 102
"...-url= data-hnum="9360687" id="..." Line: 713 Column: - 102
"...-url= data-hnum="7552851" id="..." Line: 770 Column: - 102
"...-url= data-hnum="8532579" id="..." Line: 821 Column: - 102
"...-url= data-hnum="7918831" id="..." Line: 876 Column: - 102
"...-url= data-hnum="7971593" id="..." Line: 931 Column: - 102
"...-url= data-hnum="6833874" id="..." Line: 1116 Column: - 101
"...-url= data-hnum="8700046" id="..." Line: 1168 Column: - 101
"...-url= data-hnum="3826027" id="..." Line: 1224 Column: - 101
"...-url= data-hnum="8702807" id="..." Line: 1276 Column: - 101
"...-url= data-hnum="8275400" id="..." Line: 1328 Column: - 101
"...-url= data-hnum="8702804" id="..." Line: 1380 Column: - 101
"...-url= data-hnum="8275463" id="..." Line: 1434 Column: - 101
"...-url= data-hnum="8345280" id="..." Line: 1486 Column: - 101
"...-url= data-hnum="8704731" id="..." Line: 1538 Column: - 101
"...-url= data-hnum="8702514" id="..." Line: 1590 Column: - 101
"...-url= data-hnum="8237452" id="..."
“"” in an unquoted attribute value. Probable causes: Attributes running together or a URL query string in an unquoted attribute value.
"...url= data-hnum="8620204" id="p..." Line: 452 Column: - 111
"...a-hnum="8620204" id="product-8..." Line: 503 Column: - 103
"...url= data-hnum="7672302" id="p..." Line: 503 Column: - 111
"...a-hnum="7672302" id="product-7..." Line: 555 Column: - 103
"...url= data-hnum="5941256" id="p..." Line: 555 Column: - 111
"...a-hnum="5941256" id="product-5..." Line: 607 Column: - 103
"...url= data-hnum="1561269" id="p..." Line: 607 Column: - 111
"...a-hnum="1561269" id="product-1..." Line: 662 Column: - 103
"...url= data-hnum="9360687" id="p..." Line: 662 Column: - 111
"...a-hnum="9360687" id="product-9..." Line: 713 Column: - 103
"...url= data-hnum="7552851" id="p..." Line: 713 Column: - 111
"...a-hnum="7552851" id="product-7..." Line: 770 Column: - 103
"...url= data-hnum="8532579" id="p..." Line: 770 Column: - 111
"...a-hnum="8532579" id="product-8..." Line: 821 Column: - 103
"...url= data-hnum="7918831" id="p..." Line: 821 Column: - 111
"...a-hnum="7918831" id="product-7..." Line: 876 Column: - 103
"...url= data-hnum="7971593" id="p..." Line: 876 Column: - 111
"...a-hnum="7971593" id="product-7..." Line: 931 Column: - 103
"...url= data-hnum="6833874" id="p..." Line: 931 Column: - 111
"...a-hnum="6833874" id="product-6..." Line: 1116 Column: - 102
"...url= data-hnum="8700046" id="p..." Line: 1116 Column: - 110
"...a-hnum="8700046" id="product-8..." Line: 1168 Column: - 102
"...url= data-hnum="3826027" id="p..." Line: 1168 Column: - 110
"...a-hnum="3826027" id="product-3..." Line: 1224 Column: - 102
"...url= data-hnum="8702807" id="p..." Line: 1224 Column: - 110
"...a-hnum="8702807" id="product-8..." Line: 1276 Column: - 102
"...url= data-hnum="8275400" id="p..." Line: 1276 Column: - 110
"...a-hnum="8275400" id="product-8..." Line: 1328 Column: - 102
"...url= data-hnum="8702804" id="p..." Line: 1328 Column: - 110
"...a-hnum="8702804" id="product-8..." Line: 1380 Column: - 102
"...url= data-hnum="8275463" id="p..." Line: 1380 Column: - 110
"...a-hnum="8275463" id="product-8..." Line: 1434 Column: - 102
"...url= data-hnum="8345280" id="p..." Line: 1434 Column: - 110
"...a-hnum="8345280" id="product-8..." Line: 1486 Column: - 102
"...url= data-hnum="8704731" id="p..." Line: 1486 Column: - 110
"...a-hnum="8704731" id="product-8..." Line: 1538 Column: - 102
"...url= data-hnum="8702514" id="p..." Line: 1538 Column: - 110
"...a-hnum="8702514" id="product-8..." Line: 1590 Column: - 102
"...url= data-hnum="8237452" id="p..." Line: 1590 Column: - 110
"...a-hnum="8237452" id="product-8..."
Element “div” not allowed as child of element “a” in this context. (Suppressing further errors from this subtree.)
"... <div class="by">David ..." Line: 469 Column: 14 - 32
"... <div class="title">Christ..." Line: 519 Column: 10 - 25
"... <div class="by">Guano ..." Line: 520 Column: 14 - 32
"... <div class="title">Proud ..." Line: 571 Column: 10 - 25
"... <div class="by">Falco<..." Line: 572 Column: 14 - 32
"... <div class="title">Falco ..." Line: 626 Column: 10 - 25
"... <div class="by">Steve ..." Line: 627 Column: 14 - 32
"... <div class="title">Please..." Line: 678 Column: 10 - 25
"... <div class="by">Thin L..." Line: 679 Column: 14 - 32
"... <div class="title">Vagabo..." Line: 732 Column: 10 - 25
"... <div class="by">David ..." Line: 733 Column: 14 - 32
"... <div class="title">Live A..." Line: 786 Column: 10 - 25
"... <div class="by">Paul B..." Line: 787 Column: 14 - 32
"... <div class="title">Live I..." Line: 840 Column: 10 - 25
"... <div class="by">Chris ..." Line: 841 Column: 14 - 32
"... <div class="title">The Re..." Line: 895 Column: 10 - 25
"... <div class="by">Steve ..." Line: 896 Column: 14 - 32
"... <div class="title">Wuther..." Line: 950 Column: 10 - 25
"... <div class="by">Leo Sa..." Line: 951 Column: 14 - 32
"... <div class="title">More T..."
Element “div” not allowed as child of element “h3” in this context. (Suppressing further errors from this subtree.)
"... <div class="by">Rivers..." Line: 1135 Column: 14 - 32
"... <div class="title">Wastel..." Line: 1189 Column: 10 - 25
"... <div class="by">Eloy</..." Line: 1190 Column: 14 - 32
"... <div class="title">Eloy (..." Line: 1242 Column: 10 - 25
"... <div class="by">Philli..." Line: 1243 Column: 14 - 32
"... <div class="title">Earthl..." Line: 1294 Column: 14 - 32
"... <div class="title">Bravo ..." Line: 1346 Column: 10 - 25
"... <div class="by">Philli..." Line: 1347 Column: 14 - 32
"... <div class="title">Earthl..." Line: 1398 Column: 10 - 25
"... <div class="by">The Ro..." Line: 1399 Column: 14 - 32
"... <div class="title">From T..." Line: 1452 Column: 10 - 25
"... <div class="by">The Be..." Line: 1453 Column: 14 - 32
"... <div class="title">Yellow..." Line: 1504 Column: 10 - 25
"... <div class="by">Philli..." Line: 1505 Column: 14 - 32
"... <div class="title">Earthl..." Line: 1556 Column: 10 - 25
"... <div class="by">Pink F..." Line: 1557 Column: 14 - 32
"... <div class="title">A Foot..." Line: 1608 Column: 10 - 25
"... <div class="by">Floren..." Line: 1609 Column: 14 - 32
"... <div class="title">High A..."
Warnings
Attribute with the local name “xmlns:fb” is not serializable as XML 1.0.
"...E 9]><!--> <html class="no-js" lang="de" xmlns:fb="https://www.facebook.com/2008/fbml" > <!--<..."
Document uses the Unicode Private Use Area(s), which should not be used in publicly exchanged documents. (Charmod C073)
"...older="  Suchbegriff e..."
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
".../header> <section class="my-account"> <..." Line: 249 Column: 5 - 30
"... <section class="heroshot"> ..." Line: 1007 Column: 9 - 29
"... <section class="ads"> ..." Line: 1663 Column: 9 - 29
"... <section class="ads"> ..." Line: 2116 Column: 1 - 27
".../footer> <section class="copyright"> <..."
Article lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all articles.
"... <article> ..." Line: 1008 Column: 25 - 46
"... <article class="nr-0"> <..." Line: 1021 Column: 25 - 46
"... <article class="nr-1"> <..." Line: 1034 Column: 25 - 46
"... <article class="nr-2"> <..." Line: 1664 Column: 25 - 46
"... <article class="nr-0"> <..." Line: 1677 Column: 25 - 46
"... <article class="nr-1"> <..." Line: 1690 Column: 25 - 46
"... <article class="nr-2"> <..."
wom.de similar domains
www.wom.net
www.wom.org
www.wom.info
www.wom.biz
www.wom.us
www.wom.mobi
www.om.de
www.wom.de
www.qom.de
www.wqom.de
www.qwom.de
www.aom.de
www.waom.de
www.awom.de
www.som.de
www.wsom.de
www.swom.de
www.eom.de
www.weom.de
www.ewom.de
www.wm.de
www.wim.de
www.woim.de
www.wiom.de
www.wkm.de
www.wokm.de
www.wkom.de
www.wlm.de
www.wolm.de
www.wlom.de
www.wpm.de
www.wopm.de
www.wpom.de
www.wo.de
www.won.de
www.womn.de
www.wonm.de
www.woj.de
www.womj.de
www.wojm.de
www.wok.de
www.womk.de
wom.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.
wom.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.