5.8 sec in total
89 ms
4.6 sec
1.1 sec
Visit uzazu.org now to see the best up-to-date UZAZU content and also check out these interesting facts you probably never knew about uzazu.org
Oops!You don't have permission to view this page! Make sure you're logged in and try again, or contact support.
Visit uzazu.orgWe analyzed Uzazu.org page load time and found that the first response time was 89 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
uzazu.org performance score
name
value
score
weighting
Value9.7 s
0/100
10%
Value16.3 s
0/100
25%
Value13.3 s
2/100
10%
Value1,740 ms
10/100
30%
Value0.053
98/100
15%
Value20.6 s
2/100
10%
89 ms
2715 ms
38 ms
53 ms
74 ms
Our browser made a total of 187 requests to load all elements on the main page. We found that 74% of them (138 requests) were addressed to the original Uzazu.org, 9% (17 requests) were made to Fonts.gstatic.com and 6% (12 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Uzazu.org.
Page size can be reduced by 839.5 kB (14%)
5.9 MB
5.1 MB
In fact, the total size of Uzazu.org main page is 5.9 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. Only a small number of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 549.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 549.8 kB or 86% of the original size.
Potential reduce by 204.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. UZAZU images are well optimized though.
Potential reduce by 5.9 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. This website has mostly compressed JavaScripts.
Potential reduce by 79.5 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. Uzazu.org needs all CSS files to be minified and compressed as it can save up to 79.5 kB or 24% of the original size.
Number of requests can be reduced by 135 (90%)
150
15
The browser has sent 150 CSS, Javascripts, AJAX and image requests in order to completely render the main page of UZAZU. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 87 to 1 for JavaScripts and from 50 to 1 for CSS and as a result speed up the page load time.
uzazu.org
89 ms
www.uzazu.org
2715 ms
bootstrap.min.css
38 ms
toolset_maps_fixes.css
53 ms
learndash.min.css
74 ms
ldvc.css
59 ms
grid-banner.css
55 ms
css
50 ms
css
50 ms
tribe-events-pro-mini-calendar-block.min.css
59 ms
style-index.css
63 ms
mediaelementplayer-legacy.min.css
68 ms
wp-mediaelement.min.css
70 ms
views-frontend.css
82 ms
template.css
84 ms
icons.css
95 ms
backend.css
87 ms
frontend-comp.css
115 ms
reactions-1723461196.css
90 ms
blogposts-.css
91 ms
markdown.css
93 ms
placeholders.css
100 ms
bundle.min.css
101 ms
learndash_quiz_front.min.css
103 ms
jquery.dropdown.min.css
104 ms
learndash_lesson_video.min.css
107 ms
h5p.css
141 ms
style.css
145 ms
print_style.css
143 ms
style.css
157 ms
media_style.css
147 ms
dashicons.min.css
151 ms
select2.css
153 ms
moods.css
154 ms
giphy.css
155 ms
learndash-.css
181 ms
jquery-ui.min.css
181 ms
datepicker.css
183 ms
frontend.css
184 ms
css
45 ms
css
49 ms
css
43 ms
css
42 ms
css
58 ms
css
60 ms
css
57 ms
css
56 ms
css
56 ms
css
68 ms
api.js
67 ms
landingpage-front.css
174 ms
style.css
147 ms
toolset-common-es-frontend.js
157 ms
jquery.min.js
157 ms
jquery-migrate.min.js
167 ms
all.min.js
190 ms
v4-shims.min.js
168 ms
wp-embed.min.js
158 ms
header.min.js
160 ms
imagesloaded.min.js
149 ms
masonry.min.js
150 ms
jquery.masonry.min.js
146 ms
general.min.js
144 ms
bundle.min.js
145 ms
frontend.min.js
145 ms
underscore-before.js
143 ms
underscore.min.js
139 ms
underscore-after.js
137 ms
core.min.js
136 ms
modules.min.js
135 ms
elements.min.js
135 ms
sections.min.js
133 ms
activitystream.min.js
100 ms
bootstrap.bundle.min.js
97 ms
learndash.js
95 ms
ldvc.js
91 ms
backbone.min.js
90 ms
api-request.min.js
89 ms
wp-api.min.js
88 ms
core.min.js
516 ms
bundle.min.js
492 ms
member.min.js
489 ms
activitystream.min.js
492 ms
comment.min.js
489 ms
form.min.js
490 ms
datepicker-noconflict.js
490 ms
datepicker.min.js
476 ms
datepicker.min.js
472 ms
activity.min.js
458 ms
image-scale.min.js
456 ms
modal-comments.min.js
455 ms
reactions.min.js
455 ms
hashtags.min.js
455 ms
page-autoload.min.js
455 ms
blogposts.min.js
455 ms
markdown.min.js
455 ms
mouse.min.js
455 ms
sortable.min.js
455 ms
postbox-backgrounds.js
454 ms
follower.min.js
454 ms
site_tracking.js
454 ms
triggers.min.js
454 ms
conditional-display.min.js
454 ms
toggle.min.js
453 ms
video.min.js
454 ms
custom.js
454 ms
jqueryfscript.js
454 ms
frontend.min.js
454 ms
suggest.min.js
454 ms
main.js
455 ms
date.js
454 ms
usertags.min.js
454 ms
location.min.js
454 ms
moods.min.js
454 ms
3-Day-UZAZU-Workshop-Moscow-2019-Embodied-Experience-Sponge.jpeg
724 ms
3-Day-UZAZU-Workshop-Moscow-2019-258-Anastasia-Listens.jpeg
750 ms
3-Day-UZAZU-Workshop-Moscow-2019-22-Dylan-and-Alena.jpeg
755 ms
Group-Embodiment-in-the-UZAZU-Workshop-Moscow-2019-52.jpeg
623 ms
4-Moments-from-the-Moscow-UZAZU-Foundations-Training-2019-2.jpeg
759 ms
Dylan-Newcomb-Aug-19-2021-Vinalhaven-Maine-Portrait-2.2.jpeg
756 ms
Deb-Grant-Full-Photo-March-10-2023-2.jpeg
752 ms
bundle.min.js
169 ms
giphy.min.js
166 ms
bundle.min.js
164 ms
bundle.min.js
164 ms
peepsofriends.min.js
164 ms
bundle.min.js
163 ms
group.min.js
325 ms
bundle.min.js
326 ms
bundle.min.js
325 ms
grid.min.js
327 ms
peepsophotos.min.js
320 ms
bundle.min.js
320 ms
jquery.autosize.min.js
333 ms
custom_uzazu_core.js
331 ms
smush-lazy-load.min.js
409 ms
menu.min.js
410 ms
no-campaign.min.js
408 ms
main-footer.jpg
412 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf
167 ms
Nunito-Regular.woff
400 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhdTQ3ig.ttf
207 ms
Nunito-Medium.woff
397 ms
Nunito-Light.woff
397 ms
Nunito-ExtraLight.woff
397 ms
Nunito-SemiBold.woff
396 ms
Nunito-Bold.woff
398 ms
Nunito-ExtraBold.woff
399 ms
Nunito-Black.woff
524 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
204 ms
Montserrat-SemiBold.woff
523 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
210 ms
Montserrat-ExtraBold.woff
530 ms
Montserrat-Bold.woff
400 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
210 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
210 ms
Montserrat-Black.woff
524 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
210 ms
Montserrat-Medium.woff
521 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
304 ms
Montserrat-Regular.woff
523 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
299 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
309 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
308 ms
Montserrat-Thin.woff
522 ms
Montserrat-Bold.woff
524 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
308 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
307 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
308 ms
Montserrat-SemiBold.woff
524 ms
Montserrat-Regular.woff
522 ms
diffuser.js
303 ms
recaptcha__en.js
209 ms
Deb-guides-Kellie-into-Pillar-Mode-UZAZU-Embodied-Intelligence-v2-copy.jpeg
440 ms
prism.app-us1.com
226 ms
uzazu-logo-v5-600.png
101 ms
anchor
44 ms
styles__ltr.css
5 ms
recaptcha__en.js
14 ms
OIgm6ct-G6hNh5i9U8xy5lNjsT6YVTG9uZdpykbdxBU.js
43 ms
webworker.js
82 ms
logo_48.png
29 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
11 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
11 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
11 ms
recaptcha__en.js
12 ms
Albert-Viljoen-2.jpg
33 ms
uzazu.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
Links do not have a discernible name
uzazu.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
Missing source maps for large first-party JavaScript
uzazu.org SEO score
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 Uzazu.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 Uzazu.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.
uzazu.org
Open Graph data is detected on the main page of UZAZU. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: