5.7 sec in total
504 ms
3.9 sec
1.2 sec
Click here to check amazing World Library content for India. Otherwise, check out these important facts you probably never knew about worldlibrary.org
World Public Library - Publics
Visit worldlibrary.orgWe analyzed Worldlibrary.org page load time and found that the first response time was 504 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
worldlibrary.org performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value7.6 s
4/100
25%
Value6.9 s
34/100
10%
Value270 ms
82/100
30%
Value0.001
100/100
15%
Value8.5 s
38/100
10%
504 ms
681 ms
565 ms
246 ms
592 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 16% of them (12 requests) were addressed to the original Worldlibrary.org, 64% (48 requests) were made to Read.images.worldlibrary.net and 17% (13 requests) were made to Ebook2.worldlibrary.net. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Read.images.worldlibrary.net.
Page size can be reduced by 1.0 MB (37%)
2.7 MB
1.7 MB
In fact, the total size of Worldlibrary.org main page is 2.7 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 36.3 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 6.0 kB, which is 14% 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 36.3 kB or 82% of the original size.
Potential reduce by 52.0 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. World Library images are well optimized though.
Potential reduce by 636.5 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 636.5 kB or 76% of the original size.
Potential reduce by 294.6 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. Worldlibrary.org needs all CSS files to be minified and compressed as it can save up to 294.6 kB or 86% of the original size.
Number of requests can be reduced by 27 (38%)
72
45
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of World Library. 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 11 to 1 for CSS and as a result speed up the page load time.
worldlibrary.org
504 ms
bootstrap.css
681 ms
animate.css
565 ms
bannerscollection_zoominout.css
246 ms
modernizr.js
592 ms
jquery1.8.3.js
1120 ms
bannerscollection_zoominout.js
587 ms
wpl.css
749 ms
font-awesome.min.css
715 ms
bootstrap.js
1494 ms
jquery.inview.min.js
605 ms
jquery.prettyPhoto.js
1511 ms
isotope.js
694 ms
jquery.maximage.js
734 ms
jquery.bxslider.min.js
799 ms
appear.js
817 ms
wpl.js
865 ms
jquery-ui-1.10.4.custom.min.js
1607 ms
jquery-ui-1.10.4.custom.min.css
1607 ms
greybox.js
322 ms
greybox.css
337 ms
loader.gif
127 ms
Phone_Beach.jpg
705 ms
ReadingBringsUsTogether.jpg
706 ms
pattern.png
124 ms
02_opportune_full.jpg
536 ms
slider-top-second.jpg
510 ms
03_opportune_full.jpg
268 ms
slider-top-4th.jpg
702 ms
audiobooks-listen.jpg
538 ms
zoom.png
697 ms
ebooks.jpg
968 ms
studends-int-man.jpg
849 ms
facebook-white.png
701 ms
mediatools.aspx
532 ms
callout.jpg
2319 ms
callout-bottom.jpg
981 ms
menu_bottom_top_bg.png
703 ms
myriadpro-semibold_opentype-webfont.woff
755 ms
fontawesome-webfont.woff
1070 ms
arrow_off.gif
128 ms
8ldvc09.jpg
951 ms
stars_5.0.jpg
967 ms
jquery-1.11.0.min.js
1211 ms
core.js
802 ms
core_plugin.js
911 ms
autoscroll.js
790 ms
jquery.jcarousel-1.0.1.css
795 ms
detail-1.0.0.css
927 ms
site-1.0.1.css
920 ms
books.css
920 ms
adventures_of_huckleberry_finn.jpg
902 ms
relativityspeci01einsgoog.gif
804 ms
three_little_pigs.jpg
1285 ms
stars_4.0.jpg
924 ms
jungletalesoftar00burruoft.gif
1055 ms
originofspecies00darwuoft.gif
992 ms
frankrevise.jpg
1371 ms
the_jungle_book.jpg
1057 ms
caralic.gif
1161 ms
greatexpectatio00dick.gif
1572 ms
dyssy.jpg
1188 ms
decline1.jpg
1335 ms
tprnc.jpg
1325 ms
studyofhistoryvo009724mbp.gif
1506 ms
hawaiis_story_by_hawaiis_queen.jpg
1452 ms
img_trans.gif
1499 ms
leftNavOFF.png
131 ms
rightNavOFF.png
130 ms
play_overOFF.png
140 ms
hand.cur
430 ms
bottomNavOFF.png
249 ms
scroll_arrows.png
479 ms
ga.js
41 ms
__utm.gif
25 ms
worldlibrary.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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
worldlibrary.org 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
worldlibrary.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 Worldlibrary.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 Worldlibrary.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.
worldlibrary.org
Open Graph description is not detected on the main page of World Library. 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: