16.2 sec in total
482 ms
15.2 sec
523 ms
Welcome to beatstage.com homepage info - get ready to check Beat Stage best content for China right away, or after learning these important things about beatstage.com
第一个开放式网页音乐游戏 BeatStage
Visit beatstage.comWe analyzed Beatstage.com page load time and found that the first response time was 482 ms and then it took 15.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
beatstage.com performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value6.6 s
8/100
25%
Value5.7 s
51/100
10%
Value100 ms
98/100
30%
Value0.014
100/100
15%
Value5.6 s
70/100
10%
482 ms
485 ms
258 ms
1934 ms
1995 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 11% of them (8 requests) were addressed to the original Beatstage.com, 36% (27 requests) were made to Bs-img.b0.upaiyun.com and 16% (12 requests) were made to Bs-cdn.b0.upaiyun.com. The less responsive or slowest element that took the longest time to load (11.8 sec) relates to the external source Bs-avatar.b0.upaiyun.com.
Page size can be reduced by 345.2 kB (52%)
661.3 kB
316.1 kB
In fact, the total size of Beatstage.com main page is 661.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 223.3 kB which makes up the majority of the site volume.
Potential reduce by 113.8 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 17.3 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 113.8 kB or 91% of the original size.
Potential reduce by 15.9 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Beat Stage images are well optimized though.
Potential reduce by 108.8 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 108.8 kB or 60% of the original size.
Potential reduce by 106.7 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Beatstage.com needs all CSS files to be minified and compressed as it can save up to 106.7 kB or 82% of the original size.
Number of requests can be reduced by 25 (36%)
69
44
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Beat Stage. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
beatstage.com
482 ms
www.beatstage.com
485 ms
www.beatstage.com
258 ms
jquery-1.10.2.min.js
1934 ms
common.min.js
1995 ms
bootstrap.min.css
3665 ms
beatstage.min.css
1825 ms
jquery.timeago.min.js
1857 ms
jquery.pjax.min.js
1812 ms
jquery.cookie.min.js
2077 ms
jquery.lazyload.min.js
2077 ms
bootstrap-alert.min.js
2177 ms
stat.php
2099 ms
317515f2b3f962dccbc67156609979c5
2509 ms
38554_20.jpg
2768 ms
10076_20.jpg
2799 ms
28129_20.jpg
11816 ms
455b982664a742abcc5e1bb55728ce88
2676 ms
5698aea4969dc993b32a64821bdf4b3f
2900 ms
02f32d0ad332ae46e275eb6bf3dbe09c
2769 ms
806259e1d94e900d0f40e98394dee7ed
2776 ms
2d6802d0e6585e87350d08f841c2101b
3927 ms
08b570a15f0c74ce9899ce832db282b8
2924 ms
btn_random.png
726 ms
logo.png
419 ms
glyphicons-halflings-regular.woff
2848 ms
ga.js
28 ms
stat.htm
169 ms
core.php
1491 ms
__utm.gif
27 ms
collect
57 ms
9.gif
1408 ms
DwMkevl6NIGVASs2ATZg.js
168 ms
getStats
283 ms
getNew10
474 ms
getTodayTop10
494 ms
getTagcloud
507 ms
getLiveScore
1503 ms
cover_284_m.jpg
2024 ms
cover_283_m.jpg
2023 ms
cover_277_m.jpg
2022 ms
cover_275_m.jpg
4049 ms
cover_274_m.jpg
2022 ms
cover_273_m.jpg
2025 ms
cover_272_m.jpg
2023 ms
cover_233_m.jpg
2024 ms
cover_226_m.jpg
2063 ms
cover_212_m.jpg
2025 ms
cover_170_m.jpg
2037 ms
cover_163_m.jpg
2038 ms
feedback-tab.png
3 ms
tab-left-dark-e89fceb89af232658b40362993385936.png
5 ms
cover_284_s.jpg
1589 ms
cover_283_s.jpg
1579 ms
cover_282_s.jpg
1577 ms
cover_281_s.jpg
1589 ms
cover_280_s.jpg
1592 ms
cover_279_s.jpg
1589 ms
cover_278_s.jpg
1590 ms
cover_277_s.jpg
1592 ms
cover_276_s.jpg
1600 ms
cover_275_s.jpg
1601 ms
cover_221_s.jpg
1838 ms
cover_233_s.jpg
1580 ms
cover_225_s.jpg
1584 ms
cover_119_s.jpg
1590 ms
cover_61_s.jpg
1591 ms
app.gif
4699 ms
d239f423117906ad9e7af3b91cfc6604
450 ms
13347_20.jpg
560 ms
36438_20.png
533 ms
38303_20.jpg
599 ms
f73c68b96c60efe7dacb7e82f429b979
453 ms
cfcb9c76363cbd102a4c4b826b31efb8
431 ms
track.js
163 ms
beatstage.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
beatstage.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
beatstage.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Beatstage.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Beatstage.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
beatstage.com
Open Graph description is not detected on the main page of Beat Stage. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: