1.9 sec in total
380 ms
1.4 sec
129 ms
Click here to check amazing Buzzpark content for China. Otherwise, check out these important facts you probably never knew about buzzpark.cc
巴斯樂園目前有「遊戲擂台」和「神算」兩大娛樂頻道,每天都有新內容,提供網友不同的新體驗。另外還有經營「噗浪巴斯」這個在噗浪網站上的互動機器人,平時除了早安問候、午夜踩線之外,還有多項實用的互動功能喔。
Visit buzzpark.ccWe analyzed Buzzpark.cc page load time and found that the first response time was 380 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
buzzpark.cc performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value4.1 s
47/100
25%
Value4.3 s
76/100
10%
Value110 ms
98/100
30%
Value0
100/100
15%
Value5.8 s
67/100
10%
380 ms
49 ms
50 ms
5 ms
81 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Buzzpark.cc, 37% (18 requests) were made to Scontent.xx.fbcdn.net and 22% (11 requests) were made to Gravatar.com. The less responsive or slowest element that took the longest time to load (824 ms) relates to the external source Cdn1.buzzpark.cc.
Page size can be reduced by 90.9 kB (29%)
310.9 kB
219.9 kB
In fact, the total size of Buzzpark.cc main page is 310.9 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. 55% of websites need less resources to load. Images take 176.8 kB which makes up the majority of the site volume.
Potential reduce by 11.5 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 2.0 kB, which is 12% 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 11.5 kB or 69% of the original size.
Potential reduce by 16.6 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. Buzzpark images are well optimized though.
Potential reduce by 62.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 62.8 kB or 54% of the original size.
Number of requests can be reduced by 9 (19%)
48
39
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Buzzpark. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
buzzpark.cc
380 ms
prod_core.css
49 ms
prod_main.css
50 ms
jquery.min.js
5 ms
prod_main.js
81 ms
all.js
70 ms
797
104 ms
logo_b172x50.png
73 ms
beta.gif
76 ms
3.png
824 ms
start.gif
76 ms
173
44 ms
6562d78209ae4995c8974082aafec3cc
67 ms
100000076166174
67 ms
803
67 ms
961
68 ms
667
69 ms
337
68 ms
100000349952680
70 ms
96f55c4450c777f9e8a99c99d20d1ecd
69 ms
cf6584a9b4daf486765643b4021d9be9
69 ms
analytics.js
69 ms
21192835_1586901217998586_3538207447176414914_n.jpg
69 ms
1004656_610225952352647_368199479_n.jpg
76 ms
16195259_10206200216444550_8886653429015721161_n.jpg
81 ms
20621202_1797491130266101_7640594487170558135_n.jpg
79 ms
19553890_1945938138765385_3131858121968684219_n.jpg
78 ms
20621915_1858779197470551_7792477583752863713_n.jpg
76 ms
20638654_1465413466880288_7907552081739995099_n.jpg
77 ms
10365847_1027881247231332_4515437875957205087_n.jpg
78 ms
10340159_1296593143691404_1583810826464478291_n.jpg
81 ms
527349_405715232835459_518545959_n.jpg
79 ms
17904000_1697795936900725_980166640917315071_n.jpg
140 ms
UlIqmHJn-SK.gif
75 ms
16473485_10210368770608801_6743075709443935914_n.jpg
79 ms
85 ms
0sTQzbapM8j.js
46 ms
0sTQzbapM8j.js
62 ms
14440916_1098844773486267_5476896264235927175_n.jpg
54 ms
20258281_1905221636158334_6328248133206772408_n.jpg
52 ms
13445481_1202797336406876_2940468818556036156_n.jpg
59 ms
18582588_10203398556841415_9086869420348466473_n.jpg
57 ms
19554310_1681068375244495_7284157465425490294_n.jpg
57 ms
13010609_1255173577830623_498635928302211629_n.jpg
38 ms
collect
70 ms
like.php
128 ms
0sTQzbapM8j.js
7 ms
VYSWNx3-H66.js
16 ms
lH1ibRl5GKq.png
5 ms
buzzpark.cc accessibility score
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
buzzpark.cc 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
Issues were logged in the Issues panel in Chrome Devtools
buzzpark.cc SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
![]()
JA
![]()
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Buzzpark.cc can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Buzzpark.cc 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.
buzzpark.cc
Open Graph description is not detected on the main page of Buzzpark. 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: