2.2 sec in total
117 ms
1.9 sec
137 ms
Click here to check amazing Hymnary content for United States. Otherwise, check out these important facts you probably never knew about hymnary.org
Hymnary.org: A comprehensive index of over 1 million hymn texts, hymn tunes, and hymnals, with information on authors and composers, lyrics and scores of many hymns, and various media files. Hymnary.o...
Visit hymnary.orgWe analyzed Hymnary.org page load time and found that the first response time was 117 ms and then it took 2.1 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.
hymnary.org performance score
name
value
score
weighting
Value8.9 s
0/100
10%
Value9.2 s
1/100
25%
Value10.6 s
7/100
10%
Value1,540 ms
13/100
30%
Value0.002
100/100
15%
Value12.9 s
13/100
10%
117 ms
462 ms
71 ms
111 ms
138 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 28% of them (13 requests) were addressed to the original Hymnary.org, 20% (9 requests) were made to Static.hymnary.org and 11% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (545 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 264.4 kB (48%)
551.6 kB
287.2 kB
In fact, the total size of Hymnary.org main page is 551.6 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. 40% of websites need less resources to load. Javascripts take 278.1 kB which makes up the majority of the site volume.
Potential reduce by 22.2 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 22.2 kB or 72% of the original size.
Potential reduce by 12.9 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. Hymnary images are well optimized though.
Potential reduce by 155.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 155.5 kB or 56% of the original size.
Potential reduce by 73.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. Hymnary.org needs all CSS files to be minified and compressed as it can save up to 73.9 kB or 79% of the original size.
Number of requests can be reduced by 19 (45%)
42
23
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hymnary. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
hymnary.org
117 ms
www.hymnary.org
462 ms
css_c6800f59b749db7819dc684c1385b578.css
71 ms
books.css
111 ms
js_2c83b0a187d03906dc493b90530dbca9.js
138 ms
retina.js
110 ms
print.css
109 ms
adsbygoogle.js
4 ms
analytics.js
58 ms
all.js
272 ms
hymnary-title.png
72 ms
cicw-luyh.jpg
175 ms
ccel-logo2.png
32 ms
cicw-logo2.png
32 ms
calvin-logo2.png
72 ms
hs-footer_sm.png
66 ms
NEH-logo-small.png
63 ms
gradientbar2.png
32 ms
throbber.gif
40 ms
star.png
65 ms
page-tune.png
68 ms
flexscore.png
130 ms
myhymnals.png
130 ms
flexscore-promotion.png
130 ms
ca-pub-3003432132428802.js
43 ms
zrt_lookup.html
38 ms
show_ads_impl.js
59 ms
hymnary.woff
118 ms
collect
15 ms
ads
182 ms
osd.js
8 ms
css_5aa88501152fb1b2eecc8716a05309b8.css
34 ms
145 ms
xd_arbiter.php
227 ms
xd_arbiter.php
430 ms
5648765536851216039
40 ms
abg.js
41 ms
m_js_controller.js
51 ms
googlelogo_color_112x36dp.png
85 ms
x_button_blue2.png
27 ms
s
24 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
4 ms
ui
56 ms
like.php
85 ms
vpc6VNjRPXV.js
484 ms
LVx-xkvaJ0b.png
545 ms
hymnary.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-*] attributes do not match their roles
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
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
hymnary.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
General
Impact
Issue
Detected JavaScript libraries
hymnary.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 Hymnary.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 Hymnary.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.
hymnary.org
Open Graph description is not detected on the main page of Hymnary. 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: