M.DK Københavns Metro


m.dk website information.

m.dk domain name is registered by .DK top-level domain registry. See the other sites registred in .DK domain zone.

Following name servers are specified for m.dk domain:

  • authns2.webpartner.dk
  • authns1.webpartner.dk

and probably website m.dk is hosted by FASTLY - Fastly, US web hosting company. Check the complete list of other most popular websites hosted by FASTLY - Fastly, US hosting company.

According to Alexa traffic rank the highest website m.dk position was 38497 (in the world). The lowest Alexa rank position was 998096. Now website m.dk ranked in Alexa database as number 134518 (in the world).

Website m.dk Desktop speed measurement score (45/100) is better than the results of 19.01% of other sites shows that the page desktop performance can be improved.

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

Mobile speed measurement score of m.dk (41/100) is better than the results of 20.18% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Nov-14-2024 134,5181,554
Nov-13-2024 136,0720
Nov-12-2024 136,0720
Nov-11-2024 136,0720
Nov-10-2024 136,072-554
Nov-09-2024 135,518397
Nov-08-2024 135,915497

Advertisement

m.dk Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



m.dk whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


# Hello 167.99.102.248. Your session has been logged.
#
# Copyright (c) 2002 - 2024 by Punktum dk A/S
#
# Version: 5.4.0
#
# The data in the DK Whois database is provided by Punktum dk A/S
# for information purposes only, and to assist persons in obtaining
# information about or related to a domain name registration record.
# We do not guarantee its accuracy. We will reserve the right to remove
# access for entities abusing the data, without notice.
#
# Any use of this material to target advertising or similar activities
# are explicitly forbidden and will be prosecuted. Punktum dk A/S
# requests to be notified of any such activities or suspicions thereof.

Domain: m.dk
DNS: m.dk
Registered: 1997-01-31
Expires: 2025-03-31
Registration period: 1 year
VID: no
DNSSEC: Unsigned delegation
Status: Active

Nameservers
Hostname: ns07.sac-it.dk
Hostname: ns08.sac-it.dk

# Use option --show-handles to get handle information.
# whois -h whois.punktum.dk HELP for more help.

m.dk server information

Servers Location

IP Address
23.100.15.180
Region
Noord-Holland
City
Amsterdam

m.dk desktop page speed rank

Last tested: 2017-05-23


Desktop Speed Bad
45/100

m.dk Desktop Speed Test Quick Summary


priority - 119 Optimize images

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

Optimize the following images to reduce their size by 1.1MiB (72% reduction).

Compressing http://m.dk/~/media/Metro/Forside/Kunst-Sydhavn.jpg?h=500&la=da&w=1170 could save 411.3KiB (71% reduction).
Compressing http://m.dk/~/media/Metro/Forside/Forside-kampagne…jpg?h=500&la=da&w=1170 could save 339.8KiB (76% reduction).
Compressing and resizing http://m.dk/~/media/Metro/Forside/Forside-kampagne….jpg?h=400&la=da&w=906 could save 142.7KiB (96% reduction).
Compressing http://m.dk/~/media/Metro/Metrobyggeriet/Status%20…jpg?h=500&la=da&w=1170 could save 139.5KiB (47% reduction).
Compressing and resizing http://m.dk/~/media/Metro/Forside/Forside-kampagne….jpg?h=400&la=da&w=906 could save 122.7KiB (95% reduction).
Compressing http://m.dk/v3-html/gfx/icon/slider--arrow-next.gif?1.3 could save 1KiB (88% reduction).
Compressing http://m.dk/v3-html/gfx/icon/slider--arrow-prev.gif?1.3 could save 1KiB (88% reduction).
Compressing http://m.dk/v3-html/gfx/icon/links-social--facebook.gif?1.3 could save 999B (75% reduction).
Compressing http://m.dk/v3-html/gfx/icon/sticky--close_sm.gif?1.3 could save 991B (88% reduction).
Compressing http://m.dk/v3-html/gfx/icon/links--arrow.gif?1.3 could save 987B (87% reduction).
Compressing http://m.dk/v3-html/gfx/icon/links-social--youtube.gif?1.3 could save 911B (50% reduction).
Compressing http://m.dk/v3-html/gfx/icon/down--arrow.png?1.3 could save 900B (81% reduction).
Compressing http://m.dk/v3-html/gfx/icon/spot--arrow.png?1.3 could save 898B (81% reduction).
Compressing http://m.dk/v3-html/gfx/icon/metrostatus--info.png?1.3 could save 873B (71% reduction).
Compressing http://m.dk/v3-html/gfx/icon/links-social--twitter.gif?1.3 could save 860B (60% reduction).
Compressing http://m.dk/v3-html/gfx/logo.png?1.3 could save 681B (26% reduction).

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

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

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://maps.googleapis.com/maps/api/js?sensor=false&libraries=geometry
http://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js
http://m.dk/v-kKChCtdAZO8NmIUMPutvQ/v3-html/min/m.min.js

Optimize CSS Delivery of the following:

http://m.dk/v-IWIXrSTaMzz14JviVaWoA/v3-html/min/style.min.css
http://f.fontdeck.com/s/css/BYIdloiyr75z6gbZBPq6eYPYeJQ/m.dk/18430.css

priority - 4 Prioritize 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.

None of the final above-the-fold content could be rendered even with the full HTML response.

priority - 2 Leverage 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://maps.googleapis.com/maps/api/js?sensor=false&libraries=geometry (30 minutes)
http://m.dk/v-IWIXrSTaMzz14JviVaWoA/v3-html/min/style.min.css (60 minutes)
http://m.dk/v-kKChCtdAZO8NmIUMPutvQ/v3-html/min/m.min.js (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)

priority - 1 Minify 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 9.7KiB (16% reduction).

Minifying http://m.dk/v-kKChCtdAZO8NmIUMPutvQ/v3-html/min/m.min.js could save 9.2KiB (16% reduction) after compression.
Minifying http://m.dk/v3-html/js/libs/instafeed.min.js?_=1495521797195 could save 515B (16% reduction) after compression.

priority - 0 Reduce server response time

In our test, your server responded in 0.21 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

m.dk Desktop Resources

Total Resources54
Number of Hosts8
Static Resources30
JavaScript Resources8
CSS Resources1

m.dk Desktop Resource Breakdown

m.dk mobile page speed rank

Last tested: 2017-05-23


Mobile Speed Bad
41/100

m.dk Mobile Speed Test Quick Summary


priority - 107 Optimize images

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

Optimize the following images to reduce their size by 1MiB (65% reduction).

Compressing http://m.dk/~/media/Metro/Forside/Kunst-Sydhavn.jpg?h=500&la=da&w=1170 could save 411.3KiB (71% reduction).
Compressing http://m.dk/~/media/Metro/Forside/Forside-kampagne…jpg?h=500&la=da&w=1170 could save 339.8KiB (76% reduction).
Compressing http://m.dk/~/media/Metro/Metrobyggeriet/Status%20…jpg?h=500&la=da&w=1170 could save 139.5KiB (47% reduction).
Compressing http://m.dk/~/media/Metro/Forside/Forside-kampagne….jpg?h=400&la=da&w=906 could save 94.5KiB (64% reduction).
Compressing http://m.dk/~/media/Metro/Forside/Forside-kampagne….jpg?h=400&la=da&w=906 could save 56.4KiB (44% reduction).
Compressing http://m.dk/v3-html/gfx/pattern/pattern-noise.png?1.3 could save 1.4KiB (17% reduction).
Compressing http://m.dk/v3-html/gfx/icon/slider--arrow-next.gif?1.3 could save 1KiB (88% reduction).
Compressing http://m.dk/v3-html/gfx/icon/slider--arrow-prev.gif?1.3 could save 1KiB (88% reduction).
Compressing http://m.dk/v3-html/gfx/icon/sticky--close_sm.gif?1.3 could save 991B (88% reduction).
Compressing http://m.dk/v3-html/gfx/icon/down--arrow.png?1.3 could save 900B (81% reduction).
Compressing http://m.dk/v3-html/gfx/icon/spot--arrow.png?1.3 could save 898B (81% reduction).
Compressing http://m.dk/v3-html/gfx/icon/metrostatus--info.png?1.3 could save 873B (71% reduction).
Compressing http://m.dk/v3-html/gfx/logo.png?1.3 could save 681B (26% reduction).

priority - 32 Eliminate 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.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://maps.googleapis.com/maps/api/js?sensor=false&libraries=geometry
http://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js
http://m.dk/v-kKChCtdAZO8NmIUMPutvQ/v3-html/min/m.min.js

Optimize CSS Delivery of the following:

http://m.dk/v-IWIXrSTaMzz14JviVaWoA/v3-html/min/style.min.css

priority - 16 Prioritize 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.

None of the final above-the-fold content could be rendered even with the full HTML response.

priority - 3 Leverage 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://maps.googleapis.com/maps/api/js?sensor=false&libraries=geometry (30 minutes)
http://m.dk/v-IWIXrSTaMzz14JviVaWoA/v3-html/min/style.min.css (60 minutes)
http://m.dk/v-kKChCtdAZO8NmIUMPutvQ/v3-html/min/m.min.js (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)

priority - 1 Minify 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 9.7KiB (16% reduction).

Minifying http://m.dk/v-kKChCtdAZO8NmIUMPutvQ/v3-html/min/m.min.js could save 9.2KiB (16% reduction) after compression.
Minifying http://m.dk/v3-html/js/libs/instafeed.min.js?_=1495521793638 could save 515B (16% reduction) after compression.

priority - 0 Reduce server response time

In our test, your server responded in 0.22 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

m.dk Mobile Resources

Total Resources52
Number of Hosts8
Static Resources30
JavaScript Resources8
CSS Resources1

m.dk Mobile Resource Breakdown

m.dk mobile page usability

Last tested: 2017-05-23


Mobile Usability Good
99/100

m.dk Mobile Usability Test Quick Summary


priority - 0 Size 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="#" class="dismiss-disclaimer">Luk</a> is close to 1 other tap targets.

The tap target <div class="train-info--sticky">Trafikinformation</div> is close to 1 other tap targets.

m.dk similar domains

Similar domains:
www.m.com
www.m.net
www.m.org
www.m.info
www.m.biz
www.m.us
www.m.mobi
www..dk
www.m.dk
www.n.dk
www.mn.dk
www.nm.dk
www.j.dk
www.mj.dk
www.jm.dk
www.k.dk
www.mk.dk
www.km.dk

m.dk Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


m.dk TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.