Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

bible.us

Read the Bible online. A free Bible on your phone, tablet, or computer. | The Bible App | Bible.com

Page Load Speed

7.2 sec in total

First Response

77 ms

Resources Loaded

6.7 sec

Page Rendered

463 ms

bible.us screenshot

About Website

Click here to check amazing Bible content. Otherwise, check out these important facts you probably never knew about bible.us

Read God’s Word at anytime, anywhere using the YouVersion Bible App. Share Scripture with friends, highlight passages, and create a daily habit with Bible Plans.

Visit bible.us

Key Findings

We analyzed Bible.us page load time and found that the first response time was 77 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

bible.us performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value4,650 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value21.5 s

1/100

10%

Network Requests Diagram

bible.us

77 ms

www.bible.com

678 ms

gtm.js

284 ms

application-6bd15353b81348bbf67ce4a7fa99a965.css

69 ms

style.main.1305df54a016aa3c822fa1790414f5e9.css

351 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Bible.us, 24% (15 requests) were made to Bible.com and 16% (10 requests) were made to Imageproxy.youversionapi.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Script.hotjar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (64%)

Content Size

1.8 MB

After Optimization

659.7 kB

In fact, the total size of Bible.us main page is 1.8 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. 75% 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. HTML takes 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 1.1 MB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 178.9 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 1.1 MB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 361.7 kB
  • After minification 361.7 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. Bible images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 32.2 kB

  • Original 90.9 kB
  • After minification 90.9 kB
  • After compression 58.7 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 32.2 kB or 35% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 60.4 kB
  • After minification 60.4 kB
  • After compression 60.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. Bible.us has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 33 (60%)

Requests Now

55

After Optimization

22

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

Accessibility Review

bible.us accessibility score

66

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

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.

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

Links do not have a discernible name

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

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

bible.us best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

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

Content Best Practices

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

Impact

Issue

High

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

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

Open Graph data is detected on the main page of Bible. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: