Tools & Wizards About Us
hymnary.org screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

hymnary.org

Hymnary.org: a comprehensive index of hymns and hymnals | Hymnary.org

Page Load Speed

1.3 sec in total

First Response

89 ms

Resources Loaded

1.1 sec

Page Rendered

93 ms

hymnary.org screenshot

About Website

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.org

Key Findings

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

Performance Metrics

hymnary.org performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value3,850 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value34.1 s

0/100

10%

Network Requests Diagram

hymnary.org

89 ms

hymnary.org

150 ms

system.base.css

33 ms

system.menus.css

65 ms

system.messages.css

87 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 84% of them (72 requests) were addressed to the original Hymnary.org, 3% (3 requests) were made to Cdnjs.cloudflare.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (470 ms) relates to the external source Cmp.inmobi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 82.4 kB (26%)

Content Size

312.8 kB

After Optimization

230.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hymnary.org main page is 312.8 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 125.8 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 38.4 kB

  • Original 47.5 kB
  • After minification 44.1 kB
  • After compression 9.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 38.4 kB or 81% of the original size.

Image Optimization

-19%

Potential reduce by 13.3 kB

  • Original 69.9 kB
  • After minification 56.6 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, Hymnary needs image optimization as it can save up to 13.3 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-16%

Potential reduce by 20.5 kB

  • Original 125.8 kB
  • After minification 122.7 kB
  • After compression 105.3 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 20.5 kB or 16% of the original size.

CSS Optimization

-15%

Potential reduce by 10.2 kB

  • Original 69.5 kB
  • After minification 69.5 kB
  • After compression 59.4 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 10.2 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 66 (79%)

Requests Now

84

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 84 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 34 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hymnary.org

hymnary.org

89 ms

hymnary.org

hymnary.org

150 ms

system.base.css

system.base.css

33 ms

system.menus.css

system.menus.css

65 ms

system.messages.css

system.messages.css

87 ms

system.theme.css

system.theme.css

93 ms

comment.css

comment.css

94 ms

field.css

field.css

92 ms

logintoboggan.css

logintoboggan.css

94 ms

node.css

node.css

95 ms

poll.css

poll.css

117 ms

uc_file.css

uc_file.css

123 ms

uc_order.css

uc_order.css

124 ms

uc_product.css

uc_product.css

123 ms

uc_store.css

uc_store.css

122 ms

user.css

user.css

125 ms

forum.css

forum.css

145 ms

views.css

views.css

153 ms

ctools.css

ctools.css

153 ms

hymnary.css

hymnary.css

154 ms

hymnary-mobile.css

hymnary-mobile.css

155 ms

jquery.tooltip.css

jquery.tooltip.css

156 ms

jquery.editable-select.css

jquery.editable-select.css

173 ms

hymnary_ecommerce.css

hymnary_ecommerce.css

181 ms

luyh.css

luyh.css

183 ms

style.css

style.css

185 ms

style-mobile.css

style-mobile.css

185 ms

uc_cart_block-override.css

uc_cart_block-override.css

188 ms

hamburger.css

hamburger.css

202 ms

hamburger-submenu.css

hamburger-submenu.css

219 ms

hymnary-sidr-theme.css

hymnary-sidr-theme.css

219 ms

headerbar-menu.css

headerbar-menu.css

221 ms

pager.css

pager.css

220 ms

blockedBanner.css

blockedBanner.css

221 ms

all.css

all.css

209 ms

jquery.js

jquery.js

257 ms

jquery-extend-3.4.0.js

jquery-extend-3.4.0.js

240 ms

jquery-html-prefilter-3.5.0-backport.js

jquery-html-prefilter-3.5.0-backport.js

243 ms

jquery-3.4.0.slim.min.js

jquery-3.4.0.slim.min.js

40 ms

bloodhound.min.js

bloodhound.min.js

38 ms

typeahead.bundle.min.js

typeahead.bundle.min.js

48 ms

typeahead.jquery.min.js

typeahead.jquery.min.js

60 ms

js

js

57 ms

cls.css

cls.css

42 ms

pubfig.min.js

pubfig.min.js

61 ms

jquery.once.js

jquery.once.js

242 ms

drupal.js

drupal.js

220 ms

uc_file.js

uc_file.js

191 ms

hymnary-search-block.js

hymnary-search-block.js

189 ms

jquery.tooltip.js

jquery.tooltip.js

186 ms

jquery.delegate.js

jquery.delegate.js

188 ms

jquery.bgiframe.js

jquery.bgiframe.js

189 ms

jquery.editable-select.js

jquery.editable-select.js

193 ms

popup.js

popup.js

196 ms

AnalyticsEvents.js

AnalyticsEvents.js

189 ms

js.cookie.js

js.cookie.js

200 ms

luyh.js

luyh.js

200 ms

home_page.js

home_page.js

200 ms

hymnary_search_autocomplete.js

hymnary_search_autocomplete.js

201 ms

googleanalytics.js

googleanalytics.js

200 ms

hamburger.js

hamburger.js

230 ms

hamburger-submenu.js

hamburger-submenu.js

223 ms

headerbar-menu.js

headerbar-menu.js

223 ms

retina.js

retina.js

224 ms

includes.js

includes.js

226 ms

experiment.js

experiment.js

223 ms

blockedBanner.js

blockedBanner.js

209 ms

analytics.js

analytics.js

86 ms

js

js

85 ms

choice.js

choice.js

470 ms

domain

domain

426 ms

hymnary-H-box-sized.png

hymnary-H-box-sized.png

224 ms

hymnary-title.png

hymnary-title.png

225 ms

hamburger.png

hamburger.png

223 ms

star.png

star.png

223 ms

flexscore.png

flexscore.png

224 ms

myhymnals.png

myhymnals.png

224 ms

cart.png

cart.png

227 ms

ccel-logo2.png

ccel-logo2.png

227 ms

cicw-logo2.png

cicw-logo2.png

225 ms

calvin-university.svg

calvin-university.svg

228 ms

hs-footer_sm.png

hs-footer_sm.png

228 ms

NEH-logo-small.png

NEH-logo-small.png

231 ms

menu-leaf.gif

menu-leaf.gif

203 ms

collect

collect

41 ms

collect

collect

32 ms

Accessibility Review

hymnary.org accessibility score

73

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

hymnary.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

hymnary.org SEO score

73

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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 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.

Social Sharing Optimization

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: