Tools & Wizards About Us
houseofprayerhingham.org screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

houseofprayerhingham.org

House of Prayer – Spreading Christ’s Message of Love

Page Load Speed

1.3 sec in total

First Response

98 ms

Resources Loaded

905 ms

Page Rendered

344 ms

houseofprayerhingham.org screenshot

About Website

Welcome to houseofprayerhingham.org homepage info - get ready to check House Of Prayer Hingham best content right away, or after learning these important things about houseofprayerhingham.org

House of Prayer Hingham Home. “My house shall be called a house of prayer for all peoples.’’ - Isaiah 56:7

Visit houseofprayerhingham.org

Key Findings

We analyzed Houseofprayerhingham.org page load time and found that the first response time was 98 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

houseofprayerhingham.org performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value7.9 s

22/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

houseofprayerhingham.org

98 ms

houseofprayerhingham.org

184 ms

js

88 ms

formidableforms.css

123 ms

layerslider.css

128 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 74% of them (49 requests) were addressed to the original Houseofprayerhingham.org, 17% (11 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (383 ms) belongs to the original domain Houseofprayerhingham.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 242.7 kB (12%)

Content Size

2.1 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Houseofprayerhingham.org main page is 2.1 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. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 113.5 kB

  • Original 138.5 kB
  • After minification 137.5 kB
  • After compression 25.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 113.5 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 110.4 kB

  • Original 1.4 MB
  • After minification 1.3 MB

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. House Of Prayer Hingham images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.0 kB

  • Original 402.3 kB
  • After minification 402.3 kB
  • After compression 400.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. This website has mostly compressed JavaScripts.

CSS Optimization

-11%

Potential reduce by 16.8 kB

  • Original 154.1 kB
  • After minification 154.1 kB
  • After compression 137.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. Houseofprayerhingham.org needs all CSS files to be minified and compressed as it can save up to 16.8 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (71%)

Requests Now

52

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

houseofprayerhingham.org

houseofprayerhingham.org

98 ms

houseofprayerhingham.org

houseofprayerhingham.org

184 ms

js

js

88 ms

formidableforms.css

formidableforms.css

123 ms

layerslider.css

layerslider.css

128 ms

style.min.css

style.min.css

38 ms

be.css

be.css

42 ms

animations.min.css

animations.min.css

118 ms

fontawesome.css

fontawesome.css

67 ms

jplayer.blue.monday.min.css

jplayer.blue.monday.min.css

77 ms

responsive.css

responsive.css

74 ms

css

css

71 ms

jquery.qtip.min.css

jquery.qtip.min.css

77 ms

default-calendar-grid.min.css

default-calendar-grid.min.css

78 ms

default-calendar-list.min.css

default-calendar-list.min.css

79 ms

greensock.js

greensock.js

75 ms

jquery.min.js

jquery.min.js

76 ms

jquery-migrate.min.js

jquery-migrate.min.js

77 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

108 ms

layerslider.transitions.js

layerslider.transitions.js

107 ms

email-decode.min.js

email-decode.min.js

105 ms

css

css

64 ms

rs6.css

rs6.css

116 ms

rbtools.min.js

rbtools.min.js

372 ms

rs6.min.js

rs6.min.js

365 ms

core.min.js

core.min.js

279 ms

tabs.min.js

tabs.min.js

230 ms

debouncedresize.min.js

debouncedresize.min.js

260 ms

magnificpopup.min.js

magnificpopup.min.js

259 ms

menu.js

menu.js

260 ms

visible.min.js

visible.min.js

261 ms

animations.min.js

animations.min.js

262 ms

jplayer.min.js

jplayer.min.js

284 ms

enllax.min.js

enllax.min.js

274 ms

translate3d.js

translate3d.js

275 ms

scripts.js

scripts.js

276 ms

jquery.qtip.min.js

jquery.qtip.min.js

281 ms

default-calendar.min.js

default-calendar.min.js

280 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

281 ms

Screen-Shot-2017-11-18-at-5.08.52-PM.png

Screen-Shot-2017-11-18-at-5.08.52-PM.png

59 ms

box_shadow.png

box_shadow.png

139 ms

dummy.png

dummy.png

137 ms

Sanctuary.jpg

Sanctuary.jpg

59 ms

St-Francis-window-of-prayer.jpg

St-Francis-window-of-prayer.jpg

275 ms

Psalm-1412-window-of-prayer.jpg

Psalm-1412-window-of-prayer.jpg

60 ms

HOP-signature-window.png

HOP-signature-window.png

115 ms

Luke-216-window.jpg

Luke-216-window.jpg

144 ms

Burning-bush-window-of-prayer.jpg

Burning-bush-window-of-prayer.jpg

383 ms

Luke-322b-window-of-prayer.jpg

Luke-322b-window-of-prayer.jpg

244 ms

evlogo.png

evlogo.png

275 ms

Disability-sign.png

Disability-sign.png

229 ms

js

js

123 ms

analytics.js

analytics.js

115 ms

u-4n0qyriQwlOrhSvowK_l521wRZWMf_.ttf

u-4n0qyriQwlOrhSvowK_l521wRZWMf_.ttf

185 ms

u-440qyriQwlOrhSvowK_l5-fCZJ.ttf

u-440qyriQwlOrhSvowK_l5-fCZJ.ttf

220 ms

u-4n0qyriQwlOrhSvowK_l52xwNZWMf_.ttf

u-4n0qyriQwlOrhSvowK_l52xwNZWMf_.ttf

220 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

221 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

200 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

215 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

135 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

133 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

136 ms

icons.woff

icons.woff

269 ms

u-4m0qyriQwlOrhSvowK_l5-eRZOf-c.ttf

u-4m0qyriQwlOrhSvowK_l5-eRZOf-c.ttf

137 ms

u-4l0qyriQwlOrhSvowK_l5-eR71Wvf4jvk.ttf

u-4l0qyriQwlOrhSvowK_l5-eR71Wvf4jvk.ttf

136 ms

collect

collect

61 ms

Accessibility Review

houseofprayerhingham.org accessibility score

77

Accessibility Issues

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

houseofprayerhingham.org SEO score

93

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

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

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

houseofprayerhingham.org

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