mofa.gov.mn website information.
mofa.gov.mn domain name is registered by .MN top-level domain registry. See the other sites registred in .MN domain zone.
Following name servers are specified for mofa.gov.mn domain:
- ns1.gov.mn
- ns.gov.mn
According to Alexa traffic rank the highest website mofa.gov.mn position was 34671 (in the world). The lowest Alexa rank position was 999139. Current position of mofa.gov.mn in Alexa rank database is below 1 million.
Website mofa.gov.mn Desktop speed measurement score (66/100) is better than the results of 44.37% of other sites shows that the page desktop performance can be improved.
mofa.gov.mn Mobile usability score (62/100) is better than the results of 7.29% of other sites and shows that the page mobile usability is poor and can be improved.
Mobile speed measurement score of mofa.gov.mn (57/100) is better than the results of 48.04% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
| Date | Rank | Change |
|---|---|---|
| Sep-22-2024 | N/A | N/A |
| Sep-21-2024 | N/A | N/A |
| Sep-20-2024 | N/A | N/A |
| Sep-19-2024 | N/A | N/A |
| Sep-18-2024 | N/A | N/A |
| Sep-17-2024 | N/A | N/A |
| Sep-16-2024 | N/A | N/A |
Advertisement
mofa.gov.mn 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.
mofa.gov.mn 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.
NOT FOUND
>>> Last update of WHOIS database: 2021-06-01T07:16:51Z
mofa.gov.mn server information
mofa.gov.mn desktop page speed rank
Last tested: 2019-06-17
mofa.gov.mn Desktop Speed Test Quick Summary
priority - 21 Enable 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 201.1KiB (87% reduction).
priority - 12 Reduce server response time
In our test, your server responded in 1.4 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.
priority - 9 Minify 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 87KiB (38% reduction).
priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 5 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.
Optimize CSS Delivery of the following:
http://mofa.gov.mn/exp/css/bootstrap.min.css
http://mofa.gov.mn/exp/css/font-awesome.min.css
http://mofa.gov.mn/exp/css/slick.css
http://mofa.gov.mn/exp/css/main.css
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://syndication.twitter.com/settings (10 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
mofa.gov.mn Desktop Resources
| Total Resources | 14 |
| Number of Hosts | 8 |
| Static Resources | 9 |
| JavaScript Resources | 8 |
| CSS Resources | 1 |
mofa.gov.mn Desktop Resource Breakdown
mofa.gov.mn mobile page speed rank
Last tested: 2018-12-09
mofa.gov.mn Mobile Speed Test Quick Summary
priority - 32 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 5 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.
Optimize CSS Delivery of the following:
http://mofa.gov.mn/exp/css/bootstrap.min.css
http://mofa.gov.mn/exp/css/font-awesome.min.css
http://mofa.gov.mn/exp/css/slick.css
http://mofa.gov.mn/exp/css/main.css
priority - 21 Enable 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 206.5KiB (86% reduction).
priority - 18 Reduce server response time
In our test, your server responded in 1.4 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.
priority - 9 Minify 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 86.2KiB (37% reduction).
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://syndication.twitter.com/settings (10 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
mofa.gov.mn Mobile Resources
| Total Resources | 15 |
| Number of Hosts | 8 |
| Static Resources | 10 |
| JavaScript Resources | 9 |
| CSS Resources | 1 |
mofa.gov.mn Mobile Resource Breakdown
mofa.gov.mn mobile page usability
Last tested: 2018-12-09
mofa.gov.mn Mobile Usability Test Quick Summary
priority - 39 Use 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.
Ургамал хамгаа…Журмын төслийг and 28 others render only 5 pixels tall (16 CSS pixels).Монгол Улсад х…ыг дэвшүүлсэн. and 22 others render only 5 pixels tall (16 CSS pixels).Аймгуудын Хүнс…аж ахуйн газар and 11 others render only 5 pixels tall (16 CSS pixels).Сайд, Төрийн н…даргын тушаал and 95 others render only 5 pixels tall (16 CSS pixels).Ноос ноолууран бүтээгдэхүүн and 65 others render only 5 pixels tall (16 CSS pixels).Хөдөө аж ахуйн…ааны мэдээлэл: renders only 5 pixels tall (16 CSS pixels).Салбарын хянал…байгуулж байна and 9 others render only 7 pixels tall (19 CSS pixels).Аймаг дундын о…алтын захиргаа and 10 others render only 5 pixels tall (16 CSS pixels).Эх сурвалж renders only 3 pixels tall (10 CSS pixels).Гурилан бүтээгдэхүүн and 5 others render only 5 pixels tall (16 CSS pixels).2018.12.05 and 5 others render only 4 pixels tall (11 CSS pixels)."Алтан тариа"…ээд, савласан) and 92 others render only 5 pixels tall (16 CSS pixels).ХХААХҮ-ийн дэд…рын мэндчилгээ and 20 others render only 4 pixels tall (13 CSS pixels).Огноо: 2018.12.07 and 4 others render only 4 pixels tall (11 CSS pixels).Хэлэлцүүлэг and 2 others render only 4 pixels tall (11 CSS pixels).Аргачлалын төс…анал авч байна and 2 others render only 4 pixels tall (13 CSS pixels).http://www.biocombinat.mn/ and 14 others render only 4 pixels tall (11 CSS pixels).Хөдөө аж ахуйн…дээллийн индэр renders only 4 pixels tall (13 CSS pixels).www.vcmongolia.mn renders only 4 pixels tall (11 CSS pixels).Зохиогчийн эрх…үйлдвэрийн яам renders only 5 pixels tall (16 CSS pixels).priority - 11 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.
<a href="http://mofa.go…exp/blog/7/240">Бодлого</a> and 98 others are close to other tap targets.The tap target
<a href="http://mofa.go…exp/blog/41/62">Үйл ажиллагаа</a> and 65 others are close to other tap targets.The tap target
<a href="http://mofa.go…cle/entry/1488"></a> and 5 others are close to other tap targets.The tap target
<a href="http://www.nso.mn/">Эх сурвалж</a> is close to 1 other tap targets.The tap target
<a href="https://twitte…Hs3YhgWOh1yDO8"></a> is close to 1 other tap targets.The tap target
<a href="http://mofa.go…cle/entry/1493">Шинэ санаа-Шил…оо: 2018.12.07</a> and 4 others are close to other tap targets.The tap target
<a href="http://mofa.go…cle/entry/1488">ЖДҮХС, МХС, ТЭ…оо: 2018.12.07</a> and 4 others are close to other tap targets.priority - 10 Configure the viewport
Your page specifies a fixed-width desktop viewport. Use a responsive viewport to allow your page to render properly on all devices.
Configuring a viewport specifying width=device-width instead of width=1100 will allow your page to adapt for devices of various widths. This may require additional work to adapt your styling for smaller screens.
priority - 3 Size content to viewport
The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.
The page content is 1,147 CSS pixels wide, but the viewport is only 1,100 CSS pixels wide. The following elements fall outside the viewport:
<div class="parallax-layer"></div> falls outside the viewport.The element
<div class="parallax-layer"></div> falls outside the viewport.The element
<div class="parallax-layer"></div> falls outside the viewport.mofa.gov.mn similar domains
www.mofa.net
www.mofa.org
www.mofa.info
www.mofa.biz
www.mofa.us
www.mofa.mobi
www.ofa.gov.mn
www.mofa.gov.mn
www.nofa.gov.mn
www.mnofa.gov.mn
www.nmofa.gov.mn
www.jofa.gov.mn
www.mjofa.gov.mn
www.jmofa.gov.mn
www.kofa.gov.mn
www.mkofa.gov.mn
www.kmofa.gov.mn
www.mfa.gov.mn
www.mifa.gov.mn
www.moifa.gov.mn
www.miofa.gov.mn
www.mkfa.gov.mn
www.mokfa.gov.mn
www.mlfa.gov.mn
www.molfa.gov.mn
www.mlofa.gov.mn
www.mpfa.gov.mn
www.mopfa.gov.mn
www.mpofa.gov.mn
www.moa.gov.mn
www.moca.gov.mn
www.mofca.gov.mn
www.mocfa.gov.mn
www.moda.gov.mn
www.mofda.gov.mn
www.modfa.gov.mn
www.mora.gov.mn
www.mofra.gov.mn
www.morfa.gov.mn
www.mota.gov.mn
www.mofta.gov.mn
www.motfa.gov.mn
www.moga.gov.mn
www.mofga.gov.mn
www.mogfa.gov.mn
www.mova.gov.mn
www.mofva.gov.mn
www.movfa.gov.mn
www.mof.gov.mn
www.mofq.gov.mn
www.mofaq.gov.mn
www.mofqa.gov.mn
www.mofw.gov.mn
www.mofaw.gov.mn
www.mofwa.gov.mn
www.mofs.gov.mn
www.mofas.gov.mn
www.mofsa.gov.mn
www.mofz.gov.mn
www.mofaz.gov.mn
www.mofza.gov.mn
mofa.gov.mn 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.
mofa.gov.mn 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.