16FAN.COM 十六番_旅行者社区 - 十六番


16fan.com website information.

16fan.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.

Following name servers are specified for 16fan.com domain:

  • ns4.dnsv4.com
  • ns3.dnsv4.com

and probably website 16fan.com is hosted by AUTOMATTIC - Automattic, Inc, US web hosting company. Check the complete list of other most popular websites hosted by AUTOMATTIC - Automattic, Inc, US hosting company.

According to Alexa traffic rank the highest website 16fan.com position was 10384 (in the world). The lowest Alexa rank position was 722341. Now website 16fan.com ranked in Alexa database as number 327810 (in the world).

Website 16fan.com Desktop speed measurement score (81/100) is better than the results of 71.91% of other sites and shows that the page is performing great on desktop computers.

16fan.com 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 16fan.com (72/100) is better than the results of 79.79% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Apr-16-2024 327,810-61
Apr-15-2024 327,749-771
Apr-14-2024 326,978-6,681
Apr-13-2024 320,2971,214
Apr-12-2024 321,51128
Apr-11-2024 321,5391,378
Apr-10-2024 322,9176,791

Advertisement

16fan.com 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.



16fan.com 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.


Domain Name: 16FAN.COM
Registry Domain ID: 1161419720_DOMAIN_COM-VRSN
Registrar WHOIS Server: grs-whois.hichina.com
Registrar URL: http://www.net.cn
Updated Date: 2021-04-08T05:56:42Z
Creation Date: 2007-08-17T10:41:41Z
Registry Expiry Date: 2023-08-17T10:41:41Z
Registrar: Alibaba Cloud Computing (Beijing) Co., Ltd.
Registrar IANA ID: 420
Registrar Abuse Contact Email: DomainAbuse@service.aliyun.com
Registrar Abuse Contact Phone: +86.95187
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: NS3.DNSV4.COM
Name Server: NS4.DNSV4.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-04-25T07:41:08Z

16fan.com server information

Servers Location

IP Address
218.93.127.94
Country
China
Region
Jiangsu
City
Changzhou

16fan.com desktop page speed rank

Last tested: 2019-12-06


Desktop Speed Medium
81/100

16fan.com Desktop Speed Test Quick Summary


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

Your page has 6 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://guide.16fan.com/common/js/jquery-d76c6fa034.min.js
http://guide.16fan.com/common/js/v2/pre-common-850a5b28d8.min.js
https://api.map.baidu.com/location/ip?ak=8B39cTPQc…Ej7c&callback=locateIp
http://guide.16fan.com/common/js/v2/common-736e8de3b8.min.js
http://guide.16fan.com/common/js/v2/loadjs-common-5f915cca36.min.js
http://guide.16fan.com/dist/www-index-bce04edd87.min.js

Optimize CSS Delivery of the following:

http://guide.16fan.com/common/css/v2/common-66c3a2d92a.min.css
http://guide.16fan.com/common/css/v2/global-d2a657d371.min.css
http://guide.16fan.com/common/css/v2/index-d9c08f0767.min.css
http://guide.16fan.com/common/js/v2/theme/default/layer.css?v=3.1.1

priority - 8 Optimize images

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

Optimize the following images to reduce their size by 76.8KiB (55% reduction).

Compressing and resizing http://icon.16fan.com/1548936_1575640228.jpg?imageView2/0/w/120/h/120 could save 26.7KiB (93% reduction).
Compressing and resizing http://icon.16fan.com/988865_1548990490.jpg?imageView2/0/w/120/h/120 could save 24.2KiB (93% reduction).
Compressing and resizing http://icon.16fan.com/882786_1548945564.jpg?imageView2/0/w/120/h/120 could save 4.5KiB (89% reduction).
Compressing http://guide.16fan.com/common/css/v2/sprite/sprite-common.png could save 3.9KiB (18% reduction).
Compressing and resizing http://guide.16fan.com/common/images/footer.png could save 3.5KiB (40% reduction).
Compressing and resizing http://icon.16fan.com/1527483_1574148856.jpg?imageView2/0/w/120/h/120 could save 2.7KiB (84% reduction).
Compressing http://guide.16fan.com/common/images/weixin.png could save 1.5KiB (15% reduction).
Compressing and resizing http://guide.16fan.com/common/images/Filing.png could save 1.5KiB (64% reduction).
Compressing and resizing http://icon.16fan.com/no_avatar.jpg?imageView2/0/w/120/h/120 could save 1.3KiB (87% reduction).
Compressing and resizing http://s.16fan.com/attachments/static/201908/06/15650828039934e.png could save 1.3KiB (46% reduction).
Compressing http://guide.16fan.com/common/images/topbar160.png could save 1.2KiB (12% reduction).
Compressing and resizing http://s.16fan.com/attachments/static/201908/06/156508277088640e.png could save 1KiB (49% reduction).
Compressing and resizing http://s.16fan.com/attachments/static/201908/06/156508257872865e.png could save 944B (49% reduction).
Compressing http://guide.16fan.com/common/css/v2/sprite/index-sprite.png could save 764B (11% reduction).
Compressing and resizing http://s.16fan.com/attachments/static/201904/10/15…707700185base64.jpg-36 could save 571B (56% reduction).
Compressing and resizing http://s.16fan.com/attachments/static/201811/28/15…225115500base64.jpg-36 could save 465B (54% reduction).
Compressing and resizing http://s.16fan.com/attachments/static/201811/29/15…746982385base64.jpg-36 could save 315B (46% reduction).
Compressing http://guide.16fan.com/common/css/v2/logo.png could save 275B (12% reduction).
Compressing http://guide.16fan.com/common/images/medal/levelcolor1.png could save 119B (14% reduction).

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 20% of the final above-the-fold content could be rendered with the full HTML response.
Click to see the screenshot with only the HTML response:

priority - 0 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://www.google-analytics.com/analytics.js (2 hours)

16fan.com Desktop Resources

Total Resources59
Number of Hosts10
Static Resources51
JavaScript Resources9
CSS Resources4

16fan.com Desktop Resource Breakdown

16fan.com mobile page speed rank

Last tested: 2017-12-04


Mobile Speed Medium
72/100

16fan.com Mobile Speed Test Quick Summary


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

Your page has 2 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://guide.16fan.com/common/js/jquery-3.1.1.min.js
http://guide.16fan.com/common/js/v2/pre-common.min.js

Optimize CSS Delivery of the following:

http://guide.16fan.com/common/css/mobile-homepage_v170803.min.css
http://guide.16fan.com/common/css/mobile-common_v171116.min.css
http://guide.16fan.com/common/dep/PhotoSwipe/photoswipe.min.css
http://guide.16fan.com/common/dep/PhotoSwipe/defau…n/default-skin.min.css

priority - 8 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://www.google-analytics.com/analytics.js (2 hours)
http://guide.16fan.com/common/css/mobile-common_v171116.min.css (12 hours)
http://guide.16fan.com/common/css/mobile-homepage_v170803.min.css (12 hours)
http://guide.16fan.com/common/dep/PhotoSwipe/defau…n/default-skin.min.css (12 hours)
http://guide.16fan.com/common/dep/PhotoSwipe/photoswipe-ui-default.min.js (12 hours)
http://guide.16fan.com/common/dep/PhotoSwipe/photoswipe.min.css (12 hours)
http://guide.16fan.com/common/dep/PhotoSwipe/photoswipe.min.js (12 hours)
http://guide.16fan.com/common/dep/iscroll/iscroll.min.js (12 hours)
http://guide.16fan.com/common/js/v2/jquery.lazyload-1.9.7.min.js (12 hours)
http://guide.16fan.com/common/js/v2/loadjs-mobile_v171116.min.js (12 hours)
http://guide.16fan.com/common/js/v2/pre-common.min.js (12 hours)
http://guide.16fan.com/themes/mobile/js/find_homepage_v171116.min.js (12 hours)

priority - 4 Reduce server response time

In our test, your server responded in 0.47 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 - 1 Optimize images

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

Optimize the following images to reduce their size by 11.7KiB (31% reduction).

Compressing http://guide.16fan.com/themes/mobile/images/mobile.png could save 2.7KiB (44% reduction).
Compressing http://guide.16fan.com//themes/mobile/images/wb_iphone.png could save 2.7KiB (91% reduction).
Compressing http://bbs.16fan.com/uc_server/data/avatar/000/99/93/03_avatar_middle.jpg could save 1.5KiB (25% reduction).
Compressing http://bbs.16fan.com/uc_server/data/avatar/001/06/23/41_avatar_middle.jpg could save 1.3KiB (29% reduction).
Compressing http://bbs.16fan.com/uc_server/data/avatar/000/27/53/55_avatar_middle.jpg could save 1.1KiB (19% reduction).
Compressing http://bbs.16fan.com/uc_server/data/avatar/000/24/07/55_avatar_middle.jpg could save 1.1KiB (25% reduction).
Compressing http://bbs.16fan.com/uc_server/data/avatar/000/94/21/38_avatar_middle.jpg could save 723B (27% reduction).
Compressing http://guide.16fan.com/common/css/v2/sprite/find_homepage@3x.png could save 713B (13% 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 2.2KiB (15% reduction).

Minifying http://www.16fan.com/ could save 2.2KiB (15% reduction) after compression.

16fan.com Mobile Resources

Total Resources78
Number of Hosts6
Static Resources50
JavaScript Resources8
CSS Resources4

16fan.com Mobile Resource Breakdown

16fan.com mobile page usability

Last tested: 2017-12-04


Mobile Usability Good
99/100

16fan.com 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 <a href="http://www.16fan.com?cid=5">海岛游</a> and 1 others are close to other tap targets.

The tap target <div class="clear"></div> is close to 1 other tap targets.

The tap target <a href="http://wenda.1…on/365163.html" class="u-medal u-medal-article-name"></a> and 27 others are close to other tap targets.

16fan.com similar domains

Similar domains:
www.16fan.com
www.16fan.net
www.16fan.org
www.16fan.info
www.16fan.biz
www.16fan.us
www.16fan.mobi
www.6fan.com
www.16fan.com
www.1fan.com
www.16an.com
www.16can.com
www.16fcan.com
www.16cfan.com
www.16dan.com
www.16fdan.com
www.16dfan.com
www.16ran.com
www.16fran.com
www.16rfan.com
www.16tan.com
www.16ftan.com
www.16tfan.com
www.16gan.com
www.16fgan.com
www.16gfan.com
www.16van.com
www.16fvan.com
www.16vfan.com
www.16fn.com
www.16fqn.com
www.16faqn.com
www.16fqan.com
www.16fwn.com
www.16fawn.com
www.16fwan.com
www.16fsn.com
www.16fasn.com
www.16fsan.com
www.16fzn.com
www.16fazn.com
www.16fzan.com
www.16fa.com
www.16fab.com
www.16fanb.com
www.16fabn.com
www.16fah.com
www.16fanh.com
www.16fahn.com
www.16faj.com
www.16fanj.com
www.16fajn.com
www.16fam.com
www.16fanm.com
www.16famn.com
www.16fan.con

16fan.com 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.


16fan.com 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.