7.7 sec in total
1.2 sec
5.7 sec
816 ms
Visit tripitaka.cbeta.org now to see the best up-to-date Tripitaka CBETA content for China and also check out these interesting facts you probably never knew about tripitaka.cbeta.org
Visit tripitaka.cbeta.orgWe analyzed Tripitaka.cbeta.org page load time and found that the first response time was 1.2 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
tripitaka.cbeta.org performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value2.8 s
84/100
25%
Value5.5 s
54/100
10%
Value1,340 ms
17/100
30%
Value0.001
100/100
15%
Value11.3 s
19/100
10%
1240 ms
1048 ms
1109 ms
39 ms
46 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 34% of them (32 requests) were addressed to the original Tripitaka.cbeta.org, 9% (9 requests) were made to Google.com and 8% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 140.1 kB (30%)
461.7 kB
321.6 kB
In fact, the total size of Tripitaka.cbeta.org main page is 461.7 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. 65% of websites need less resources to load. Images take 242.8 kB which makes up the majority of the site volume.
Potential reduce by 37.6 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 37.6 kB or 75% of the original size.
Potential reduce by 7.5 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. Tripitaka CBETA images are well optimized though.
Potential reduce by 51.0 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.0 kB or 45% of the original size.
Potential reduce by 44.1 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. Tripitaka.cbeta.org needs all CSS files to be minified and compressed as it can save up to 44.1 kB or 80% of the original size.
Number of requests can be reduced by 52 (58%)
90
38
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tripitaka 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 32 to 1 for JavaScripts and as a result speed up the page load time.
tripitaka.cbeta.org
1240 ms
css_0a507ad5d2851338feed89f6d1ac864a.css
1048 ms
js_0d4575c65077c3a5c654e0bce3a91d83.js
1109 ms
jsapi
39 ms
t13n
46 ms
show_ads.js
38 ms
all.js
363 ms
google_plus_widget.js
351 ms
t13n
90 ms
brand
116 ms
google_plus_widget.js
245 ms
ga.js
90 ms
arrow4.gif
196 ms
fill_top.png
159 ms
fill_top_left.png
158 ms
fill_top_right.png
163 ms
rotate.php
486 ms
smlogo.gif
160 ms
paypal.gif
173 ms
donation.gif
163 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
197 ms
diigo.png
452 ms
google.png
455 ms
yahoo.png
450 ms
funp.png
464 ms
hemi.png
467 ms
plurk.png
468 ms
powered-blue-80x15.png
468 ms
by-nc-sa.png
468 ms
107 ms
__utm.gif
28 ms
transliteration.css
32 ms
transliteration.I.js
54 ms
192 ms
fill_left.png
170 ms
fill_right.png
169 ms
_sidebarimg.png
169 ms
fill_block.png
182 ms
cb-gad-02.gif
401 ms
ca-pub-2756763990045438.js
518 ms
zrt_lookup.html
609 ms
show_ads_impl.js
801 ms
google_custom_search_watermark.gif
525 ms
icon_01_48.png
279 ms
icon_07_48.png
280 ms
check.png
280 ms
inputtools.js
350 ms
524 ms
wp-is-back.png
272 ms
icon_20_48.png
223 ms
icon_14_48.png
224 ms
login-bg.png
484 ms
xd_arbiter.php
480 ms
xd_arbiter.php
795 ms
all.js
392 ms
widgets.js
387 ms
plusone.js
582 ms
_brand.png
112 ms
google_custom_search_watermark.gif
62 ms
like.php
308 ms
share_button.php
296 ms
ads
448 ms
css_441533d6054d3417f454b7768c0a4c65.css
220 ms
button.65b4bc8f0d6592fdc51d322b3f197660.js
398 ms
like.php
203 ms
xd_arbiter.php
293 ms
6kMqU_fzmnN.js
1260 ms
LVx-xkvaJ0b.png
1271 ms
6kMqU_fzmnN.js
1611 ms
osd.js
283 ms
cb=gapi.loaded_0
258 ms
cb=gapi.loaded_1
393 ms
fastbutton
415 ms
ads
414 ms
0_jFwqgyZG.jpg
786 ms
a.gif
432 ms
bcs0
432 ms
creative_add_on.js
596 ms
cb=gapi.loaded_0
270 ms
cb=gapi.loaded_1
170 ms
postmessageRelay
259 ms
creative_add_on.js
309 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
300 ms
bcs0
151 ms
0_NdQE4OBS.jpg
763 ms
a.gif
149 ms
tweet_button.64a917b4a230f163048902c783e1530f.en.html
145 ms
surly.js
427 ms
3193398744-postmessagerelay.js
402 ms
rpc:shindig_random.js
79 ms
jot
532 ms
surly.js
468 ms
cb=gapi.loaded_0
136 ms
ba.html
132 ms
4.gif
142 ms
tripitaka.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
Image elements do not have [alt] attributes
Form elements do not have associated labels
tripitaka.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
tripitaka.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
Image elements do not have [alt] attributes
JA
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tripitaka.cbeta.org 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 Tripitaka.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.
tripitaka.cbeta.org
Open Graph description is not detected on the main page of Tripitaka 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: