ww2.dk Website Information
Daily Unique Visits: 3,978
Daily Page Views: 15,912
Income Per Day: $45
Estimated Value: $24,300
ww2.dk is registered under .DK top-level domain. Please check other sites in .DK zone.
No name server records were found.
and is probably hosted by One.com A/S. See the full list of other websites hosted by One.com A/S.
The highest website ww2.dk position in Alexa rank database was 10732 and the lowest rank position was 998999. Current position of ww2.dk in Alexa rank database is 315461.
Desktop speed score of ww2.dk (96/100) is better than the results of 94.12% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of ww2.dk (64/100) is better than the results of 11.2% of other sites and means that the page is not mobile-friendly.
Mobile speed score of ww2.dk (95/100) is better than the results of 94.47% of other sites and shows that the landing page performance on mobile devices is excellent.
Advertisement
ww2.dk 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.
ww2.dk 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.
ww2.dk server information
Servers Location
ww2.dk desktop page speed rank
Last tested: 2016-01-10
ww2.dk Desktop Speed Test Quick Summary
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:
http://ww2.dk/graphics/getacro.gif (expiration not specified)
http://ww2.dk/graphics/lw.gif (expiration not specified)
http://ww2.dk/graphics/marble.jpg (expiration not specified)
http://ww2.dk/graphics/ww2.jpg (expiration not specified)
priority - 0Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 4.3KiB (16% reduction).
Losslessly compressing http://ww2.dk/graphics/lw.gif could save 1.2KiB (80% reduction).
Losslessly compressing http://ww2.dk/graphics/ww2.jpg could save 827B (13% reduction).
Losslessly compressing http://ww2.dk/graphics/marble.jpg could save 626B (15% reduction).
ww2.dk Desktop Resource Breakdown
Total Resources | 10 |
Number of Hosts | 1 |
Static Resources | 5 |
ww2.dk mobile page speed rank
Last tested: 2019-11-07
ww2.dk Mobile Speed Test Quick Summary
priority - 4Leverage 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://ww2.dk/graphics/getacro.gif (expiration not specified)
http://ww2.dk/graphics/lw.gif (expiration not specified)
http://ww2.dk/graphics/marble.jpg (expiration not specified)
http://ww2.dk/graphics/ww2.jpg (expiration not specified)
priority - 0Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 2.6KiB (22% reduction).
Compressing http://ww2.dk/graphics/ww2.jpg could save 836B (13% reduction).
Compressing http://ww2.dk/graphics/marble.jpg could save 661B (16% reduction).
ww2.dk Mobile Resource Breakdown
Total Resources | 10 |
Number of Hosts | 1 |
Static Resources | 5 |
ww2.dk mobile page usability
Last tested: 2019-11-07
ww2.dk Mobile Usability Test Quick Summary
priority - 30Use legible font sizes
The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.
The following text fragments have a small font size. Increase the font size to make them more legible.
CONTENTS:
renders only 5 pixels tall (13 CSS pixels).Luftwaffe Offi…reer Summaries
and 16 others render only 5 pixels tall (13 CSS pixels).NEW
and 1 others render only 6 pixels tall (16 CSS pixels).New website online:
renders only 5 pixels tall (13 CSS pixels).This page is n…f information.
and 2 others render only 6 pixels tall (16 CSS pixels).Messerschmitt…41 (Profile by
and 1 others render only 6 pixels tall (16 CSS pixels).Olve Dybvig
renders only 6 pixels tall (16 CSS pixels).Last updated
renders only 6 pixels tall (16 CSS pixels).Credits
renders only 6 pixels tall (16 CSS pixels).Any comments,…y appreciated.
and 1 others render only 6 pixels tall (16 CSS pixels).Michael Holm
renders only 6 pixels tall (16 CSS pixels).priority - 19Size 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="news.htm">What's new</a>
and 16 others are close to other tap targets.<a href="credits.htm">Credits</a>
is close to 1 other tap targets.<a href="http://www.ado…/readstep.html"></a>
is close to 1 other tap targets.priority - 10Configure the viewport
Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.
ww2.dk HTML validation
Errors
Malformed byte sequence: “f8”.
"......"
Start tag seen without seeing a doctype first. Expected “<!DOCTYPE html>”.
"...<html> <hea..."
The “frameset” element is obsolete. Use the “iframe” element and CSS instead, or use server-side includes.
"... </head> <frameset rows="84,*,64"> <fr..." Line: 14 Column: 3 - 25
"...r.htm"> <frameset cols="159,*"> <..."
Attribute “target” not allowed on element “frame” at this point.
"...,*,64"> <frame name="�verst" scrolling="no" noresize target="indhold" src="header.htm"> <fr..." Line: 15 Column: 5 - 65
"...9,*"> <frame name="indhold" target="hovedramme" src="contents.htm"> <..." Line: 16 Column: 5 - 61
"...htm"> <frame name="hovedramme" src="main.htm" target="indhold"> </f..." Line: 18 Column: 3 - 82
"...ameset> <frame name="nederst" scrolling="no" noresize target="indhold" src="footer.htm"> <no..."
Attribute “cols” not allowed on element “frameset” at this point.
"...r.htm"> <frameset cols="159,*"> <..."
The “noframes” element is obsolete. Use the “iframe” element and CSS instead, or use server-side includes.
"...r.htm"> <noframes> <bo..."
ww2.dk similar domains
www.ww2.net
www.ww2.org
www.ww2.info
www.ww2.biz
www.ww2.us
www.ww2.mobi
www.w2.dk
www.ww2.dk
www.qw2.dk
www.wqw2.dk
www.qww2.dk
www.aw2.dk
www.waw2.dk
www.aww2.dk
www.sw2.dk
www.wsw2.dk
www.sww2.dk
www.ew2.dk
www.wew2.dk
www.eww2.dk
www.wq2.dk
www.wwq2.dk
www.wa2.dk
www.wwa2.dk
www.ws2.dk
www.wws2.dk
www.we2.dk
www.wwe2.dk
www.ww.dk
ww2.dk 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.
ww2.dk 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.