Tools & Wizards About Us
saintmaryvancouver.org screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

saintmaryvancouver.org

Hohite Semay Saint Mary Ethiopian Orthodox Tewahido Church

Page Load Speed

1.4 sec in total

First Response

167 ms

Resources Loaded

862 ms

Page Rendered

360 ms

saintmaryvancouver.org screenshot

About Website

Visit saintmaryvancouver.org now to see the best up-to-date Saint Mary Vancouver content and also check out these interesting facts you probably never knew about saintmaryvancouver.org

Hohite Semay Saint Mary Ethiopian Orthodox Tewahido Church welcomes you to join us in praising the Lord

Visit saintmaryvancouver.org

Key Findings

We analyzed Saintmaryvancouver.org page load time and found that the first response time was 167 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 20% of websites can load faster.

Performance Metrics

saintmaryvancouver.org performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value3,430 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.96

2/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

saintmaryvancouver.org

167 ms

style.css

30 ms

subscribeform.css

60 ms

skin.css

60 ms

prettyPhoto.css

69 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 87% of them (62 requests) were addressed to the original Saintmaryvancouver.org, 3% (2 requests) were made to Code.jquery.com and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (229 ms) belongs to the original domain Saintmaryvancouver.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 996.0 kB (24%)

Content Size

4.2 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Saintmaryvancouver.org main page is 4.2 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. 80% 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 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 45.4 kB

  • Original 57.1 kB
  • After minification 46.9 kB
  • After compression 11.6 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. This page needs HTML code to be minified as it can gain 10.2 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 45.4 kB or 80% of the original size.

Image Optimization

-21%

Potential reduce by 828.5 kB

  • Original 3.9 MB
  • After minification 3.1 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. Obviously, Saint Mary Vancouver needs image optimization as it can save up to 828.5 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-46%

Potential reduce by 113.5 kB

  • Original 244.9 kB
  • After minification 244.7 kB
  • After compression 131.4 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 113.5 kB or 46% of the original size.

CSS Optimization

-29%

Potential reduce by 8.6 kB

  • Original 29.7 kB
  • After minification 29.7 kB
  • After compression 21.2 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. Saintmaryvancouver.org needs all CSS files to be minified and compressed as it can save up to 8.6 kB or 29% of the original size.

Requests Breakdown

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

Requests Now

68

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

saintmaryvancouver.org

saintmaryvancouver.org

167 ms

style.css

style.css

30 ms

subscribeform.css

subscribeform.css

60 ms

skin.css

skin.css

60 ms

prettyPhoto.css

prettyPhoto.css

69 ms

ui.totop.css

ui.totop.css

59 ms

jplayer.blue.monday.css

jplayer.blue.monday.css

54 ms

jquery-1.6.1.min.js

jquery-1.6.1.min.js

93 ms

superfish.js

superfish.js

78 ms

tabs.js

tabs.js

77 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

77 ms

jquery.jcarousel.js

jquery.jcarousel.js

94 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

107 ms

hover-image.js

hover-image.js

96 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

118 ms

jplayer.playlist.min.js

jplayer.playlist.min.js

97 ms

jquery.ui.totop.js

jquery.ui.totop.js

117 ms

FF-cash.js

FF-cash.js

117 ms

jquery.hashchange.min.js

jquery.hashchange.min.js

120 ms

jquery.easytabs.min.js

jquery.easytabs.min.js

121 ms

swfobject_modified.js

swfobject_modified.js

128 ms

jquery-ui.css

jquery-ui.css

21 ms

jquery-ui.js

jquery-ui.js

23 ms

jquery-ui-1.10.2.custom.js

jquery-ui-1.10.2.custom.js

229 ms

jquery-ui-1.10.2.custom.css

jquery-ui-1.10.2.custom.css

140 ms

jquerycookie.js

jquerycookie.js

140 ms

subscript.js

subscript.js

142 ms

reset.css

reset.css

121 ms

grid_24.css

grid_24.css

129 ms

superfish.css

superfish.css

140 ms

css

css

21 ms

all.js

all.js

59 ms

frontbg.jpg

frontbg.jpg

51 ms

menubg2.jpg

menubg2.jpg

100 ms

FinalHeader.jpg

FinalHeader.jpg

105 ms

nav_span.png

nav_span.png

97 ms

nav_sub_marker.png

nav_sub_marker.png

99 ms

nav_sub_marker2.png

nav_sub_marker2.png

99 ms

s-1.jpg

s-1.jpg

104 ms

s-2.jpg

s-2.jpg

101 ms

s-3.jpg

s-3.jpg

100 ms

s-4.jpg

s-4.jpg

102 ms

s-5.jpg

s-5.jpg

104 ms

s-6.jpg

s-6.jpg

101 ms

s-7.jpg

s-7.jpg

125 ms

s-8.jpg

s-8.jpg

120 ms

s-9.jpg

s-9.jpg

115 ms

s-10.jpg

s-10.jpg

176 ms

s-11.jpg

s-11.jpg

162 ms

s-12.jpg

s-12.jpg

162 ms

s-13.jpg

s-13.jpg

161 ms

s-14.jpg

s-14.jpg

162 ms

border.jpg

border.jpg

163 ms

frontbg2.jpg

frontbg2.jpg

175 ms

Asterio_2020.jpg

Asterio_2020.jpg

203 ms

view.jpg

view.jpg

167 ms

tinsa2009.PNG

tinsa2009.PNG

193 ms

Asterio2017FrontVideo.PNG

Asterio2017FrontVideo.PNG

204 ms

line01.gif

line01.gif

194 ms

Gitsawe.aspx

Gitsawe.aspx

160 ms

marker1.jpg

marker1.jpg

189 ms

carousel_prev.png

carousel_prev.png

111 ms

carousel_next.png

carousel_next.png

135 ms

carousel_item.png

carousel_item.png

135 ms

ui-bg_highlight-hard_100_f2f5f7_1x100.png

ui-bg_highlight-hard_100_f2f5f7_1x100.png

134 ms

ui-icons_72a7cf_256x240.png

ui-icons_72a7cf_256x240.png

133 ms

all.js

all.js

25 ms

back_to.jpg

back_to.jpg

26 ms

feedback.php

feedback.php

81 ms

pR4GxpoX2AR.css

pR4GxpoX2AR.css

26 ms

TRQl3HaQZeb.css

TRQl3HaQZeb.css

30 ms

Accessibility Review

saintmaryvancouver.org accessibility score

84

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

High

<object> elements do not have alternate text

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

saintmaryvancouver.org best practices score

58

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

Browser errors were logged to the console

SEO Factors

saintmaryvancouver.org SEO score

62

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

High

Document uses plugins

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

saintmaryvancouver.org

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