2.8 sec in total
627 ms
1.9 sec
251 ms
Welcome to cbeta.org homepage info - get ready to check CBETA best content for China right away, or after learning these important things about cbeta.org
Visit cbeta.orgWe analyzed Cbeta.org page load time and found that the first response time was 627 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
cbeta.org performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value12.5 s
0/100
25%
Value12.0 s
4/100
10%
Value890 ms
32/100
30%
Value0.001
100/100
15%
Value16.0 s
6/100
10%
627 ms
71 ms
200 ms
36 ms
67 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 42% of them (42 requests) were addressed to the original Cbeta.org, 8% (8 requests) were made to Google.com and 7% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (627 ms) belongs to the original domain Cbeta.org.
Page size can be reduced by 144.9 kB (51%)
283.3 kB
138.4 kB
In fact, the total size of Cbeta.org main page is 283.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. 70% of websites need less resources to load. Javascripts take 98.8 kB which makes up the majority of the site volume.
Potential reduce by 45.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 45.8 kB or 76% of the original size.
Potential reduce by 7.8 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. CBETA images are well optimized though.
Potential reduce by 51.6 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 51.6 kB or 52% of the original size.
Potential reduce by 39.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. Cbeta.org needs all CSS files to be minified and compressed as it can save up to 39.7 kB or 80% of the original size.
Number of requests can be reduced by 56 (60%)
94
38
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CBETA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
cbeta.org
627 ms
css_93a7fc42aef14d7949156e73c0c49750.css
71 ms
js_de5758cce77e120fa924c1d60ab7df93.js
200 ms
jsapi
36 ms
t13n
67 ms
brand
26 ms
jinglu_search.js
152 ms
show_ads.js
6 ms
all.js
150 ms
brand
72 ms
t13n
51 ms
ga.js
29 ms
42 ms
arrow4.gif
168 ms
fill_top.png
68 ms
fill_top_left.png
73 ms
fill_top_right.png
146 ms
rotate.php
373 ms
smlogo.gif
145 ms
donation.gif
145 ms
paypal.gif
166 ms
CBETA%E6%BC%A2%E6%96%87%E5%A4%A7%E8%97%8F%E7%B6%93%E6%89%8B%E6%A9%9F%E7%89%88%E7%B6%B2%E5%9D%80.png
145 ms
cd27_small.jpg
370 ms
new2.gif
312 ms
diigo.png
367 ms
google.png
370 ms
yahoo.png
370 ms
funp.png
370 ms
hemi.png
445 ms
plurk.png
447 ms
feed.png
448 ms
powered-blue-80x15.png
446 ms
by-nc-sa.png
444 ms
__utm.gif
11 ms
transliteration.css
9 ms
transliteration.I.js
33 ms
38 ms
menu-expanded.png
340 ms
menu-leaf.png
414 ms
fill_left.png
414 ms
fill_right.png
416 ms
_sidebarimg.png
414 ms
fill_block.png
413 ms
plusone.js
268 ms
more.png
386 ms
inputtools.js
75 ms
cb-gad-01.gif
425 ms
ca-pub-2756763990045438.js
200 ms
zrt_lookup.html
227 ms
show_ads_impl.js
151 ms
icon_06_48.png
404 ms
icon_01_48.png
433 ms
icon_19_48.png
351 ms
icon_20_48.png
361 ms
check.png
363 ms
icon_14_48.png
420 ms
login-bg.png
419 ms
253 ms
all.js
181 ms
widgets.js
104 ms
ping
224 ms
_brand.png
347 ms
nav-down.png
352 ms
menushadow.png
354 ms
xd_arbiter.php
183 ms
xd_arbiter.php
309 ms
ads
172 ms
google_custom_search_watermark.gif
74 ms
osd.js
54 ms
ads
247 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
98 ms
like.php
127 ms
cb=gapi.loaded_0
45 ms
cb=gapi.loaded_1
83 ms
fastbutton
164 ms
like.php
110 ms
share_button.php
116 ms
postmessageRelay
89 ms
vpc6VNjRPXV.js
310 ms
LVx-xkvaJ0b.png
319 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
17 ms
vpc6VNjRPXV.js
398 ms
cb=gapi.loaded_0
39 ms
cb=gapi.loaded_1
25 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
94 ms
api.js
28 ms
core:rpc:shindig.random:shindig.sha1.js
71 ms
2536007149-postmessagerelay.js
70 ms
css
67 ms
m_js_controller.js
50 ms
abg.js
49 ms
css_7812db96483ec8b70db246b2c1237504.css
70 ms
jot
109 ms
favicon
65 ms
nessie_icon_tiamat_white.png
24 ms
s
13 ms
googlelogo_color_112x36dp.png
65 ms
x_button_blue2.png
5 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
3 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
37 ms
cbeta.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
cbeta.org 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
Browser errors were logged to the console
cbeta.org 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
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
ZH
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cbeta.org can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Cbeta.org 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.
cbeta.org
Open Graph description is not detected on the main page of CBETA. 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: