namus.gov Website Information
Daily Unique Visits: 10,569
Daily Page Views: 52,845
Income Per Day: $132
Estimated Value: $79,200
This website is located in United States and is using following IP address 149.101.127.151. See the complete list of popular websites hosted in United States.
namus.gov is registered under .GOV top-level domain. Please check other sites in .GOV zone.
Website namus.gov is using the following name servers:
- ns-jdcw-01.usdoj.gov
- ns-jdcw-02.usdoj.gov
and is probably hosted by USDOJ-GOV - United States Department of Justice, US. See the full list of other websites hosted by USDOJ-GOV - United States Department of Justice, US.
The highest website namus.gov position in Alexa rank database was 28363 and the lowest rank position was 998642. Current position of namus.gov in Alexa rank database is 128921.
Desktop speed score of namus.gov (86/100) is better than the results of 82.23% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of namus.gov (65/100) is better than the results of 13.11% of other sites and means that the page is not mobile-friendly.
Mobile speed score of namus.gov (71/100) is better than the results of 78.26% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
namus.gov 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.
namus.gov 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.
Domain Name: NAMUS.GOV
Status: ACTIVE
Security Contact Email: Responsible_Disclosure@usdoj.gov
>>> Last update of whois database: 2022-07-14T11:03:59Z
namus.gov server information
Servers Location
namus.gov desktop page speed rank
Last tested: 2019-11-28
namus.gov Desktop Speed Test Quick Summary
priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
https://namus.gov/css/screen.css
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://namus.gov/css/screen.css (expiration not specified)
https://namus.gov/images/missing.gif (expiration not specified)
https://namus.gov/images/namus-video.png (expiration not specified)
https://namus.gov/images/namus_logo.gif (expiration not specified)
https://namus.gov/images/namus_masthead_h.gif (expiration not specified)
https://namus.gov/images/namus_unclaimed.gif (expiration not specified)
https://namus.gov/images/ojp_masthead.gif (expiration not specified)
https://namus.gov/images/unidentified.gif (expiration not specified)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 1Enable 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 10.4KiB (68% reduction).
Compressing https://namus.gov/css/screen.css could save 4.1KiB (73% reduction).
Compressing https://namus.gov/css/print.css could save 567B (57% reduction).
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 1.6KiB (29% reduction).
priority - 0Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 1KiB (38% reduction).
namus.gov Desktop Resource Breakdown
| Total Resources | 15 |
| Number of Hosts | 3 |
| Static Resources | 10 |
| JavaScript Resources | 2 |
| CSS Resources | 2 |
namus.gov mobile page speed rank
Last tested: 2017-05-03
namus.gov Mobile Speed Test Quick Summary
priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
https://namus.gov/css/screen.css
priority - 7Leverage 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://namus.gov/css/screen.css (expiration not specified)
https://namus.gov/images/missing.gif (expiration not specified)
https://namus.gov/images/namus-video.png (expiration not specified)
https://namus.gov/images/namus_logo.gif (expiration not specified)
https://namus.gov/images/namus_masthead_h.gif (expiration not specified)
https://namus.gov/images/namus_unclaimed.gif (expiration not specified)
https://namus.gov/images/ojp_masthead.gif (expiration not specified)
https://namus.gov/images/unidentified.gif (expiration not specified)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 1Enable 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 10.4KiB (68% reduction).
Compressing https://namus.gov/css/screen.css could save 4.1KiB (73% reduction).
Compressing https://namus.gov/css/print.css could save 567B (57% reduction).
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 1.6KiB (29% reduction).
priority - 0Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 1KiB (38% reduction).
namus.gov Mobile Resource Breakdown
| Total Resources | 15 |
| Number of Hosts | 3 |
| Static Resources | 10 |
| JavaScript Resources | 2 |
| CSS Resources | 2 |
namus.gov mobile page usability
Last tested: 2017-05-03
namus.gov Mobile Usability Test Quick Summary
priority - 40Use 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.
Volunteer Information and 4 others render only 5 pixels tall (13 CSS pixels).NamUs Behind t…Why It Matters and 4 others render only 5 pixels tall (12 CSS pixels).Watch an 6-minute video: and 1 others render only 4 pixels tall (10 CSS pixels).NamUs 2.0: Upg…in the Works! and 3 others render only 5 pixels tall (13 CSS pixels).Throughout the…the databases. and 1 others render only 5 pixels tall (13 CSS pixels).Learn about a…ical incidents renders only 5 pixels tall (13 CSS pixels).The National I…g these cases. and 4 others render only 5 pixels tall (13 CSS pixels).contains infor…t legislation. and 5 others render only 5 pixels tall (13 CSS pixels).Language Acces…eso al Idioma) and 9 others render only 5 pixels tall (13 CSS pixels).| and 7 others render only 5 pixels tall (13 CSS pixels).Office of Justice Programs renders only 4 pixels tall (10 CSS pixels).• 810 7th Stre…gton, DC 20531 renders only 4 pixels tall (10 CSS pixels).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.
priority - 5Size 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="index.htm">Home</a> is close to 1 other tap targets.<a href="https://www.findthemissing.org">Missing Persons</a> and 3 others are close to other tap targets.<a href="http://www.usdoj.gov/">DOJ Home</a> and 9 others are close to other tap targets.<a href="http://www.ojp.gov">Office of Justice Programs</a> is close to 2 other tap targets.namus.gov HTML validation
Errors
Obsolete doctype. Expected “<!DOCTYPE html>”.
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html..."
Internal encoding declaration “iso-8859-1” disagrees with the actual encoding of the document (“utf-8”).
"...> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> <titl..." Line: 20 Column: 1 - 74
"...dif]--> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <meta..."
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”.
"...> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> <titl..." Line: 20 Column: 1 - 74
"...dif]--> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <meta..."
A document must not include more than one “meta” element with a “http-equiv” attribute whose value is “content-type”.
"...dif]--> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <meta..."
Malformed byte sequence: “97”.
"......"
The “center” element is obsolete. Use CSS instead.
"...lbi" --> <center> <a hr..."
No “li” element in scope but a “li” end tag seen.
"...SA.gov</a></li> </cen..."
Warnings
The “language” attribute on the “script” element is obsolete. You can safely omit it.
"...7uA=" /> <script language="javascript" id="_fed_an_ua_tag" src="https://dap.digitalgov.gov/Universal-Federated-Analytics-Min.1.0.js?agency=DOJ&subagency=NIJ"></scri..."
The document is not mappable to XML 1.0 due to two consecutive hyphens in a comment.
"...v></div> *** ---> </div> <di..."
The “name” attribute is obsolete. Consider putting an “id” attribute on the nearest container instead.
"...textarea"><a name="link" id="link"></a> ..."
This document appears to be written in English. Consider adding “lang="en"” (or variant) to the “html” start tag.
"...rict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <hea..."
namus.gov similar domains
www.namus.net
www.namus.org
www.namus.info
www.namus.biz
www.namus.us
www.namus.mobi
www.amus.gov
www.namus.gov
www.bamus.gov
www.nbamus.gov
www.bnamus.gov
www.hamus.gov
www.nhamus.gov
www.hnamus.gov
www.jamus.gov
www.njamus.gov
www.jnamus.gov
www.mamus.gov
www.nmamus.gov
www.mnamus.gov
www.nmus.gov
www.nqmus.gov
www.naqmus.gov
www.nqamus.gov
www.nwmus.gov
www.nawmus.gov
www.nwamus.gov
www.nsmus.gov
www.nasmus.gov
www.nsamus.gov
www.nzmus.gov
www.nazmus.gov
www.nzamus.gov
www.naus.gov
www.nanus.gov
www.namnus.gov
www.nanmus.gov
www.najus.gov
www.namjus.gov
www.najmus.gov
www.nakus.gov
www.namkus.gov
www.nakmus.gov
www.nams.gov
www.namys.gov
www.namuys.gov
www.namyus.gov
www.namhs.gov
www.namuhs.gov
www.namhus.gov
www.namjs.gov
www.namujs.gov
www.namis.gov
www.namuis.gov
www.namius.gov
www.namu.gov
www.namuw.gov
www.namusw.gov
www.namuws.gov
www.namue.gov
www.namuse.gov
www.namues.gov
www.namud.gov
www.namusd.gov
www.namuds.gov
www.namuz.gov
www.namusz.gov
www.namuzs.gov
www.namux.gov
www.namusx.gov
www.namuxs.gov
www.namua.gov
www.namusa.gov
www.namuas.gov
namus.gov 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.
namus.gov 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.