2.3 sec in total
19 ms
2 sec
269 ms
Welcome to reading.org homepage info - get ready to check Reading best content for United States right away, or after learning these important things about reading.org
A global advocacy and membership organization that transforms lives through literacy across 75 countries.
Visit reading.orgWe analyzed Reading.org page load time and found that the first response time was 19 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
reading.org performance score
19 ms
91 ms
63 ms
37 ms
47 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Reading.org, 64% (32 requests) were made to Literacyworldwide.org and 16% (8 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Literacyworldwide.org.
Page size can be reduced by 2.8 MB (66%)
4.3 MB
1.5 MB
In fact, the total size of Reading.org main page is 4.3 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. 65% of websites need less resources to load. Javascripts take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 33.5 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 5.7 kB, which is 13% 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 33.5 kB or 76% of the original size.
Potential reduce by 9.1 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. Reading images are well optimized though.
Potential reduce by 2.6 MB
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 2.6 MB or 70% of the original size.
Potential reduce by 194.9 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. Reading.org needs all CSS files to be minified and compressed as it can save up to 194.9 kB or 84% of the original size.
Number of requests can be reduced by 26 (67%)
39
13
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Reading. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
reading.org
19 ms
www.literacyworldwide.org
91 ms
trq7eyn.js
63 ms
jquery.min.js
37 ms
Telerik.Web.UI.WebResource.axd
47 ms
layout_transformations.css
33 ms
reset.css
15 ms
fonts.css
16 ms
style.css
21 ms
responsive.css
19 ms
newHeader.css
18 ms
newHeaderLogin.css
20 ms
style-guide.css
22 ms
WebResource.axd
30 ms
ScriptResource.axd
26 ms
ScriptResource.axd
24 ms
ScriptResource.axd
30 ms
ScriptResource.axd
63 ms
ScriptResource.axd
71 ms
ScriptResource.axd
31 ms
ScriptResource.axd
31 ms
WebResource.axd
35 ms
html5lightbox.js
34 ms
custom.js
35 ms
www.literacyworldwide.org
134 ms
ila-logo.png
375 ms
firstread_1250x400.jpg
376 ms
homepage-1.jpg
373 ms
homepage-2.jpg
375 ms
homepage-3.jpg
373 ms
ila-signature.png
374 ms
Ss3XBz9h_pHlW_2l5bq_t4DR2XepMw35xFP4wKzJnZSffHhpEN32IgCjMKM2HMItgI4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff
55 ms
cVsyxOJe39SMAhm5wPoEm9p-NaXtNQY5Npx_Jj3H92CffVamggMdeMJ6Mk6g5MZfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
172 ms
sZasDCRCTb0vT302FeYZCnZTACZ8AOe97EcjQ2xh1LXffOfpEN32IgCjMKM2HMItgX4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff
174 ms
icon-search.png
46 ms
icomoon.woff
76 ms
gtm.js
72 ms
css
55 ms
lightbox-next.png
552 ms
lightbox-prev.png
61 ms
lightbox-close.png
1060 ms
x6fEe8WNPge-24DUADPGGUzGh1yyYZiRBrLTsRTIJSwffHEpEN32IgCjMKM2HMIt2q4MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff
47 ms
JNmWtxbm21hjkJkG9wxB1MdsTstkuH3LFak_rGEqdo9ffV_mggMdeMJ6Mk6g5ggfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
264 ms
VotKQGc6kv5IkgrCWMkBbPw_623JM0yJVuIDQ55lkKjffHrpEN32IgCjMKM2HMItI94MFhFqjhJXFe48FeIaZeJt52SaZcZyFAw3w2MajRyqZ26hFAJDjc4RwD6D52wUZc9kZAIUFDicFRJkFQiy5QIowb.woff
57 ms
p.gif
116 ms
analytics.js
26 ms
linkid.js
11 ms
collect
12 ms
collect
53 ms
roundtrip.js
9 ms
reading.org SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Reading.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Reading.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.
reading.org
Open Graph description is not detected on the main page of Reading. 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: