1.7 sec in total
92 ms
1.3 sec
272 ms
Click here to check amazing Ctb Ku content for United States. Otherwise, check out these important facts you probably never knew about ctb.ku.edu
Tools to change our world – free resources for those working to build healthier communities and bring about social change.
Visit ctb.ku.eduWe analyzed Ctb.ku.edu page load time and found that the first response time was 92 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 30% of websites can load faster.
ctb.ku.edu performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value7.7 s
3/100
25%
Value4.5 s
72/100
10%
Value120 ms
97/100
30%
Value0.149
76/100
15%
Value6.5 s
59/100
10%
92 ms
33 ms
63 ms
65 ms
97 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 58% of them (45 requests) were addressed to the original Ctb.ku.edu, 14% (11 requests) were made to Fonts.gstatic.com and 9% (7 requests) were made to Cdn.knightlab.com. The less responsive or slowest element that took the longest time to load (536 ms) belongs to the original domain Ctb.ku.edu.
Page size can be reduced by 960.5 kB (38%)
2.5 MB
1.5 MB
In fact, the total size of Ctb.ku.edu main page is 2.5 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. 55% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 91.2 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 91.2 kB or 73% of the original size.
Potential reduce by 167.7 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. Obviously, Ctb Ku needs image optimization as it can save up to 167.7 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 517.3 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 517.3 kB or 65% of the original size.
Potential reduce by 184.2 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. Ctb.ku.edu needs all CSS files to be minified and compressed as it can save up to 184.2 kB or 83% of the original size.
Number of requests can be reduced by 24 (39%)
61
37
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ctb Ku. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
en
92 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
33 ms
css_15Pp1wZ03zUuWC8I4dbsH5Kj1ZxWogrs2FHyNIlwiVo.css
63 ms
css_u81ggvGX1BcxQCN0Uf_oYO39wowg5Rc3OYhUru5Fp1A.css
65 ms
css_1V5Fl3QKZ7ditDRH9MtJP8PrYTK4GR70w5q2tbW7y4w.css
97 ms
jquery.min.js
154 ms
jquery.once.js
66 ms
drupal.js
105 ms
jquery.nivo.slider.pack.js
122 ms
views_nivo_slider.js
105 ms
googleanalytics.js
104 ms
easing.js
127 ms
bootstrap.min.js
164 ms
jquery.tipTip.minified.js
126 ms
application.js
125 ms
addthis_widget.js
9 ms
amiri.css
24 ms
ga.js
146 ms
heart.png
133 ms
index.html
83 ms
300lo.json
28 ms
counter.8eb9e83b9fa0d4af1e4f.js
20 ms
logo_complete.png
64 ms
logo-text.png
65 ms
ctb-logo-english-print.png
95 ms
logo_xs.png
66 ms
search.png
65 ms
continents.png
82 ms
header_bg.png
80 ms
slider-bg.jpg
169 ms
buildyourtoolbox_slide.png
536 ms
communitycheckbox_announcement_0.png
338 ms
ctb-slide-1710x651.png
257 ms
3_0.jpg
233 ms
2_0.jpg
190 ms
5.jpg
287 ms
4.jpg
273 ms
book.png
290 ms
life_saver.png
317 ms
ku_logo_white.png
304 ms
loading.gif
318 ms
en
372 ms
menuicon1.png
334 ms
menuicon2.png
347 ms
menuicon3.png
348 ms
menuicon4.png
366 ms
menuicon5.png
367 ms
arrows.png
378 ms
proxima_nova_regular-webfont.woff
408 ms
proximanovacond-bold-webfont.woff
530 ms
proxima_nova_condensed_semibold-webfont.woff
531 ms
proxima_nova_light-webfont.woff
531 ms
sh.7c7179124ea24ac6ba46caac.html
27 ms
storyjs-embed-cdn.js
45 ms
__utm.gif
31 ms
shares.json
25 ms
timeline.css
22 ms
webfont.js
31 ms
__utm.gif
15 ms
collect
98 ms
css
23 ms
jquery.min.js
31 ms
BreeSerif-OpenSans.css
25 ms
timeline-min.js
32 ms
LQ7WLTaITDg4OSRuOZCpsxsxEYwM7FgeyaSgU71cLG0.woff
27 ms
PRmiXeptR36kaC0GEAetxh_xHqYgAV9Bl_ZQbYUxnQU.woff
36 ms
xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff
50 ms
PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff
39 ms
PRmiXeptR36kaC0GEAetxjqR_3kx9_hJXbbyU8S6IN0.woff
50 ms
PRmiXeptR36kaC0GEAetxkCDe67GEgBv_HnyvHTfdew.woff
48 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
49 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
47 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
47 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
55 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
60 ms
loading.gif
14 ms
values
237 ms
timeline.png
108 ms
ctb.ku.edu 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
[id] attributes on active, focusable elements are not unique
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
Links do not have a discernible name
ctb.ku.edu 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
ctb.ku.edu 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ctb.ku.edu 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 Ctb.ku.edu 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.
ctb.ku.edu
Open Graph description is not detected on the main page of Ctb Ku. 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: