NH.EE Noorte hääl - Portaal noortele ja noortest


nh.ee website information.

nh.ee domain name is registered by .EE top-level domain registry. See the other sites registred in .EE domain zone.

Following name servers are specified for nh.ee domain:

  • ns-1131.awsdns-13.org
  • ns-1721.awsdns-23.co.uk
  • ns-206.awsdns-25.com
  • ns-939.awsdns-53.net
  • ns.delfi.ee
  • ns2.delfi.ee

and probably website nh.ee is hosted by NTU-TW National Taiwan University, TW web hosting company. Check the complete list of other most popular websites hosted by NTU-TW National Taiwan University, TW hosting company.

According to Alexa traffic rank the highest website nh.ee position was 20762 (in the world). The lowest Alexa rank position was 998539. Now website nh.ee ranked in Alexa database as number 808326 (in the world).

Website nh.ee Desktop speed measurement score (70/100) is better than the results of 50.91% of other sites shows that the page desktop performance can be improved.

nh.ee 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 nh.ee (39/100) is better than the results of 17.83% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Sep-22-2024 808,326-29,477
Sep-21-2024 778,84910,270
Sep-20-2024 789,119-9,559
Sep-19-2024 779,560-4,389
Sep-18-2024 775,17124,436
Sep-17-2024 799,60711,688
Sep-16-2024 811,295-22,797

Advertisement

nh.ee 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.



nh.ee 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.


Search results may not be used for commercial, advertising, recompilation,
repackaging, redistribution, reuse, obscuring or other similar activities.

Estonia .ee Top Level Domain WHOIS server

Domain:
name: nh.ee
status: ok (paid and in zone)
registered: 2010-08-04 17:44:56 +03:00
changed: 2020-08-05 13:14:25 +03:00
expire: 2021-08-05
outzone:
delete:

Registrant:
name: AS EKSPRESS MEEDIA
org id: 10586863
country: EE
email: Not Disclosed - Visit www.internet.ee for webbased WHOIS
changed: 2020-08-05 13:14:25 +03:00

Administrative contact:
name: Not Disclosed - Visit www.internet.ee for webbased WHOIS
email: Not Disclosed - Visit www.internet.ee for webbased WHOIS
changed: Not Disclosed - Visit www.internet.ee for webbased WHOIS

Technical contact:
name: Not Disclosed - Visit www.internet.ee for webbased WHOIS
email: Not Disclosed - Visit www.internet.ee for webbased WHOIS
changed: Not Disclosed - Visit www.internet.ee for webbased WHOIS

Registrar:
name: Telia Eesti AS
url: http://www.telia.ee
phone: +372 655 9188
changed: 2019-12-04 13:26:47 +02:00

Name servers:
nserver: ns-1131.awsdns-13.org
nserver: ns-1721.awsdns-23.co.uk
nserver: ns-206.awsdns-25.com
nserver: ns2.delfi.ee
nserver: ns-939.awsdns-53.net
nserver: ns.delfi.ee
changed: 2019-01-22 16:26:43 +02:00

Estonia .ee Top Level Domain WHOIS server
More information at http://internet.ee

nh.ee server information

Servers Location

IP Address
185.20.100.195
185.20.100.193
185.20.100.194
185.20.100.192
Region
Harjumaa
Harjumaa
Harjumaa
Harjumaa
City
Tallinn
Tallinn
Tallinn
Tallinn

nh.ee desktop page speed rank

Last tested: 2019-01-22


Desktop Speed Medium
70/100

nh.ee Desktop Speed Test Quick Summary


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

Your page has 10 blocking script resources and 9 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:

http://g2.nh.ee/scms/?g=j&1383734069
http://g2.nh.ee/scms/?g=jsh_ee_nd,dfp,dweather-h,i…sh,jp,dw,ps&1439466626
http://delfiee.adocean.pl/files/js/ado.js
http://delfiee.adocean.pl/_1439804331566/ad.js?id=…fP9gUQe3iOWYshaXjML.l7
http://delfiadee.hit.gemius.pl/_1439804331567/redo…/sarg=55D1ABAB2045F5EF
http://delfiee.adocean.pl/_1439804331568/ad.js?id=…rtehaal_frontpage/fv=-
http://g1.nh.ee/js/swfobject.js
http://delfiee.adocean.pl/_1439804331570/ad.js?id=…rtehaal_frontpage/fv=-
http://g2.nh.ee/scms/?g=enreach_b&1438000065
http://delfiee.adocean.pl/_1439804331579/ad.js?id=…rtehaal_frontpage/fv=-

Optimize CSS Delivery of the following:

http://g2.nh.ee/scms/?g=dweather-h.css,ilmateade-h.css&1434618692
http://g2.nh.ee/scms/?g=delfi-header.css&1439803362
http://h.delfi.ee/g/h/noortehaal.css?v=1.30
http://g1.nh.ee/jquery/fancybox/fancybox.css
http://g3.nh.ee/nh/s/_/b64_global.css?1049
http://g2.nh.ee/scms/?g=noortehaal-cat.css&1433165003
http://g2.nh.ee/scms/?g=delfi2012.css&1425558480
http://g.delfi.ee/n/r/se/_/b64_se15.css?6144
http://g.delfi.ee/g/r/pup/_/b64_pup.css?bb64

priority - 7 Optimize images

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

Optimize the following images to reduce their size by 62.5KiB (26% reduction).

Losslessly compressing http://delfiee.adocean.pl/files/x/kkn/tplrtdw/vfdr…dascreate_1800x450.jpg could save 23.9KiB (41% reduction).
Losslessly compressing http://delfiee.adocean.pl/files/x/kkn/tplrtdw/yemk…ascreate_1600x1200.jpg could save 15.2KiB (16% reduction).
Losslessly compressing http://g.delfi.ee/c/bg/bg_shadow_big.png?1 could save 6.3KiB (17% reduction).
Losslessly compressing http://g.delfi.ee/nh/img/header.gif?1 could save 3.7KiB (20% reduction).
Losslessly compressing http://g.delfi.ee/tvguide/channel_logos/delfi_908_32_foxcrime.png could save 2.6KiB (79% reduction).
Losslessly compressing http://g.delfi.ee/tvguide/channel_logos/delfi_11_32_etv.png could save 2.6KiB (68% reduction).
Losslessly compressing http://g.delfi.ee/nh/img/search_bg.gif?1 could save 1.5KiB (65% reduction).
Losslessly compressing http://h.delfi.ee/g/h/s/searchbox_bg.gif could save 938B (80% reduction).
Losslessly compressing http://g.delfi.ee/tvguide/channel_logos/delfi_6_32_tv6.png could save 932B (28% reduction).
Losslessly compressing http://g.delfi.ee/tvguide/channel_logos/delfi_13_32_tv3.png could save 898B (31% reduction).
Losslessly compressing http://h.delfi.ee/g/h/l/toptab_bg_inactive.gif could save 808B (64% reduction).
Losslessly compressing http://g.delfi.ee/tvguide/channel_logos/delfi_914_32_foxlife.png could save 773B (36% reduction).
Losslessly compressing http://g.delfi.ee/ct/fl/filmilaenutus_bg2.jpg? could save 656B (7% reduction).
Losslessly compressing http://g.delfi.ee/nh/b/btn_bg.gif?1 could save 643B (62% reduction).
Losslessly compressing http://h.delfi.ee/g/h/n/nh_bg.gif could save 637B (77% reduction).
Losslessly compressing http://h.delfi.ee/g/h/tt/toptab_noortehaal.gif could save 599B (66% reduction).

priority - 6 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 60.3KiB (77% reduction).

Compressing http://delfiee.adocean.pl/_1439804331568/ad.js?id=…rtehaal_frontpage/fv=- could save 31.4KiB (85% reduction).
Compressing http://delfiee.adocean.pl/_1439804331579/ad.js?id=…rtehaal_frontpage/fv=- could save 12.3KiB (77% reduction).
Compressing http://delfiee.adocean.pl/_1439804331570/ad.js?id=…rtehaal_frontpage/fv=- could save 10.2KiB (76% reduction).
Compressing http://g1.nh.ee/js/swfobject.js could save 5.4KiB (59% reduction).
Compressing http://g3.nh.ee/t/e/spring.js?160 could save 1KiB (46% reduction).

priority - 4 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:

http://delfi.spring-tns.net/blank.gif (expiration not specified)
http://delfi.spring-tns.net/survey.js (expiration not specified)
http://kava.delfi.ee/tvguide/fe/service.php?callba…extra%5Blogo_size%5D=2 (5 minutes)
http://connect.facebook.net/et_EE/all.js (20 minutes)
http://ekspresskonto.ee/delfi.ee/sso/embed.php?s=idp_header (30 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
http://static.chartbeat.com/js/chartbeat.js (2 hours)
http://www.google-analytics.com/ga.js (2 hours)

priority - 0 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 1.7KiB (5% reduction).

Minifying http://delfiee.adocean.pl/_1439804331568/ad.js?id=…rtehaal_frontpage/fv=- could save 1.1KiB (3% reduction).
Minifying http://gaee.hit.gemius.pl/xgemius.js could save 633B (13% reduction) after compression.

priority - 0 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 1.2KiB (10% reduction).

Minifying http://noortehaal.delfi.ee/ could save 1.2KiB (10% reduction) after compression.

nh.ee Desktop Resources

Total Resources139
Number of Hosts26
Static Resources84
JavaScript Resources29
CSS Resources10

nh.ee Desktop Resource Breakdown

nh.ee mobile page speed rank

Last tested: 2019-01-22


Mobile Speed Bad
39/100

nh.ee Mobile Speed Test Quick Summary


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

Your page has 10 blocking script resources and 4 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:

http://g2.nh.ee/scms/?g=mdelfi.js&1439801082
http://delfiee.adocean.pl/files/js/ado.js
http://delfiee.adocean.pl/_1439804326935/ad.js?id=…fP9gUQe3iOWYshaXjML.l7
http://delfiadee.hit.gemius.pl/_1439804326936/redo…/sarg=55D1ABA770EC9546
http://delfiee.adocean.pl/_1439804326937/ad.js?id=…hannel_noortehaal/fv=-
http://g2.nh.ee/scms/?g=enreach_b&1438000065
http://ekspresskonto.ee/delfi.ee/sso/embed.php?s=m…_sso_login_button&l=et
http://g4.nh.ee/t/t.js
http://g3.nh.ee/t/e/spring.js?160
http://g2.nh.ee/scms/?g=enreach_f&1433508783

Optimize CSS Delivery of the following:

http://g2.nh.ee/scms/?g=mdelfi.css&1439800554
http://g4.nh.ee/mb/s/_/b64_inoortehaal.css?6036
http://ekspresskonto.ee/delfi.ee/sso/styles/mobile.css?c=525a
http://ekspresskonto.ee/delfi.ee/sso/styles/messboxes.css?c=525a

priority - 26 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.

http://nh.ee/
http://noortehaal.delfi.ee/
http://m.noortehaal.delfi.ee/

priority - 12 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 117KiB (70% reduction).

Compressing http://muu.delfi.ee/m/rmb/121/251/curlify.min.js?ver=5 could save 97.5KiB (72% reduction).
Compressing http://delfiee.adocean.pl/_1439804326937/ad.js?id=…hannel_noortehaal/fv=- could save 7.8KiB (75% reduction).
Compressing http://delfiee.adocean.pl/_1439804327064/ad.js?id=…hannel_noortehaal/fv=- could save 3.8KiB (60% reduction).
Compressing http://delfiee.adocean.pl/_1439804327062/ad.js?id=…hannel_noortehaal/fv=- could save 3.8KiB (61% reduction).
Compressing http://muu.delfi.ee/m/rmb/121/251/polys.js could save 3KiB (57% reduction).
Compressing http://g3.nh.ee/t/e/spring.js?160 could save 1KiB (46% reduction).

priority - 8 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.

Only about 58% of the final above-the-fold content could be rendered with the full HTML response.

priority - 7 Reduce server response time

In our test, your server responded in 0.66 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 - 4 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:

http://delfi.spring-tns.net/blank.gif (expiration not specified)
http://delfi.spring-tns.net/survey.js (expiration not specified)
http://ekspresskonto.ee/delfi.ee/sso/embed.php?s=m…_sso_login_button&l=et (30 minutes)
http://static.chartbeat.com/js/chartbeat.js (2 hours)
http://www.google-analytics.com/analytics.js (2 hours)
http://www.google-analytics.com/ga.js (2 hours)

priority - 1 Optimize images

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

Optimize the following images to reduce their size by 9.3KiB (6% reduction).

Losslessly compressing http://delfiee.adocean.pl/files/x/rop/qgthnwv/qleoqqmfjy/DELFI_600x600.jpg could save 5.4KiB (8% reduction).
Losslessly compressing http://g3.nh.ee/mb/ic/delfitv@2x.png could save 2.4KiB (65% reduction).
Losslessly compressing http://delfiee.adocean.pl/files/x/wbf/tioesgq/nmle…ON24_600x600_aug_2.jpg could save 939B (2% reduction).
Losslessly compressing http://g4.nh.ee/mb/ic/horoskoop_b.png could save 530B (19% reduction).

priority - 0 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 3.1KiB (12% reduction).

Minifying http://m.noortehaal.delfi.ee/ could save 2.4KiB (11% reduction) after compression.
Minifying http://muu.delfi.ee/m/rmb/121/251/index.html could save 674B (19% reduction) after compression.

priority - 0 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 1.8KiB (3% reduction).

Minifying http://gaee.hit.gemius.pl/xgemius.js could save 633B (13% reduction) after compression.
Minifying http://gdeee.hit.gemius.pl/gemius.js could save 616B (13% reduction) after compression.
Minifying http://g2.nh.ee/scms/?g=mdelfi.js&1439801082 could save 554B (1% reduction) after compression.

nh.ee Mobile Resources

Total Resources108
Number of Hosts22
Static Resources64
JavaScript Resources31
CSS Resources4

nh.ee Mobile Resource Breakdown

nh.ee mobile page usability

Last tested: 2019-01-22


Mobile Usability Good
99/100

nh.ee 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 <div id="mainContent" class="active"></div> is close to 1 other tap targets.

The tap target <a href="http://m.noortehaal.delfi.ee/" class="header-logo"></a> is close to 1 other tap targets.

The tap target <a href="http://delfiad….ee%2Fkorvpall"></a> is close to 1 other tap targets.

The tap target <a href="http://m.noort…55&amp;com=1&amp;reg=1" class="commentCount">(40)</a> and 11 others are close to other tap targets.
The tap target <a href="http://m.noort…hp?id=72032099" class="md-scrollpos">VAATA, milline…lev poiss täna</a> and 14 others are close to other tap targets.
The tap target <a href="http://m.noort…99&amp;com=1&amp;reg=1" class="commentCount">(10)</a> and 46 others are close to other tap targets.
The tap target <a href="http://m.noort…hp?id=72219083" class="md-scrollpos">Lõpureisi VIDE…hüvasti jätta!</a> and 2 others are close to other tap targets.

nh.ee similar domains

Similar domains:
www.nh.com
www.nh.net
www.nh.org
www.nh.info
www.nh.biz
www.nh.us
www.nh.mobi
www.h.ee
www.nh.ee
www.bh.ee
www.nbh.ee
www.bnh.ee
www.hh.ee
www.nhh.ee
www.hnh.ee
www.jh.ee
www.njh.ee
www.jnh.ee
www.mh.ee
www.nmh.ee
www.mnh.ee
www.n.ee
www.nb.ee
www.nhb.ee
www.ng.ee
www.nhg.ee
www.ngh.ee
www.ny.ee
www.nhy.ee
www.nyh.ee
www.nu.ee
www.nhu.ee
www.nuh.ee
www.nj.ee
www.nhj.ee
www.nn.ee
www.nhn.ee
www.nnh.ee

nh.ee 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.


nh.ee 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.