Report Summary

  • 58

    Performance

    Renders faster than
    75% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

wh.org

WalkerHouse, a Christian internet community, Falls Church, Virginia and worldwide on the internet

Page Load Speed

1.8 sec in total

First Response

81 ms

Resources Loaded

828 ms

Page Rendered

893 ms

wh.org screenshot

About Website

Click here to check amazing Wh content. Otherwise, check out these important facts you probably never knew about wh.org

WalkerHouse Christian forum on the internet where we encourage Christians to follow God's word and prosper in this life. WalkerHouse publishes Christian literature from Falls Church, Virginia and worl...

Visit wh.org

Key Findings

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

Performance Metrics

wh.org performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

61/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value1,650 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

wh.org

81 ms

wh.org

138 ms

api.js

53 ms

recaptcha__en.js

102 ms

whbac.gif

61 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 35% of them (7 requests) were addressed to the original Wh.org, 25% (5 requests) were made to Gstatic.com and 15% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (503 ms) relates to the external source I3.cpcache.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.7 kB (22%)

Content Size

154.9 kB

After Optimization

120.3 kB

In fact, the total size of Wh.org main page is 154.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. 25% of websites need less resources to load. Images take 139.6 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 9.8 kB

  • Original 13.5 kB
  • After minification 12.3 kB
  • After compression 3.7 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 9.8 kB or 73% of the original size.

Image Optimization

-18%

Potential reduce by 24.7 kB

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

JavaScript Optimization

-9%

Potential reduce by 52 B

  • Original 572 B
  • After minification 572 B
  • After compression 520 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.

CSS Optimization

-2%

Potential reduce by 25 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 1.3 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. Wh.org has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

16

After Optimization

16

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wh. According to our analytics all requests are already optimized.

Accessibility Review

wh.org accessibility score

66

Accessibility Issues

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

High

Links do not have a discernible name

Best Practices

wh.org best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

SEO Factors

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wh.org 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 Wh.org main page’s claimed encoding is . 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

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