NGACN.CC 艾泽拉斯国家地理论坛


ngacn.cc website information.

ngacn.cc website servers are located in China and are responding from following IP address 222.180.162.237. Check the full list of most visited websites located in China.

ngacn.cc domain name is registered by .CC top-level domain registry. See the other sites registred in .CC domain zone.

Following name servers are specified for ngacn.cc domain:

  • ns2.ngacn.cc
  • ns1.ngacn.cc

and probably website ngacn.cc is hosted by ngacn.cc web hosting company. Check the complete list of other most popular websites hosted by ngacn.cc hosting company.

According to Alexa traffic rank the highest website ngacn.cc position was 268 (in the world). The lowest Alexa rank position was 867958. Now website ngacn.cc ranked in Alexa database as number 3169 (in the world).

Website ngacn.cc Desktop speed measurement score (66/100) is better than the results of 44.27% of other sites shows that the page desktop performance can be improved.

ngacn.cc Mobile usability score (89/100) is better than the results of 45.16% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of ngacn.cc (46/100) is better than the results of 24.03% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Nov-20-2019 3,169-412
Nov-19-2019 2,757282
Nov-18-2019 3,03917
Nov-17-2019 3,0561,130
Nov-16-2019 4,186-826
Nov-15-2019 3,360-237
Nov-14-2019 3,123502

Advertisement

ngacn.cc 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.


ngacn.cc 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.


Whois Server Version 2.0

Domain names can now be registered with many different competing registrars.
Go to http://registrar.verisign-grs.com/whois/ for detailed information.

Domain Name: NGACN.CC
Domain ID: 89910463
WHOIS Server: whois.paycenter.com.cn
Referral URL: http://www.xinnet.com
Updated Date: 2014-04-01T12:46:13Z
Creation Date: 2008-04-17T12:46:11Z
Registry Expiry Date: 2019-04-17T12:46:11Z
Sponsoring Registrar: XIN NET TECHNOLOGY CORPORATION
Sponsoring Registrar IANA ID: 120
Domain Status: clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited
Name Server: DNS1.NGACN.CC
Name Server: DNS2.NGACN.CC
DNSSEC: unsigned
>>> Last update of WHOIS database: 2015-05-03T13:55:14Z

ngacn.cc server information

Servers Location

ngacn.cc desktop page speed rank

Last tested: 2015-05-21


Desktop Speed Medium
66/100

ngacn.cc Desktop Speed Test Quick Summary


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

Your page has 16 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:

http://img4.nga.178.com/common_res/js_commonLib.js?120846
http://img4.nga.178.com/common_res/js_bbs_adslist.js?120403
http://market.178.com/178nga/26.js
http://img4.nga.178.com/common_res/js_adscommon.js?120438
http://img4.nga.178.com/common_res/js_md5.js?140333
http://img4.nga.178.com/common_res/js_commonui.js?1101698
http://img4.nga.178.com/ngabbs/nga_classic/js_default.js?111270
http://img4.nga.178.com/common_res/js_bbscode_core.js?120484
http://img4.nga.178.com/ngabbs/nga_classic/js_bbscode_smiles.js?120482
http://img4.nga.178.com/common_res/js_postfunc_v2.js?140733
http://img4.nga.178.com/common_res/js_mainMenu.js?110855
http://img4.nga.178.com/ngabbs/nga_classic/js_customBg.js?111090
http://market.178.com/A/33262824097.js
http://w.cnzz.com/c.php?id=30043604
http://w.cnzz.com/c.php?id=30039253

Use asynchronous versions of the following scripts:

http://www.google-analytics.com/ga.js

Optimize CSS Delivery of the following:

http://img4.nga.178.com/ngabbs/nga_classic/css_default.css?111080
http://img4.nga.178.com/common_res/css_tooltip.css?131026

priority - 13 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 126.9KiB (66% reduction).

Compressing http://img4.nga.178.com/common_res/js_commonui.js?1101698 could save 102.8KiB (67% reduction).
Compressing http://img4.nga.178.com/common_res/js_bbs_adslist.js?120403 could save 7.8KiB (64% reduction).
Compressing http://w.cnzz.com/c.php?id=30039253 could save 6.5KiB (65% reduction).
Compressing http://w.cnzz.com/c.php?id=30043604 could save 6.5KiB (65% reduction).
Compressing http://c.cnzz.com/core.php?web_id=30043604&t=q could save 1.2KiB (47% reduction).
Compressing http://c.cnzz.com/core.php?web_id=30039253&t=q could save 1.2KiB (46% reduction).
Compressing http://market.178.com/A/33262824097.js could save 1KiB (57% reduction).

priority - 7 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 67KiB (27% reduction).

Minifying http://img4.nga.178.com/common_res/js_commonui.js?1101698 could save 34.6KiB (23% reduction).
Minifying http://img4.nga.178.com/ngabbs/nga_classic/js_default.js?111270 could save 6.6KiB (38% reduction) after compression.
Minifying http://img4.nga.178.com/common_res/js_bbs_adslist.js?120403 could save 6KiB (49% reduction).
Minifying http://img4.nga.178.com/common_res/js_commonLib.js?120846 could save 5.1KiB (45% reduction) after compression.
Minifying http://img4.nga.178.com/common_res/js_postfunc_v2.js?140733 could save 5KiB (29% reduction) after compression.
Minifying http://img4.nga.178.com/common_res/js_bbscode_core.js?120484 could save 3.7KiB (17% reduction) after compression.
Minifying http://img4.nga.178.com/ngabbs/nga_classic/js_bbscode_smiles.js?120482 could save 2KiB (21% reduction) after compression.
Minifying http://img4.nga.178.com/common_res/js_md5.js?140333 could save 1.4KiB (41% reduction) after compression.
Minifying http://img4.nga.178.com/common_res/js_mainMenu.js?110855 could save 1.1KiB (24% reduction) after compression.
Minifying http://img4.nga.178.com/common_res/js_adscommon.js?120438 could save 852B (26% reduction) after compression.
Minifying http://market.178.com/A/33262824097.js could save 700B (38% 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://market.178.com/178nga/26.js (5 minutes)
http://market.178.com/A/33262824097.js (5 minutes)
http://market.178.com/fodder/201505/6ba4a23fa286ab8cf41ba99f2024704d.swf (5 minutes)
http://c.cnzz.com/core.php?web_id=30039253&t=q (15 minutes)
http://c.cnzz.com/core.php?web_id=30043604&t=q (15 minutes)
http://w.cnzz.com/c.php?id=30039253 (90 minutes)
http://w.cnzz.com/c.php?id=30043604 (90 minutes)
http://www.google-analytics.com/ga.js (2 hours)

priority - 2 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 64% of the final above-the-fold content could be rendered with the full HTML response.

priority - 1 Optimize images

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

Optimize the following images to reduce their size by 11.8KiB (8% reduction).

Losslessly compressing http://img4.nga.178.com/ngabbs/nga_classic/logoshadow6.png could save 3.6KiB (33% reduction).
Losslessly compressing http://img0.178.com/wow/201411/209259899170/209259930313.gif could save 1.1KiB (63% reduction).
Losslessly compressing http://img4.nga.178.com/ngabbs/nga_classic/f/240.png could save 1.1KiB (27% reduction).
Losslessly compressing http://img4.nga.178.com/ngabbs/nga_classic/f/390.png could save 1KiB (45% reduction).
Losslessly compressing http://cimg.178.com/nga/s/zt/20140701/b.gif could save 1,009B (92% reduction).
Losslessly compressing http://img4.nga.178.com/ngabbs/nga_classic/f/-46468.png could save 960B (43% reduction).
Losslessly compressing http://img3.178.com/wow/201505/226014906484/226014925240.jpg could save 936B (2% reduction).
Losslessly compressing http://img4.nga.178.com/ngabbs/nga_classic/f/388.png could save 851B (44% reduction).
Losslessly compressing http://img5.178.com/ngacn/201505/226173760803/226187915869.jpg could save 707B (4% reduction).
Losslessly compressing http://img2.178.com/wow/201505/225914551994/225941229862.jpg could save 702B (3% 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 2.1KiB (21% reduction).

Minifying http://img4.nga.178.com/ngabbs/nga_classic/css_default.css?111080 could save 2.1KiB (21% reduction) after compression.

ngacn.cc Desktop Resources

Total Resources124
Number of Hosts18
Static Resources117
JavaScript Resources19
CSS Resources2

ngacn.cc Desktop Resource Breakdown

ngacn.cc mobile page speed rank

Last tested: 2015-05-21


Mobile Speed Bad
46/100

ngacn.cc Mobile Speed Test Quick Summary


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

Your page has 16 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:

http://img4.nga.178.com/common_res/js_commonLib.js?120846
http://img4.nga.178.com/common_res/js_bbs_adslist.js?120403
http://market.178.com/178nga/26.js
http://img4.nga.178.com/common_res/js_adscommon.js?120438
http://img4.nga.178.com/common_res/js_md5.js?140333
http://img4.nga.178.com/common_res/js_commonui.js?1101698
http://img4.nga.178.com/ngabbs/nga_classic/js_default.js?111270
http://img4.nga.178.com/common_res/js_bbscode_core.js?120484
http://img4.nga.178.com/ngabbs/nga_classic/js_bbscode_smiles.js?120482
http://img4.nga.178.com/common_res/js_postfunc_v2.js?140733
http://img4.nga.178.com/common_res/js_mainMenu.js?110855
http://img4.nga.178.com/ngabbs/nga_classic/js_customBg.js?111090
http://market.178.com/A/33262824097.js
http://w.cnzz.com/c.php?id=30043604
http://w.cnzz.com/c.php?id=30039253

Use asynchronous versions of the following scripts:

http://www.google-analytics.com/ga.js

Optimize CSS Delivery of the following:

http://img4.nga.178.com/ngabbs/nga_classic/css_default.css?111080
http://img4.nga.178.com/common_res/css_tooltip.css?131026

priority - 13 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 126.9KiB (66% reduction).

Compressing http://img4.nga.178.com/common_res/js_commonui.js?1101698 could save 102.8KiB (67% reduction).
Compressing http://img4.nga.178.com/common_res/js_bbs_adslist.js?120403 could save 7.8KiB (64% reduction).
Compressing http://w.cnzz.com/c.php?id=30039253 could save 6.5KiB (65% reduction).
Compressing http://w.cnzz.com/c.php?id=30043604 could save 6.5KiB (65% reduction).
Compressing http://c.cnzz.com/core.php?web_id=30043604&t=q could save 1.2KiB (47% reduction).
Compressing http://c.cnzz.com/core.php?web_id=30039253&t=q could save 1.2KiB (46% reduction).
Compressing http://market.178.com/A/33262824097.js could save 1KiB (57% 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 11% of the final above-the-fold content could be rendered with the full HTML response.

priority - 7 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 67KiB (27% reduction).

Minifying http://img4.nga.178.com/common_res/js_commonui.js?1101698 could save 34.6KiB (23% reduction).
Minifying http://img4.nga.178.com/ngabbs/nga_classic/js_default.js?111270 could save 6.6KiB (38% reduction) after compression.
Minifying http://img4.nga.178.com/common_res/js_bbs_adslist.js?120403 could save 6KiB (49% reduction).
Minifying http://img4.nga.178.com/common_res/js_commonLib.js?120846 could save 5.1KiB (45% reduction) after compression.
Minifying http://img4.nga.178.com/common_res/js_postfunc_v2.js?140733 could save 5KiB (29% reduction) after compression.
Minifying http://img4.nga.178.com/common_res/js_bbscode_core.js?120484 could save 3.7KiB (17% reduction) after compression.
Minifying http://img4.nga.178.com/ngabbs/nga_classic/js_bbscode_smiles.js?120482 could save 2KiB (21% reduction) after compression.
Minifying http://img4.nga.178.com/common_res/js_md5.js?140333 could save 1.4KiB (41% reduction) after compression.
Minifying http://img4.nga.178.com/common_res/js_mainMenu.js?110855 could save 1.1KiB (24% reduction) after compression.
Minifying http://img4.nga.178.com/common_res/js_adscommon.js?120438 could save 852B (26% reduction) after compression.
Minifying http://market.178.com/A/33262824097.js could save 700B (38% reduction).

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:

http://market.178.com/178nga/26.js (5 minutes)
http://market.178.com/A/33262824097.js (5 minutes)
http://c.cnzz.com/core.php?web_id=30039253&t=q (15 minutes)
http://c.cnzz.com/core.php?web_id=30043604&t=q (15 minutes)
http://w.cnzz.com/c.php?id=30039253 (90 minutes)
http://w.cnzz.com/c.php?id=30043604 (90 minutes)
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 3.8KiB (37% reduction).

Losslessly compressing http://img4.nga.178.com/ngabbs/nga_classic/f/240.png could save 1.1KiB (27% reduction).
Losslessly compressing http://img4.nga.178.com/ngabbs/nga_classic/f/390.png could save 1KiB (45% reduction).
Losslessly compressing http://img4.nga.178.com/ngabbs/nga_classic/f/-46468.png could save 960B (43% reduction).
Losslessly compressing http://img4.nga.178.com/ngabbs/nga_classic/f/388.png could save 851B (44% 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 2.1KiB (21% reduction).

Minifying http://img4.nga.178.com/ngabbs/nga_classic/css_default.css?111080 could save 2.1KiB (21% reduction) after compression.

ngacn.cc Mobile Resources

Total Resources110
Number of Hosts12
Static Resources102
JavaScript Resources19
CSS Resources2

ngacn.cc Mobile Resource Breakdown

ngacn.cc mobile page usability

Last tested: 2015-05-21


Mobile Usability Good
89/100

ngacn.cc Mobile Usability Test Quick Summary


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=525 will allow your page to adapt for devices of various widths. This may require additional work to adapt your styling for smaller screens.

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="/thread.php?fid=182">魔法圣堂</a> and 3 others are close to other tap targets.

The tap target <a href="http://www.178…ion/index.html">关于178</a> and 8 others are close to other tap targets.
The tap target <a href="http://app.178.com" class="white">下载论坛移动客户端</a> is close to 1 other tap targets.

The tap target <a href="javascript:void(0)" class="white">X</a> is close to 1 other tap targets.

ngacn.cc Mobile Resources

Total Resources110
Number of Hosts12
Static Resources102
JavaScript Resources19
CSS Resources2

ngacn.cc Mobile Resource Breakdown

ngacn.cc similar domains

Similar domains:
www.ngacn.com
www.ngacn.net
www.ngacn.org
www.ngacn.info
www.ngacn.biz
www.ngacn.us
www.ngacn.mobi
www.gacn.cc
www.ngacn.cc
www.bgacn.cc
www.nbgacn.cc
www.bngacn.cc
www.hgacn.cc
www.nhgacn.cc
www.hngacn.cc
www.jgacn.cc
www.njgacn.cc
www.jngacn.cc
www.mgacn.cc
www.nmgacn.cc
www.mngacn.cc
www.nacn.cc
www.nfacn.cc
www.ngfacn.cc
www.nfgacn.cc
www.nvacn.cc
www.ngvacn.cc
www.nvgacn.cc
www.ntacn.cc
www.ngtacn.cc
www.ntgacn.cc
www.nbacn.cc
www.ngbacn.cc
www.nyacn.cc
www.ngyacn.cc
www.nygacn.cc
www.nhacn.cc
www.nghacn.cc
www.ngcn.cc
www.ngqcn.cc
www.ngaqcn.cc
www.ngqacn.cc
www.ngwcn.cc
www.ngawcn.cc
www.ngwacn.cc
www.ngscn.cc
www.ngascn.cc
www.ngsacn.cc
www.ngzcn.cc
www.ngazcn.cc
www.ngzacn.cc
www.ngan.cc
www.ngaxn.cc
www.ngacxn.cc
www.ngaxcn.cc
www.ngadn.cc
www.ngacdn.cc
www.ngadcn.cc
www.ngafn.cc
www.ngacfn.cc
www.ngafcn.cc
www.ngavn.cc
www.ngacvn.cc
www.ngavcn.cc
www.ngac.cc
www.ngacb.cc
www.ngacnb.cc
www.ngacbn.cc
www.ngach.cc
www.ngacnh.cc
www.ngachn.cc
www.ngacj.cc
www.ngacnj.cc
www.ngacjn.cc
www.ngacm.cc
www.ngacnm.cc
www.ngacmn.cc

ngacn.cc 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.


ngacn.cc 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.