4.1 sec in total
1.5 sec
2.3 sec
342 ms
Click here to check amazing Centerforstory content. Otherwise, check out these important facts you probably never knew about centerforstory.org
Learn more about the transformative power of story, and how the new Center for Story will change lives...one story at a time.
Visit centerforstory.orgWe analyzed Centerforstory.org page load time and found that the first response time was 1.5 sec and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
centerforstory.org performance score
1486 ms
119 ms
122 ms
194 ms
374 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 92% of them (54 requests) were addressed to the original Centerforstory.org, 3% (2 requests) were made to Google.com and 3% (2 requests) were made to Paypalobjects.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Centerforstory.org.
Page size can be reduced by 132.1 kB (12%)
1.1 MB
955.7 kB
In fact, the total size of Centerforstory.org main page is 1.1 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. 35% of websites need less resources to load. Images take 923.2 kB which makes up the majority of the site volume.
Potential reduce by 21.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. This page needs HTML code to be minified as it can gain 2.9 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 21.2 kB or 84% of the original size.
Potential reduce by 7.3 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. Centerforstory images are well optimized though.
Potential reduce by 55.8 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 55.8 kB or 68% of the original size.
Potential reduce by 47.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. Centerforstory.org needs all CSS files to be minified and compressed as it can save up to 47.7 kB or 83% of the original size.
Number of requests can be reduced by 32 (56%)
57
25
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Centerforstory. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
centerforstory.org
1486 ms
template.css
119 ms
custom.css
122 ms
mod_yoo_carousel.css.php
194 ms
mootools.js
374 ms
caption.js
154 ms
base.js
192 ms
accordionmenu.js
202 ms
fancymenu.js
224 ms
dropdownmenu.js
228 ms
template.js
225 ms
mod_yoo_carousel.js
201 ms
brand
14 ms
reset.css
155 ms
layout.css
178 ms
typography.css
185 ms
menus.css
270 ms
modules.css
283 ms
joomla.css
284 ms
extensions.css
241 ms
brand
37 ms
btn_donateCC_LG.gif
58 ms
pixel.gif
63 ms
bg_white.jpg
440 ms
bg_mainmenu.png
61 ms
menubar_bg.png
64 ms
menubar_shadow.png
65 ms
menu_level1_item.png
62 ms
menu_dropdown_corners.png
74 ms
menu_dropdown_edges.png
118 ms
module_headerbar.png
130 ms
logo.png
132 ms
Power4.jpg
190 ms
StorytellingFestival.jpg
197 ms
youthtellertraining.jpg
183 ms
Power3.jpg
194 ms
drama.jpg
194 ms
Power2.jpg
307 ms
c4s.workshop.web.jpg
388 ms
Power1.jpg
262 ms
music.jpg
276 ms
dance.jpg
274 ms
home-page-side-ads.jpg
338 ms
orem-city-logo.jpg
343 ms
orem-library-logo.jpg
344 ms
tsf-logo.jpg
374 ms
content_wrapper_corners.png
387 ms
content_wrapper_edges_without.png
392 ms
button_prev.png
401 ms
button_next.png
430 ms
google_custom_search_watermark.gif
33 ms
article_separator.png
429 ms
module_tab_l.png
440 ms
module_tab_t.png
445 ms
module_tab_tr.png
454 ms
module_tab_bl.png
472 ms
module_tab_header.png
481 ms
module_rounded_white_corners.png
488 ms
footer_anchor.png
496 ms
centerforstory.org SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Centerforstory.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 Centerforstory.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.
centerforstory.org
Open Graph description is not detected on the main page of Centerforstory. 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: