6.9 sec in total
920 ms
5.5 sec
469 ms
Click here to check amazing Smcl Biblio Commons content for United States. Otherwise, check out these important facts you probably never knew about smcl.bibliocommons.com
Explore San Mateo County Libraries. New titles, recently rated, and recently tagged by the library community.
Visit smcl.bibliocommons.comWe analyzed Smcl.bibliocommons.com page load time and found that the first response time was 920 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
smcl.bibliocommons.com performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value4.2 s
44/100
25%
Value30.6 s
0/100
10%
Value36,250 ms
0/100
30%
Value0.603
10/100
15%
Value61.3 s
0/100
10%
920 ms
183 ms
105 ms
129 ms
143 ms
Our browser made a total of 192 requests to load all elements on the main page. We found that 2% of them (4 requests) were addressed to the original Smcl.bibliocommons.com, 58% (111 requests) were made to Contentcafe2.btol.com and 21% (41 requests) were made to Cor-cdn-static.bibliocommons.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Smcl.bibliocommons.com.
Page size can be reduced by 719.3 kB (28%)
2.6 MB
1.9 MB
In fact, the total size of Smcl.bibliocommons.com main page is 2.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.0 MB which makes up the majority of the site volume.
Potential reduce by 436.4 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 436.4 kB or 89% of the original size.
Potential reduce by 279.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. Obviously, Smcl Biblio Commons needs image optimization as it can save up to 279.3 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
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.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. Smcl.bibliocommons.com has all CSS files already compressed.
Number of requests can be reduced by 62 (39%)
157
95
The browser has sent 157 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Smcl Biblio Commons. 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 19 to 1 for CSS and as a result speed up the page load time.
smcl.bibliocommons.com
920 ms
gtm.js
183 ms
analytics.js
105 ms
bc_base-7458b34fb4de9be11818e405e123b860.css
129 ms
core-7d64d4c928373d7aa8d477bce16543c5.css
143 ms
dashboard-aa0ea2fdf1b09998517dc104ca00771e.css
128 ms
library_branding.css
287 ms
stylesheet.css
237 ms
css2
172 ms
footer_all.css
170 ms
vendor-8b62f51688d44fede5e5f3b4d64b7ba8.js
174 ms
sdk.js
175 ms
core-81d20c140346a97912b9d456245585c0.js
172 ms
dashboard-6b043bd6a4a50850e3e54efe74297e8c.js
171 ms
collect
57 ms
collect
59 ms
8067.js
56 ms
js
54 ms
css
15 ms
logo.png
22 ms
Open-for-Exploration-Tagline.png
384 ms
preloader.grey-0972ac11db78fb0f16f5338beb76d559.gif
23 ms
ajax-loader-2ad22ee6988a62b7f1661cb696219501.gif
20 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
103 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
104 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
105 ms
print-fb42783833d8fede559cd8b19f911dd8.css
75 ms
smcl.bibliocommons.com.json
88 ms
fontello-7aaf5df643343c6846d1d2be8803acd8.woff
25 ms
base_master-9668a2e92af385e1e8e47db36e3c7845.png
6 ms
app.sdk-da53d9c1c28c77f4cb9e.css
43 ms
app.sdk-da53d9c1c28c77f4cb9e.js
415 ms
css
23 ms
recent_tags
1745 ms
app.0-30b527625a95aef0f00b.css
117 ms
app.0-30b527625a95aef0f00b.js
138 ms
app.1-12615104ee44680807f1.css
142 ms
app.1-12615104ee44680807f1.js
141 ms
app.bibliocommons-catalogue-carousel-0ebe858a3690fe3e380b.css
236 ms
app.bibliocommons-catalogue-carousel-0ebe858a3690fe3e380b.js
271 ms
app.2-16ee0ecb83f034954c19.css
218 ms
app.2-16ee0ecb83f034954c19.js
219 ms
app.14-021b657cda7b6f243912.css
216 ms
app.14-021b657cda7b6f243912.js
219 ms
recent_lists_carousel
797 ms
app.app-components-layouts-FeedbackBox-FeedbackBoxContainer-ee988b036fd1db5c23e5.css
649 ms
app.app-components-layouts-FeedbackBox-FeedbackBoxContainer-ee988b036fd1db5c23e5.js
706 ms
nerf_sdk_library_branding.css
176 ms
app.bibliocommons-rating-card-060231d21efad9508dd4.css
505 ms
app.bibliocommons-rating-card-060231d21efad9508dd4.js
500 ms
Jacket.aspx
579 ms
image_proxy
425 ms
Jacket.aspx
216 ms
Jacket.aspx
217 ms
Jacket.aspx
218 ms
Jacket.aspx
579 ms
Jacket.aspx
585 ms
Jacket.aspx
583 ms
Jacket.aspx
580 ms
Jacket.aspx
581 ms
Jacket.aspx
581 ms
Jacket.aspx
579 ms
Jacket.aspx
582 ms
Jacket.aspx
603 ms
Jacket.aspx
586 ms
Jacket.aspx
585 ms
Jacket.aspx
583 ms
Jacket.aspx
586 ms
Jacket.aspx
585 ms
Jacket.aspx
606 ms
Jacket.aspx
588 ms
Jacket.aspx
587 ms
Jacket.aspx
607 ms
Jacket.aspx
589 ms
Jacket.aspx
588 ms
Jacket.aspx
622 ms
Jacket.aspx
590 ms
Jacket.aspx
621 ms
Jacket.aspx
589 ms
Jacket.aspx
590 ms
Jacket.aspx
591 ms
Jacket.aspx
592 ms
Jacket.aspx
595 ms
Jacket.aspx
596 ms
Jacket.aspx
597 ms
Jacket.aspx
599 ms
Jacket.aspx
600 ms
2180059779.png
445 ms
2179927769.png
383 ms
2179916819.png
384 ms
2179479309.png
384 ms
2178092890.png
385 ms
2177230089.png
389 ms
2176223319.png
429 ms
2176200814.png
410 ms
2176117229.png
414 ms
2173553399.png
415 ms
2173532319.png
461 ms
2173527219.png
467 ms
2173527009.png
430 ms
2173526109.png
426 ms
2172626779.png
475 ms
2172165337.png
512 ms
2170634219.png
468 ms
2170242959.png
509 ms
2170075249.png
476 ms
2169380229.png
477 ms
2169377369.png
504 ms
2169376699.png
510 ms
2169046259.png
501 ms
2169039389.png
502 ms
2167217769.png
508 ms
2166022579.png
508 ms
2165972118.png
570 ms
2165068909.png
510 ms
2165065659.png
511 ms
2165031609.png
533 ms
Jacket.aspx
387 ms
Jacket.aspx
389 ms
Jacket.aspx
387 ms
Jacket.aspx
57 ms
Jacket.aspx
42 ms
Jacket.aspx
42 ms
Jacket.aspx
43 ms
Jacket.aspx
44 ms
Jacket.aspx
43 ms
Jacket.aspx
44 ms
Jacket.aspx
45 ms
Jacket.aspx
45 ms
Jacket.aspx
44 ms
Jacket.aspx
44 ms
Jacket.aspx
45 ms
Jacket.aspx
90 ms
Jacket.aspx
91 ms
Jacket.aspx
44 ms
Jacket.aspx
45 ms
Jacket.aspx
44 ms
Jacket.aspx
42 ms
Jacket.aspx
44 ms
Jacket.aspx
87 ms
Jacket.aspx
88 ms
Jacket.aspx
43 ms
Jacket.aspx
43 ms
Jacket.aspx
41 ms
Jacket.aspx
40 ms
Jacket.aspx
41 ms
Jacket.aspx
39 ms
Jacket.aspx
40 ms
Jacket.aspx
39 ms
Jacket.aspx
40 ms
Jacket.aspx
64 ms
Jacket.aspx
62 ms
Jacket.aspx
63 ms
Jacket.aspx
63 ms
Jacket.aspx
52 ms
Jacket.aspx
52 ms
Jacket.aspx
50 ms
Jacket.aspx
52 ms
Jacket.aspx
52 ms
Jacket.aspx
51 ms
Jacket.aspx
52 ms
Jacket.aspx
52 ms
Jacket.aspx
53 ms
Jacket.aspx
49 ms
Jacket.aspx
53 ms
Jacket.aspx
51 ms
Jacket.aspx
51 ms
Jacket.aspx
48 ms
Jacket.aspx
50 ms
Jacket.aspx
50 ms
Jacket.aspx
50 ms
Jacket.aspx
49 ms
Jacket.aspx
86 ms
Jacket.aspx
85 ms
Jacket.aspx
48 ms
Jacket.aspx
46 ms
Jacket.aspx
83 ms
Jacket.aspx
46 ms
Jacket.aspx
45 ms
Jacket.aspx
45 ms
Jacket.aspx
45 ms
Jacket.aspx
47 ms
Jacket.aspx
48 ms
Jacket.aspx
45 ms
Jacket.aspx
45 ms
Jacket.aspx
45 ms
Jacket.aspx
46 ms
Jacket.aspx
46 ms
Jacket.aspx
43 ms
Jacket.aspx
43 ms
Jacket.aspx
44 ms
Jacket.aspx
44 ms
smcl.bibliocommons.com 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
smcl.bibliocommons.com 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
smcl.bibliocommons.com 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 Smcl.bibliocommons.com 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 Smcl.bibliocommons.com 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.
smcl.bibliocommons.com
Open Graph description is not detected on the main page of Smcl Biblio Commons. 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: