BILIBILI.COM 哔哩哔哩弹幕视频网 - ( ゜- ゜)つロ 乾杯~ - bilibili


bilibili.com website information.

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

No name server records were found.

According to Alexa traffic rank the highest website bilibili.com position was 28 (in the world). The lowest Alexa rank position was 399. Now website bilibili.com ranked in Alexa database as number 67 (in the world).

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

bilibili.com Mobile usability score (99/100) is better than the results of 87.11% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of bilibili.com (45/100) is better than the results of 22.37% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Aug-20-2018 676
Aug-19-2018 734
Aug-18-2018 77-2
Aug-17-2018 752
Aug-16-2018 77-4
Aug-15-2018 73-9
Aug-14-2018 64-3

Advertisement

bilibili.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.


bilibili.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: BILIBILI.COM
Registry Domain ID: 133351793_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.name.com
Registrar URL: http://www.name.com
Updated Date: 2017-06-13T11:49:02Z
Creation Date: 2004-10-21T11:37:37Z
Registry Expiry Date: 2020-10-21T11:37:37Z
Registrar: Name.com, Inc.
Registrar IANA ID: 625
Registrar Abuse Contact Email: abuse@name.com
Registrar Abuse Contact Phone: 7202492374
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.HDSLB.NET
Name Server: NS2.HDSLB.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-07-22T18:50:59Z

bilibili.com server information

Servers Location

bilibili.com desktop page speed rank

Last tested: 2015-05-19


Desktop Speed Medium
70/100

bilibili.com Desktop Speed Test Quick Summary


priority - 19 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.bilibili.com/index/ding-count.json (3 seconds)
http://www.bilibili.com/index/ding.json (3 seconds)
http://www.bilibili.com/index/catalogy/1-3day.json (60 seconds)
http://www.bilibili.com/index/catalogy/13-3day.json (60 seconds)
http://www.bilibili.com/index/promote/12.json (60 seconds)
http://www.bilibili.com/index/promote/4.json (60 seconds)
http://www.bilibili.com/index/promote/5.json (60 seconds)
http://www.bilibili.com/html/ads-index.js (5 minutes)
http://www.bilibili.com/index/bangumi.json (5 minutes)
http://www.bilibili.com/index/promote.json (5 minutes)
http://www.bilibili.com/index/ranking-3day.json (5 minutes)
http://www.bilibili.com/index/slideshow.json (5 minutes)
http://www.bilibili.com/online.js (5 minutes)
http://static.hdslb.com/css/index.css (60 minutes)
http://static.hdslb.com/css/new_z2.css (60 minutes)
http://static.hdslb.com/js/base.core.v3.js (60 minutes)
http://static.hdslb.com/js/bfd.js?_=1432040421091 (60 minutes)
http://static.hdslb.com/js/page.core.js (60 minutes)
http://static.hdslb.com/js/page.index.v3.js?ver=3 (60 minutes)
http://tajs.qq.com/stats?sId=9156259&_=1432040421093 (60 minutes)
http://s11.cnzz.com/stat.php?id=2724999&web_id=2724999&_=1432040421092 (90 minutes)
http://static.hdslb.com/drawyoo/wallpaper/images/wallpapericon.png (8 hours)
http://static.hdslb.com/images/v2images/footerline.png (8 hours)
http://static.hdslb.com/images/v2images/footpic.gif (8 hours)
http://static.hdslb.com/images/v2images/icons_home.png (8 hours)
http://static.hdslb.com/images/v2images/loading.gif (8 hours)
http://static.hdslb.com/images/v2images/v_pg.png (8 hours)
http://static.hdslb.com/images/v3images/bodyline.png (8 hours)
http://static.hdslb.com/images/v3images/coverbg.png (8 hours)
http://static.hdslb.com/images/v3images/icons1.png (8 hours)
http://static.hdslb.com/images/v3images/icons2.png (8 hours)
http://static.hdslb.com/images/v3images/icons_v.png (8 hours)
http://static.hdslb.com/images/v3images/img_loading.png (8 hours)
http://static.hdslb.com/images/v3images/main_icons.png (8 hours)
http://static.hdslb.com/images/v3images/onlinepic.png (8 hours)
http://static.hdslb.com/images/v3images/refresh.png (8 hours)
http://static.hdslb.com/images/v3images/repeatline.png (8 hours)
http://static.hdslb.com/images/v3images/vrank.png (8 hours)

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

Your page has 7 blocking script resources and 3 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://static.hdslb.com/js/jquery.min.js
http://static.hdslb.com/js/jquery-ui.min.js
http://static.hdslb.com/js/base.core.v3.js
http://static.hdslb.com/js/page.core.js
http://static.hdslb.com/js/page.index.v3.js?ver=3
http://www.bilibili.com/html/ads-index.js
http://www.bilibili.com/online.js

Optimize CSS Delivery of the following:

http://static.hdslb.com/images/jquery-ui/custom/jquery-ui.css
http://static.hdslb.com/css/new_z2.css
http://static.hdslb.com/css/index.css

priority - 9 Optimize images

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

Optimize the following images to reduce their size by 90.1KiB (18% reduction).

Losslessly compressing http://i0.hdslb.com/u_user/1b66a353f7dc5bfc48443dfd01219346.jpg could save 28.2KiB (43% reduction).
Compressing and resizing http://i0.hdslb.com/320_180/video/59/59a5651019913e4e3d0004631d869231.jpg could save 9KiB (59% reduction).
Compressing and resizing http://i0.hdslb.com/320_180/video/53/53f2eb80ba70d42b39ffb8a2d8e1dcd0.jpg could save 8.9KiB (60% reduction).
Compressing and resizing http://i1.hdslb.com/320_180/video/4d/4d23b1f663b90617e98d8f3ff969f656.jpg could save 7.1KiB (59% reduction).
Compressing and resizing http://i2.hdslb.com/320_180/video/35/35dac5bd521e3bde85425b757cc384e6.jpg could save 5.3KiB (55% reduction).
Compressing and resizing http://i0.hdslb.com/320_180/video/90/9037fbcc04a949907f6296e95c0e9a08.jpg could save 4.2KiB (56% reduction).
Compressing and resizing http://i0.hdslb.com/320_180/video/1c/1c4d2d2b5bc3edecdf59c4802bc26702.jpg could save 4KiB (54% reduction).
Compressing and resizing http://i1.hdslb.com/320_180/video/e1/e16c028c76b8c661752f276b64656bf6.jpg could save 3.5KiB (53% reduction).
Losslessly compressing http://static.hdslb.com/images/v2images/v_pg.png could save 2.6KiB (96% reduction).
Losslessly compressing http://static.hdslb.com/images/v2images/footpic.gif could save 1.9KiB (25% reduction).
Losslessly compressing http://static.hdslb.com/images/v3images/icons1.png could save 1.8KiB (8% reduction).
Losslessly compressing http://static.hdslb.com/images/v2images/icons_home.png could save 1.2KiB (8% reduction).
Losslessly compressing http://static.hdslb.com/images/v3images/icons_v.png could save 1.1KiB (39% reduction).
Losslessly compressing http://i2.hdslb.com/u_user/8b129c78b09b4732fb42740e33a8e6d1.jpg could save 961B (2% reduction).
Losslessly compressing http://i2.hdslb.com/promote/c9c23db2f4c72610a736a9c89f14711c.jpg could save 947B (3% reduction).
Losslessly compressing http://static.hdslb.com/images/v2images/footerline.png could save 931B (91% reduction).
Losslessly compressing http://static.hdslb.com/images/header/2015_summer1.jpg could save 914B (2% reduction).
Losslessly compressing http://i2.hdslb.com/promote/13a4c95243f737b263b2c6630816669b.jpg could save 913B (2% reduction).
Losslessly compressing http://i1.hdslb.com/u_user/2ed2286fa338f195b1f25a746022a307.jpg could save 911B (3% reduction).
Losslessly compressing http://i2.hdslb.com/u_user/de7e1f051d7e0ac04b9c3e44be51fee5.jpg could save 911B (3% reduction).
Losslessly compressing http://i1.hdslb.com/promote/7454c6ca1c0ff4716206b372d32a837f.jpg could save 908B (5% reduction).
Losslessly compressing http://static.hdslb.com/images/v3images/repeatline.png could save 867B (86% reduction).
Losslessly compressing http://static.hdslb.com/images/v3images/coverbg.png could save 858B (84% reduction).
Losslessly compressing http://static.hdslb.com/ad-images/wx.jpg could save 825B (9% reduction).
Losslessly compressing http://static.hdslb.com/images/v3images/main_icons.png could save 821B (20% reduction).
Losslessly compressing http://static.hdslb.com/images/v3images/img_loading.png could save 802B (34% 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 48% of the final above-the-fold content could be rendered with the full HTML response.

priority - 1 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 9.9KiB (61% reduction).

Compressing http://s11.cnzz.com/stat.php?id=2724999&web_id=2724999&_=1432040421092 could save 6.5KiB (65% reduction).
Compressing http://tajs.qq.com/stats?sId=9156259&_=1432040421093 could save 3.4KiB (54% reduction).

priority - 1 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 9.4KiB (17% reduction).

Minifying http://static.hdslb.com/css/new_z2.css could save 7.9KiB (16% reduction) after compression.
Minifying http://static.hdslb.com/images/jquery-ui/custom/jquery-ui.css could save 1.5KiB (26% 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.6KiB (4% reduction).

Minifying http://static.hdslb.com/js/jquery-ui.min.js could save 1.6KiB (4% 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 515B (10% reduction).

Minifying http://www.bilibili.com/ could save 515B (10% reduction) after compression.

bilibili.com Desktop Resources

Total Resources85
Number of Hosts12
Static Resources78
JavaScript Resources22
CSS Resources3

bilibili.com Desktop Resource Breakdown

bilibili.com mobile page speed rank

Last tested: 2018-04-24


Mobile Speed Bad
45/100

bilibili.com Mobile Speed Test Quick Summary


priority - 69 Avoid landing page redirects

Your page has 4 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://bilibili.com/
http://www.bilibili.com/
https://www.bilibili.com/
https://m.bilibili.com/
https://m.bilibili.com/index.html

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

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

https://s1.hdslb.com/bfs/seed/log/report/log-reporter.js
https://static.hdslb.com/js/jquery.min.js
https://s1.hdslb.com/bfs/static/mult/js/cookies.js
https://static.hdslb.com/mobile/js/swipe.min.js
https://s1.hdslb.com/bfs/static/mult/vendor-670541350.js
https://s1.hdslb.com/bfs/static/mult/utils-670541350.js
https://s1.hdslb.com/bfs/static/mult/home-670541350.js
https://s1.hdslb.com/bfs/static/mult/app-670541350.js
https://at.alicdn.com/t/font_66virlr2p1jg7gb9.js
https://cdn.bootcss.com/fastclick/1.0.6/fastclick.min.js

Optimize CSS Delivery of the following:

https://s1.hdslb.com/bfs/static/mult/home-670541350.css

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 25% 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 - 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:

https://api.bilibili.com/nav (expiration not specified)
https://s1.hdslb.com/bfs/seed/log/report/5.efe18.function.chunk.js (10 minutes)
https://s1.hdslb.com/bfs/seed/log/report/log-reporter.js (10 minutes)
https://c.cnzz.com/core.php?web_id=2724999&t=z (15 minutes)
https://s11.cnzz.com/stat.php?id=2724999&web_id=2724999&async=1 (90 minutes)
https://static.hdslb.com/images/member/noface.gif (8 hours)

priority - 3 Reduce server response time

In our test, your server responded in 0.39 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 8.7KiB (37% reduction).

Compressing https://s1.hdslb.com/bfs/static/mult/images/ic_top.png could save 2.7KiB (42% reduction).
Compressing https://s1.hdslb.com/bfs/static/mult/images/bt.png could save 2.6KiB (37% reduction).
Compressing https://s1.hdslb.com/bfs/static/mult/images/remind.png could save 968B (62% reduction).
Compressing https://s1.hdslb.com/bfs/static/mult/images/close1.png could save 955B (74% reduction).
Compressing https://s1.hdslb.com/bfs/static/mult/images/TV-Play.png could save 840B (21% reduction).
Compressing https://s1.hdslb.com/bfs/static/mult/images/logo.png could save 719B (21% reduction).

priority - 1 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 8.2KiB (61% reduction).

Compressing https://s11.cnzz.com/stat.php?id=2724999&web_id=2724999&async=1 could save 7KiB (65% reduction).
Compressing https://c.cnzz.com/core.php?web_id=2724999&t=z could save 1.1KiB (46% reduction).

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 420B (29% reduction).

Minifying https://s1.hdslb.com/bfs/static/mult/js/cookies.js could save 420B (29% reduction) after compression.

bilibili.com Mobile Resources

Total Resources43
Number of Hosts19
Static Resources26
JavaScript Resources16
CSS Resources1

bilibili.com Mobile Resource Breakdown

bilibili.com mobile page usability

Last tested: 2018-04-24


Mobile Usability Good
99/100

bilibili.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 class="index__searchI…onent-topArea-">search</a> is close to 1 other tap targets.

The tap target <a class="index__mySpace…onent-topArea-">face</a> is close to 1 other tap targets.

The tap target <div class="index__openBtn…onent-openBtn-">App 内打开</div> is close to 1 other tap targets.

bilibili.com Mobile Resources

Total Resources43
Number of Hosts19
Static Resources26
JavaScript Resources16
CSS Resources1

bilibili.com Mobile Resource Breakdown

bilibili.com similar domains

Similar domains:
www.bilibili.com
www.bilibili.net
www.bilibili.org
www.bilibili.info
www.bilibili.biz
www.bilibili.us
www.bilibili.mobi
www.ilibili.com
www.bilibili.com
www.vilibili.com
www.bvilibili.com
www.vbilibili.com
www.gilibili.com
www.bgilibili.com
www.gbilibili.com
www.hilibili.com
www.bhilibili.com
www.hbilibili.com
www.nilibili.com
www.bnilibili.com
www.nbilibili.com
www.blibili.com
www.bulibili.com
www.biulibili.com
www.builibili.com
www.bjlibili.com
www.bijlibili.com
www.bjilibili.com
www.bklibili.com
www.biklibili.com
www.bkilibili.com
www.bolibili.com
www.biolibili.com
www.boilibili.com
www.biibili.com
www.bipibili.com
www.bilpibili.com
www.biplibili.com
www.bioibili.com
www.biloibili.com
www.bikibili.com
www.bilkibili.com
www.bilbili.com
www.bilubili.com
www.biliubili.com
www.biluibili.com
www.biljbili.com
www.bilijbili.com
www.biljibili.com
www.bilkbili.com
www.bilikbili.com
www.bilobili.com
www.biliobili.com
www.biliili.com
www.bilivili.com
www.bilibvili.com
www.bilivbili.com
www.biligili.com
www.bilibgili.com
www.biligbili.com
www.bilihili.com
www.bilibhili.com
www.bilihbili.com
www.bilinili.com
www.bilibnili.com
www.bilinbili.com
www.bilibli.com
www.bilibuli.com
www.bilibiuli.com
www.bilibuili.com
www.bilibjli.com
www.bilibijli.com
www.bilibjili.com
www.bilibkli.com
www.bilibikli.com
www.bilibkili.com
www.biliboli.com
www.bilibioli.com
www.biliboili.com
www.bilibii.com
www.bilibipi.com
www.bilibilpi.com
www.bilibipli.com
www.bilibioi.com
www.bilibiloi.com
www.bilibiki.com
www.bilibilki.com
www.bilibil.com
www.bilibilu.com
www.bilibiliu.com
www.bilibilui.com
www.bilibilj.com
www.bilibilij.com
www.bilibilji.com
www.bilibilk.com
www.bilibilik.com
www.bilibilo.com
www.bilibilio.com
www.bilibili.con

bilibili.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.


bilibili.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.