6.3 sec in total
82 ms
5.8 sec
466 ms
Click here to check amazing Kunzang content. Otherwise, check out these important facts you probably never knew about kunzang.org
Visit kunzang.orgWe analyzed Kunzang.org page load time and found that the first response time was 82 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
kunzang.org performance score
name
value
score
weighting
Value11.1 s
0/100
10%
Value16.5 s
0/100
25%
Value26.3 s
0/100
10%
Value1,550 ms
13/100
30%
Value0.135
80/100
15%
Value40.4 s
0/100
10%
82 ms
4751 ms
336 ms
16 ms
32 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 94% of them (115 requests) were addressed to the original Kunzang.org, 4% (5 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Kunzang.org.
Page size can be reduced by 249.5 kB (4%)
6.0 MB
5.7 MB
In fact, the total size of Kunzang.org main page is 6.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.4 MB which makes up the majority of the site volume.
Potential reduce by 184.0 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 184.0 kB or 85% of the original size.
Potential reduce by 65.4 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. Kunzang images are well optimized though.
Potential reduce by 63 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 17 B
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. Kunzang.org has all CSS files already compressed.
Number of requests can be reduced by 14 (13%)
112
98
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kunzang. 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 from 5 to 1 for CSS and as a result speed up the page load time.
kunzang.org
82 ms
kunzang.org
4751 ms
www.kunzang.org
336 ms
a5ff7.css
16 ms
dd6b7.css
32 ms
css
39 ms
fddd9.css
41 ms
44cab.js
72 ms
4a483.js
59 ms
19c2f.js
57 ms
3aa97.js
66 ms
bf196.js
69 ms
d5ca8.css
51 ms
24830.js
65 ms
f0363.js
67 ms
864c2.js
122 ms
b0646.js
121 ms
e49a1.js
120 ms
js
50 ms
page-bkgrnd-imageflags-light.jpg
55 ms
cropped-inside-shrine-room-top-kpl.jpg
73 ms
dragon-image768x489-678x381.jpg
73 ms
yamantaka.jpg
53 ms
firepuja.jpg
53 ms
Losar.jpg
55 ms
lamatratop2023.jpg
78 ms
16-Arhats-fea.png
72 ms
BTR-termaReading.jpg
65 ms
LamaTratop-100x1301-1.jpg
71 ms
naomischmidt.jpg
117 ms
MichaelHarris.jpg
102 ms
RHSChime-100x1301.jpg
102 ms
btr-small.jpg
99 ms
lamatratop1.jpg
103 ms
BTR---RHansen-SturmGarchen5-11_MG_0543.jpg
99 ms
BTR_17%20(1).jpg
120 ms
SandersKPLKarmapa20153.jpg
120 ms
RHSTaiSituandBTRKPL.jpg
122 ms
RHSKPLHHKarmapa7-26-11_MG_1835-1%20(1).jpg
152 ms
hhk16-and-btr.jpg
151 ms
RHansen-Sturm--BTR-and-GarchenR.jpg
152 ms
01-losar-rhs-e1419678344624%20(1).jpg
153 ms
BTR-at-Raktrul-Tib.jpg
154 ms
BTR_19.jpg
154 ms
BTR_10.jpg
154 ms
Tai%20Situ%20Rinpoche%20group%20photos%20-%2009.jpg
155 ms
BTR_9.jpg
158 ms
BTR_8.jpg
160 ms
Rinpoche_on_throne_closeup_2016.jpg
174 ms
Image%2059.jpg
175 ms
RHSMingyurRinpoche2016_DSC9953.jpg
176 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
53 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
53 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
60 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
61 ms
11222735_10152882984403201_7776005755173583345_o.jpg
175 ms
BTR_14.jpg
177 ms
BTR_18.jpg
168 ms
BTR_7.jpg
149 ms
BTR_15.jpg
135 ms
BTR_16.jpg
146 ms
empowerment[1].jpg
145 ms
BTR_12.jpg
148 ms
RHSKPLBirthday2019%2064.jpg
134 ms
BTR_13.png
149 ms
BTR_6.jpg
137 ms
BTR_5.jpg
150 ms
BTR_4.jpg
151 ms
BTR_3.jpg
146 ms
BTR_2.jpg
126 ms
RHSKPLBirthday2019%2031.jpg
130 ms
KPLAnn&BTRBrithday-ns-11.jpg
141 ms
KPLAnn&BTRBrithday-ns-37.jpg
143 ms
BTR---RHansen-SturmGarchen5-11_MG_0543.jpg
157 ms
BTR_17%20(1).jpg
128 ms
SandersKPLKarmapa20153.jpg
138 ms
RHSTaiSituandBTRKPL.jpg
143 ms
RHSKPLHHKarmapa7-26-11_MG_1835-1%20(1).jpg
144 ms
hhk16-and-btr.jpg
115 ms
RHansen-Sturm--BTR-and-GarchenR.jpg
117 ms
01-losar-rhs-e1419678344624%20(1).jpg
125 ms
BTR-at-Raktrul-Tib.jpg
136 ms
BTR_19.jpg
136 ms
BTR_10.jpg
134 ms
Tai%20Situ%20Rinpoche%20group%20photos%20-%2009.jpg
137 ms
fontawesome-webfont.woff
176 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf
5 ms
fontawesome-webfont.woff
159 ms
BTR_9.jpg
150 ms
BTR_8.jpg
138 ms
Rinpoche_on_throne_closeup_2016.jpg
138 ms
Image%2059.jpg
140 ms
RHSMingyurRinpoche2016_DSC9953.jpg
159 ms
11222735_10152882984403201_7776005755173583345_o.jpg
166 ms
BTR_14.jpg
165 ms
BTR_18.jpg
161 ms
BTR_7.jpg
166 ms
BTR_15.jpg
161 ms
BTR_16.jpg
162 ms
empowerment[1].jpg
161 ms
BTR_12.jpg
162 ms
RHSKPLBirthday2019%2064.jpg
163 ms
BTR_13.png
156 ms
BTR_6.jpg
162 ms
BTR_5.jpg
163 ms
BTR_4.jpg
163 ms
BTR_3.jpg
163 ms
BTR_2.jpg
167 ms
RHSKPLBirthday2019%2031.jpg
160 ms
KPLAnn&BTRBrithday-ns-11.jpg
166 ms
KPLAnn&BTRBrithday-ns-37.jpg
176 ms
blank.gif
149 ms
Rebirth-prayers.jpg
150 ms
covid-policy_580x326.jpg
185 ms
Barway-Dorje-rupa-80x60.jpg
160 ms
white-Khechari-mandala.jpg
160 ms
Lama-Tratop-2022.jpg
193 ms
thankas-smoke-news.jpg
156 ms
Yamantaka-smoke-news.jpg
158 ms
Yamantaka-Raktrul.jpg
161 ms
Lama-Tratop-news-2.jpg
160 ms
Yeshe_for_website.jpg
168 ms
kunzang.org 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
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
Form elements do not have associated labels
Links do not have a discernible name
kunzang.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
kunzang.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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kunzang.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Kunzang.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.
kunzang.org
Open Graph description is not detected on the main page of Kunzang. 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: