Tools & Wizards About Us
eapl.org screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

eapl.org

Home | Ela Area Public Library

Page Load Speed

3.9 sec in total

First Response

1.4 sec

Resources Loaded

2.3 sec

Page Rendered

175 ms

eapl.org screenshot

About Website

Visit eapl.org now to see the best up-to-date Eapl content for India and also check out these interesting facts you probably never knew about eapl.org

Visit eapl.org

Key Findings

We analyzed Eapl.org page load time and found that the first response time was 1.4 sec and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

eapl.org performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value1,560 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.114

86/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

eapl.org

1429 ms

css_kShW4RPmRstZ3SpIC-ZvVGNFVAi0WEMuCnI0ZkYIaFw.css

126 ms

css_vZ_wrMQ9Og-YPPxa1q4us3N7DsZMJa-14jShHgRoRNo.css

150 ms

css_L9hO9cuM-tT_-ZRzVJ9LOCA24CLlaFdGi_FAqtjG3oY.css

129 ms

css

23 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 77% of them (41 requests) were addressed to the original Eapl.org, 8% (4 requests) were made to Libraryh3lp.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Eapl.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 496.8 kB (54%)

Content Size

913.0 kB

After Optimization

416.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eapl.org main page is 913.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 461.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 70.5 kB

  • Original 87.5 kB
  • After minification 85.8 kB
  • After compression 17.1 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 70.5 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 14.1 kB

  • Original 270.8 kB
  • After minification 256.8 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. Eapl images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 336.5 kB

  • Original 461.6 kB
  • After minification 399.3 kB
  • After compression 125.1 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 336.5 kB or 73% of the original size.

CSS Optimization

-81%

Potential reduce by 75.8 kB

  • Original 93.0 kB
  • After minification 89.2 kB
  • After compression 17.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. Eapl.org needs all CSS files to be minified and compressed as it can save up to 75.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (50%)

Requests Now

50

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eapl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

eapl.org

eapl.org

1429 ms

css_kShW4RPmRstZ3SpIC-ZvVGNFVAi0WEMuCnI0ZkYIaFw.css

css_kShW4RPmRstZ3SpIC-ZvVGNFVAi0WEMuCnI0ZkYIaFw.css

126 ms

css_vZ_wrMQ9Og-YPPxa1q4us3N7DsZMJa-14jShHgRoRNo.css

css_vZ_wrMQ9Og-YPPxa1q4us3N7DsZMJa-14jShHgRoRNo.css

150 ms

css_L9hO9cuM-tT_-ZRzVJ9LOCA24CLlaFdGi_FAqtjG3oY.css

css_L9hO9cuM-tT_-ZRzVJ9LOCA24CLlaFdGi_FAqtjG3oY.css

129 ms

css

css

23 ms

css_bvhIN4r55FQJw7XjYnHXd-se63ssQ1ONZnyX3yvKPbw.css

css_bvhIN4r55FQJw7XjYnHXd-se63ssQ1ONZnyX3yvKPbw.css

147 ms

css_nvQkjQ1-6eU0eihINsUgyU5LUQwn6ou-iBNkmq2iVsI.css

css_nvQkjQ1-6eU0eihINsUgyU5LUQwn6ou-iBNkmq2iVsI.css

131 ms

js_jpJjaUC0z8JMIyav5oQrYykDRUb64rpaUDpB4Y9aklU.js

js_jpJjaUC0z8JMIyav5oQrYykDRUb64rpaUDpB4Y9aklU.js

159 ms

js_2b-c3Ad47bVDxtZMmDKXbwb9lCJ_CjUsv6EQ6bgkuzs.js

js_2b-c3Ad47bVDxtZMmDKXbwb9lCJ_CjUsv6EQ6bgkuzs.js

203 ms

js_KEVLrojPh8B6r5mgtF2RYdikPkeKo9awuwix_SkN15E.js

js_KEVLrojPh8B6r5mgtF2RYdikPkeKo9awuwix_SkN15E.js

240 ms

js_5gw0jq0fNhlkal50iM2jWzBXpE3t2LjdEZrss9g-RLY.js

js_5gw0jq0fNhlkal50iM2jWzBXpE3t2LjdEZrss9g-RLY.js

194 ms

js_rjYH_eRa7L_D29070OpSiLnDi0OfNB0FR3rwIO0kzSs.js

js_rjYH_eRa7L_D29070OpSiLnDi0OfNB0FR3rwIO0kzSs.js

215 ms

js_Ycy26uh-ISELEFM9R5F3rWtVkFQXhFgB9cJVhPwDCC4.js

js_Ycy26uh-ISELEFM9R5F3rWtVkFQXhFgB9cJVhPwDCC4.js

201 ms

analytics.js

analytics.js

177 ms

elacirc@chat.libraryh3lp.com

elacirc@chat.libraryh3lp.com

196 ms

logo.png

logo.png

162 ms

book_icon.png

book_icon.png

165 ms

magazine_icon.png

magazine_icon.png

165 ms

audio_icon.png

audio_icon.png

162 ms

video_icon.png

video_icon.png

165 ms

left-nav-bg.png

left-nav-bg.png

165 ms

prev.png

prev.png

166 ms

next.png

next.png

167 ms

hoopla_2.jpg

hoopla_2.jpg

365 ms

white-65.png

white-65.png

167 ms

Passport%20Survey.jpg

Passport%20Survey.jpg

370 ms

Go%20Pro1.jpg

Go%20Pro1.jpg

368 ms

ZinioNEW_2.jpg

ZinioNEW_2.jpg

364 ms

ReUseAShoe_2.jpg

ReUseAShoe_2.jpg

433 ms

hoopla_2.jpg

hoopla_2.jpg

269 ms

Passport%20Survey.jpg

Passport%20Survey.jpg

332 ms

Go%20Pro1.jpg

Go%20Pro1.jpg

392 ms

ZinioNEW_2.jpg

ZinioNEW_2.jpg

433 ms

ReUseAShoe_2.jpg

ReUseAShoe_2.jpg

432 ms

HistoryHEreAPp.png

HistoryHEreAPp.png

434 ms

aSmall.gif

aSmall.gif

469 ms

a_reset.gif

a_reset.gif

470 ms

aBig.gif

aBig.gif

472 ms

facebook.png

facebook.png

470 ms

twitter.png

twitter.png

473 ms

pinterest.png

pinterest.png

481 ms

youtube.png

youtube.png

481 ms

flickrgreen_0.png

flickrgreen_0.png

523 ms

chosen-sprite.png

chosen-sprite.png

455 ms

WidgetV3.ashx

WidgetV3.ashx

112 ms

ODelI1aHBYDBqgeIAH2zlNHq-FFgoDNV3GTKpHwuvtI.woff

ODelI1aHBYDBqgeIAH2zlNHq-FFgoDNV3GTKpHwuvtI.woff

18 ms

toadOcfmlt9b38dHJxOBGCmgpmuQqK2I-L2S9cF65Ek.woff

toadOcfmlt9b38dHJxOBGCmgpmuQqK2I-L2S9cF65Ek.woff

19 ms

collect

collect

37 ms

sprite_2010011801.png

sprite_2010011801.png

71 ms

react.min.js

react.min.js

39 ms

libraryh3lp_jid.js

libraryh3lp_jid.js

70 ms

embedded.js

embedded.js

203 ms

unavailable

unavailable

142 ms

Accessibility Review

eapl.org accessibility score

93

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

eapl.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

eapl.org SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eapl.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 Eapl.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.

Social Sharing Optimization

eapl.org

Open Graph description is not detected on the main page of Eapl. 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: