Tools & Wizards About Us
whatsaiththescripture.com screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

whatsaiththescripture.com

What Saith The Scripture?

Page Load Speed

1.1 sec in total

First Response

70 ms

Resources Loaded

606 ms

Page Rendered

392 ms

whatsaiththescripture.com screenshot

About Website

Click here to check amazing What Saith The Scripture content for United States. Otherwise, check out these important facts you probably never knew about whatsaiththescripture.com

The key to your whole Rapture position is faith in the character of God and His Promises to escape ALL the events of the Tribulation Week.

Visit whatsaiththescripture.com

Key Findings

We analyzed Whatsaiththescripture.com page load time and found that the first response time was 70 ms and then it took 998 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

whatsaiththescripture.com performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

81/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value870 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value3.3 s

93/100

10%

Network Requests Diagram

whatsaiththescripture.com

70 ms

dropdown.css

18 ms

dropdown.js

19 ms

WStSContents.js

37 ms

show_ads.js

6 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 53% of them (20 requests) were addressed to the original Whatsaiththescripture.com, 11% (4 requests) were made to Pagead2.googlesyndication.com and 11% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (383 ms) belongs to the original domain Whatsaiththescripture.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 513.4 kB (87%)

Content Size

587.9 kB

After Optimization

74.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whatsaiththescripture.com main page is 587.9 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. 35% of websites need less resources to load. HTML takes 541.1 kB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 505.0 kB

  • Original 541.1 kB
  • After minification 540.0 kB
  • After compression 36.0 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 505.0 kB or 93% of the original size.

Image Optimization

-9%

Potential reduce by 1.6 kB

  • Original 17.2 kB
  • After minification 15.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. What Saith The Scripture images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 6.1 kB

  • Original 28.7 kB
  • After minification 27.2 kB
  • After compression 22.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 6.1 kB or 21% of the original size.

CSS Optimization

-63%

Potential reduce by 624 B

  • Original 985 B
  • After minification 813 B
  • After compression 361 B

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. Whatsaiththescripture.com needs all CSS files to be minified and compressed as it can save up to 624 B or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (53%)

Requests Now

36

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whatsaiththescripture.com

whatsaiththescripture.com

70 ms

dropdown.css

dropdown.css

18 ms

dropdown.js

dropdown.js

19 ms

WStSContents.js

WStSContents.js

37 ms

show_ads.js

show_ads.js

6 ms

brand

brand

13 ms

urchin.js

urchin.js

51 ms

brand

brand

62 ms

Silver.Thin.GIF

Silver.Thin.GIF

35 ms

1x1.GIF

1x1.GIF

14 ms

Silver.Wide.GIF

Silver.Wide.GIF

37 ms

Jesus.JPG

Jesus.JPG

36 ms

Title.WStS.white.GIF

Title.WStS.white.GIF

37 ms

topleft.GIF

topleft.GIF

35 ms

topright.GIF

topright.GIF

37 ms

dot.com.Contents.GIF

dot.com.Contents.GIF

383 ms

bottomleft.GIF

bottomleft.GIF

40 ms

bottomright.GIF

bottomright.GIF

40 ms

bottomdip.GIF

bottomdip.GIF

39 ms

Coming.Soon.JPG

Coming.Soon.JPG

39 ms

WStS.com.GIF

WStS.com.GIF

45 ms

Whats.New.Blue.GIF

Whats.New.Blue.GIF

48 ms

Tiny.Silver.Bullet.2.GIF

Tiny.Silver.Bullet.2.GIF

48 ms

WStS_Nav_Contents.txt

WStS_Nav_Contents.txt

124 ms

ca-pub-6599946240000106.js

ca-pub-6599946240000106.js

31 ms

zrt_lookup.html

zrt_lookup.html

22 ms

show_ads_impl.js

show_ads_impl.js

50 ms

__utm.gif

__utm.gif

69 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

316 ms

ads

ads

276 ms

osd.js

osd.js

245 ms

m_js_controller.js

m_js_controller.js

21 ms

abg.js

abg.js

40 ms

favicon

favicon

62 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

61 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

29 ms

s

s

14 ms

x_button_blue2.png

x_button_blue2.png

3 ms

Accessibility Review

whatsaiththescripture.com accessibility score

54

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Best Practices

whatsaiththescripture.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

whatsaiththescripture.com SEO score

67

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatsaiththescripture.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Whatsaiththescripture.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

whatsaiththescripture.com

Open Graph description is not detected on the main page of What Saith The Scripture. 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: