8.6 sec in total
123 ms
7.9 sec
568 ms
Visit search.indypl.org now to see the best up-to-date Search Indypl content for United States and also check out these interesting facts you probably never knew about search.indypl.org
Explore The Indianapolis Public Library. New titles, recently rated, and recently tagged by the library community.
Visit search.indypl.orgWe analyzed Search.indypl.org page load time and found that the first response time was 123 ms and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
search.indypl.org performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value40.4 s
0/100
25%
Value30.2 s
0/100
10%
Value38,980 ms
0/100
30%
Value0.545
13/100
15%
Value50.1 s
0/100
10%
123 ms
1676 ms
357 ms
294 ms
519 ms
Our browser made a total of 195 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Search.indypl.org, 59% (115 requests) were made to Contentcafe2.btol.com and 23% (45 requests) were made to Cor-cdn-static.bibliocommons.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Fonts.googleapis.com.
Page size can be reduced by 738.6 kB (20%)
3.6 MB
2.9 MB
In fact, the total size of Search.indypl.org main page is 3.6 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 521.7 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 521.7 kB or 91% of the original size.
Potential reduce by 213.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. Search Indypl images are well optimized though.
Potential reduce by 67 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 3.5 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. Search.indypl.org has all CSS files already compressed.
Number of requests can be reduced by 38 (25%)
155
117
The browser has sent 155 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Search Indypl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
search.indypl.org
123 ms
indypl.bibliocommons.com
1676 ms
gtm.js
357 ms
analytics.js
294 ms
bc_base-7458b34fb4de9be11818e405e123b860.css
519 ms
core-7d64d4c928373d7aa8d477bce16543c5.css
551 ms
dashboard-aa0ea2fdf1b09998517dc104ca00771e.css
550 ms
library_branding.css
510 ms
vendor-8b62f51688d44fede5e5f3b4d64b7ba8.js
582 ms
sdk.js
453 ms
core-81d20c140346a97912b9d456245585c0.js
576 ms
dashboard-6b043bd6a4a50850e3e54efe74297e8c.js
575 ms
collect
288 ms
collect
287 ms
8067.js
299 ms
js
146 ms
css
281 ms
indypl.bibliocommons.com.json
29 ms
logo.png
27 ms
preloader.grey-0972ac11db78fb0f16f5338beb76d559.gif
24 ms
ajax-loader-2ad22ee6988a62b7f1661cb696219501.gif
24 ms
print-fb42783833d8fede559cd8b19f911dd8.css
20 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
141 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
197 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
198 ms
fontello-7aaf5df643343c6846d1d2be8803acd8.woff
11 ms
base_master-9668a2e92af385e1e8e47db36e3c7845.png
53 ms
app.sdk-da53d9c1c28c77f4cb9e.css
123 ms
app.sdk-da53d9c1c28c77f4cb9e.js
143 ms
css
1878 ms
app.0-30b527625a95aef0f00b.css
164 ms
app.0-30b527625a95aef0f00b.js
165 ms
app.1-12615104ee44680807f1.css
165 ms
app.1-12615104ee44680807f1.js
176 ms
app.2-16ee0ecb83f034954c19.css
293 ms
app.2-16ee0ecb83f034954c19.js
311 ms
app.14-021b657cda7b6f243912.css
311 ms
app.14-021b657cda7b6f243912.js
309 ms
app.bibliocommons-catalogue-carousel-0ebe858a3690fe3e380b.css
276 ms
app.bibliocommons-catalogue-carousel-0ebe858a3690fe3e380b.js
427 ms
recent_lists_carousel
1498 ms
app.app-components-layouts-FeedbackBox-FeedbackBoxContainer-ee988b036fd1db5c23e5.css
325 ms
app.app-components-layouts-FeedbackBox-FeedbackBoxContainer-ee988b036fd1db5c23e5.js
325 ms
nerf_sdk_library_branding.css
153 ms
app.bibliocommons-rating-card-060231d21efad9508dd4.css
222 ms
app.bibliocommons-rating-card-060231d21efad9508dd4.js
221 ms
2182733689.png
440 ms
2182356151.png
413 ms
2182133729.png
415 ms
2181543879.png
421 ms
2181132103.png
419 ms
2181085050.png
417 ms
2181070639.png
413 ms
2180972129.png
416 ms
2179894789.png
419 ms
2179707249.png
415 ms
2179649459.png
420 ms
2179640029.png
421 ms
2179438799.png
422 ms
2178784559.png
423 ms
2178380709.png
424 ms
2178307349.png
424 ms
2178245289.png
425 ms
2177377496.png
428 ms
2177113479.png
426 ms
2176466689.png
427 ms
2176076339.png
431 ms
2175833519.png
435 ms
2173883379.png
429 ms
2173430389.png
436 ms
2173278959.png
432 ms
2173226739.png
429 ms
2173189659.png
436 ms
2172052979.png
432 ms
2171707649.png
433 ms
2171060417.png
436 ms
Jacket.aspx
799 ms
Jacket.aspx
365 ms
Jacket.aspx
586 ms
Jacket.aspx
587 ms
Jacket.aspx
612 ms
Jacket.aspx
613 ms
Jacket.aspx
609 ms
Jacket.aspx
608 ms
Jacket.aspx
604 ms
Jacket.aspx
600 ms
Jacket.aspx
619 ms
Jacket.aspx
621 ms
Jacket.aspx
626 ms
Jacket.aspx
670 ms
Jacket.aspx
626 ms
Jacket.aspx
626 ms
Jacket.aspx
633 ms
Jacket.aspx
639 ms
Jacket.aspx
683 ms
Jacket.aspx
644 ms
Jacket.aspx
641 ms
Jacket.aspx
650 ms
Jacket.aspx
653 ms
Jacket.aspx
661 ms
Jacket.aspx
657 ms
Jacket.aspx
665 ms
Jacket.aspx
669 ms
Jacket.aspx
679 ms
Jacket.aspx
675 ms
Jacket.aspx
681 ms
Jacket.aspx
684 ms
Jacket.aspx
684 ms
Jacket.aspx
694 ms
Jacket.aspx
694 ms
Jacket.aspx
696 ms
Jacket.aspx
697 ms
2180103477.png
409 ms
2177666325.png
286 ms
2177257129.png
269 ms
2175820739.png
252 ms
Jacket.aspx
345 ms
Jacket.aspx
157 ms
Jacket.aspx
130 ms
Jacket.aspx
423 ms
Jacket.aspx
116 ms
Jacket.aspx
122 ms
Jacket.aspx
114 ms
Jacket.aspx
111 ms
Jacket.aspx
118 ms
Jacket.aspx
121 ms
Jacket.aspx
125 ms
Jacket.aspx
115 ms
Jacket.aspx
116 ms
Jacket.aspx
118 ms
Jacket.aspx
122 ms
Jacket.aspx
121 ms
Jacket.aspx
164 ms
Jacket.aspx
117 ms
Jacket.aspx
119 ms
Jacket.aspx
115 ms
Jacket.aspx
157 ms
Jacket.aspx
128 ms
Jacket.aspx
118 ms
Jacket.aspx
114 ms
Jacket.aspx
131 ms
Jacket.aspx
171 ms
Jacket.aspx
128 ms
Jacket.aspx
186 ms
Jacket.aspx
136 ms
Jacket.aspx
143 ms
Jacket.aspx
155 ms
Jacket.aspx
147 ms
Jacket.aspx
143 ms
Jacket.aspx
157 ms
Jacket.aspx
172 ms
Jacket.aspx
153 ms
Jacket.aspx
154 ms
Jacket.aspx
162 ms
Jacket.aspx
175 ms
Jacket.aspx
160 ms
Jacket.aspx
160 ms
Jacket.aspx
167 ms
Jacket.aspx
215 ms
Jacket.aspx
213 ms
Jacket.aspx
211 ms
Jacket.aspx
208 ms
Jacket.aspx
202 ms
Jacket.aspx
203 ms
Jacket.aspx
198 ms
Jacket.aspx
196 ms
Jacket.aspx
186 ms
Jacket.aspx
186 ms
Jacket.aspx
183 ms
Jacket.aspx
182 ms
Jacket.aspx
169 ms
Jacket.aspx
167 ms
Jacket.aspx
171 ms
Jacket.aspx
177 ms
Jacket.aspx
155 ms
Jacket.aspx
153 ms
Jacket.aspx
157 ms
Jacket.aspx
162 ms
Jacket.aspx
154 ms
Jacket.aspx
136 ms
Jacket.aspx
135 ms
Jacket.aspx
148 ms
Jacket.aspx
148 ms
Jacket.aspx
139 ms
Jacket.aspx
141 ms
Jacket.aspx
137 ms
Jacket.aspx
140 ms
Jacket.aspx
138 ms
Jacket.aspx
176 ms
Jacket.aspx
171 ms
Jacket.aspx
166 ms
Jacket.aspx
160 ms
Jacket.aspx
194 ms
Jacket.aspx
108 ms
Jacket.aspx
107 ms
search.indypl.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
search.indypl.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
search.indypl.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
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 Search.indypl.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 Search.indypl.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.
search.indypl.org
Open Graph description is not detected on the main page of Search Indypl. 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: