nih.gov website information.
nih.gov domain name is registered by .GOV top-level domain registry. See the other sites registred in .GOV domain zone.
Following name servers are specified for nih.gov domain:
- ns.nih.gov
- ns3.nih.gov
- ns2.nih.gov
and probably website nih.gov is hosted by Akamai International B.V. web hosting company. Check the complete list of other most popular websites hosted by Akamai International B.V. hosting company.
According to Alexa traffic rank the highest website nih.gov position was 42 (in the world). The lowest Alexa rank position was 46. Now website nih.gov ranked in Alexa database as number 45 (in the world).
Website nih.gov Desktop speed measurement score (85/100) is better than the results of 80% of other sites and shows that the page is performing great on desktop computers.
nih.gov 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 nih.gov (67/100) is better than the results of 70.58% 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 |
|---|---|---|
| Nov-16-2024 | 45 | 1 |
| Nov-15-2024 | 46 | -1 |
| Nov-14-2024 | 45 | 0 |
| Nov-13-2024 | 45 | 0 |
| Nov-12-2024 | 45 | 0 |
| Nov-11-2024 | 45 | 0 |
| Nov-10-2024 | 45 | 0 |
Advertisement
nih.gov 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.
nih.gov 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.
% DOTGOV WHOIS Server ready
Domain Name: NIH.GOV
Status: ACTIVE
Security Contact Email: ResponsibleDisclosure@hhs.gov
>>> Last update of whois database: 2022-07-01T14:13:01Z
nih.gov server information
nih.gov desktop page speed rank
Last tested: 2018-10-07
nih.gov Desktop Speed Test Quick Summary
priority - 9 Avoid landing page redirects
Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
https://nih.gov/
https://www.nih.gov/
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://js.api.here.com/v3/3.0/mapsjs-mapevents.js (expiration not specified)
https://js.api.here.com/v3/3.0/mapsjs-service.js (expiration not specified)
https://js.api.here.com/v3/3.0/mapsjs-ui.css (expiration not specified)
https://js.api.here.com/v3/3.0/mapsjs-ui.js (expiration not specified)
https://search.usa.gov/assets/sayt_loader.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 2 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script 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:
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 8.4KiB (32% reduction).
Minifying https://www.nih.gov/sites/default/files/js/js_Um_q…54gm2IzhJHenEGAjCVs.js could save 2.2KiB (14% reduction) after compression.
Minifying https://www.nih.gov/sites/default/files/js/js_NpX2…BHleaYLOx5R9EWBOMRU.js could save 875B (45% reduction) after compression.
Minifying https://www.nih.gov/sites/default/files/js/js_5idE…kWmZlZv-WjSkHlWhoYk.js could save 255B (39% reduction) after compression.
priority - 1 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 7.2KiB (28% reduction).
Compressing and resizing https://www.nih.gov/sites/all/themes/nih/images/nih-logo-color.png could save 3.2KiB (33% reduction).
priority - 0 Minify 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 850B (29% reduction).
priority - 0 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 366B (43% reduction).
nih.gov Desktop Resources
| Total Resources | 60 |
| Number of Hosts | 14 |
| Static Resources | 47 |
| JavaScript Resources | 20 |
| CSS Resources | 11 |
nih.gov Desktop Resource Breakdown
nih.gov mobile page speed rank
Last tested: 2018-10-07
nih.gov Mobile Speed Test Quick Summary
priority - 34 Avoid landing page redirects
Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
https://nih.gov/
https://www.nih.gov/
priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script 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:
priority - 5 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://js.api.here.com/v3/3.0/mapsjs-mapevents.js (expiration not specified)
https://js.api.here.com/v3/3.0/mapsjs-service.js (expiration not specified)
https://js.api.here.com/v3/3.0/mapsjs-ui.css (expiration not specified)
https://js.api.here.com/v3/3.0/mapsjs-ui.js (expiration not specified)
https://search.usa.gov/assets/sayt_loader.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 2 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 17.6KiB (37% reduction).
Compressing https://www.nih.gov/sites/all/themes/nih/images/ge…ons-2x-sa080fff095.png could save 7.9KiB (21% reduction).
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 8.4KiB (32% reduction).
Minifying https://www.nih.gov/sites/default/files/js/js_Um_q…54gm2IzhJHenEGAjCVs.js could save 2.2KiB (14% reduction) after compression.
Minifying https://www.nih.gov/sites/default/files/js/js_NpX2…BHleaYLOx5R9EWBOMRU.js could save 875B (45% reduction) after compression.
Minifying https://www.nih.gov/sites/default/files/js/js_5idE…kWmZlZv-WjSkHlWhoYk.js could save 255B (39% reduction) after compression.
priority - 0 Minify 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 850B (29% reduction).
priority - 0 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 366B (43% reduction).
nih.gov Mobile Resources
| Total Resources | 59 |
| Number of Hosts | 14 |
| Static Resources | 45 |
| JavaScript Resources | 19 |
| CSS Resources | 10 |
nih.gov Mobile Resource Breakdown
nih.gov mobile page usability
Last tested: 2018-10-07
nih.gov 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.
<a href="#main-content" class="element-invisi…ment-focusable">Skip to main content</a> is close to 1 other tap targets.nih.gov similar domains
www.nih.net
www.nih.org
www.nih.info
www.nih.biz
www.nih.us
www.nih.mobi
www.ih.gov
www.nih.gov
www.bih.gov
www.nbih.gov
www.bnih.gov
www.hih.gov
www.nhih.gov
www.hnih.gov
www.jih.gov
www.njih.gov
www.jnih.gov
www.mih.gov
www.nmih.gov
www.mnih.gov
www.nh.gov
www.nuh.gov
www.niuh.gov
www.nuih.gov
www.njh.gov
www.nijh.gov
www.nkh.gov
www.nikh.gov
www.nkih.gov
www.noh.gov
www.nioh.gov
www.noih.gov
www.ni.gov
www.nib.gov
www.nihb.gov
www.nibh.gov
www.nig.gov
www.nihg.gov
www.nigh.gov
www.niy.gov
www.nihy.gov
www.niyh.gov
www.niu.gov
www.nihu.gov
www.nij.gov
www.nihj.gov
www.nin.gov
www.nihn.gov
www.ninh.gov
nih.gov 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.
nih.gov 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.