Tools & Wizards About Us
stjameswv.org screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

stjameswv.org

St. James the Greater Church

Page Load Speed

3.1 sec in total

First Response

27 ms

Resources Loaded

2 sec

Page Rendered

1.1 sec

stjameswv.org screenshot

About Website

Click here to check amazing St James Wv content for United States. Otherwise, check out these important facts you probably never knew about stjameswv.org

St. James the Greater Church - Home page

Visit stjameswv.org

Key Findings

We analyzed Stjameswv.org page load time and found that the first response time was 27 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

stjameswv.org performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value14.3 s

0/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value1,100 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.44

21/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

stjameswv.org

27 ms

stjameswv.org

55 ms

www.stjameswv.org

462 ms

foundation-icons.css

15 ms

main.css

76 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 8% of them (7 requests) were addressed to the original Stjameswv.org, 39% (34 requests) were made to Uploads.weconnect.com and 11% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Uploads.weconnect.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 99.8 kB (1%)

Content Size

8.1 MB

After Optimization

8.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stjameswv.org main page is 8.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. 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 7.7 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 50.0 kB

  • Original 64.4 kB
  • After minification 63.3 kB
  • After compression 14.4 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 50.0 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 49.4 kB

  • Original 7.7 MB
  • After minification 7.6 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. St James Wv images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 184 B

  • Original 320.0 kB
  • After minification 320.0 kB
  • After compression 319.8 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

-0%

Potential reduce by 184 B

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

Requests Breakdown

Number of requests can be reduced by 26 (34%)

Requests Now

77

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stjameswv.org

stjameswv.org

27 ms

stjameswv.org

stjameswv.org

55 ms

www.stjameswv.org

www.stjameswv.org

462 ms

foundation-icons.css

foundation-icons.css

15 ms

main.css

main.css

76 ms

splide.css

splide.css

90 ms

jquery-ui-smoothness.css

jquery-ui-smoothness.css

95 ms

css

css

31 ms

element.js

element.js

50 ms

after-head.js

after-head.js

129 ms

email-decode.min.js

email-decode.min.js

17 ms

before-body.js

before-body.js

127 ms

splide.js

splide.js

92 ms

jquery.ui.js

jquery.ui.js

92 ms

print.css

print.css

475 ms

gpt.js

gpt.js

386 ms

gtm.js

gtm.js

355 ms

wahixs46agxdsazfp1g0de0jn7.png

wahixs46agxdsazfp1g0de0jn7.png

578 ms

page.php

page.php

505 ms

potw-vert.html

potw-vert.html

544 ms

analytics.js

analytics.js

265 ms

jxnczv0guxf6dykyjahgcqqk3xf.jpg

jxnczv0guxf6dykyjahgcqqk3xf.jpg

443 ms

qnp61i3l8omfw8fthrr0ccyk1rf.jpg

qnp61i3l8omfw8fthrr0ccyk1rf.jpg

442 ms

ej5q6yv062mwmotes671nthrejf.jpg

ej5q6yv062mwmotes671nthrejf.jpg

689 ms

pep8p26scxtmzb3obbr176va4hf.jpg

pep8p26scxtmzb3obbr176va4hf.jpg

443 ms

mlb6829oxhr4zavre7dokr1pjkl.png

mlb6829oxhr4zavre7dokr1pjkl.png

344 ms

iah46vferko5pu0ykjgsc8iuwil.png

iah46vferko5pu0ykjgsc8iuwil.png

429 ms

shxgpcnu3qqvxbbgrcgceufo8ul.png

shxgpcnu3qqvxbbgrcgceufo8ul.png

562 ms

xbpnlpkc1f94xwc5pw2hvu90bgl.png

xbpnlpkc1f94xwc5pw2hvu90bgl.png

562 ms

dngaf89f7ow2naawpln2fro304l.png

dngaf89f7ow2naawpln2fro304l.png

561 ms

as8016wgwpy5o3bzp6r69tt7oll.png

as8016wgwpy5o3bzp6r69tt7oll.png

561 ms

joieov9rl971drg2nrsuicm8upl.png

joieov9rl971drg2nrsuicm8upl.png

693 ms

w9btemzgqhyeusv1jp9nbyvy6fl.jpg

w9btemzgqhyeusv1jp9nbyvy6fl.jpg

762 ms

pryt2ar3h75q5c159k4agel6gzl.png

pryt2ar3h75q5c159k4agel6gzl.png

694 ms

s30ykoadj80994qcjixtxq3vcil.png

s30ykoadj80994qcjixtxq3vcil.png

738 ms

gb19g61rze834idkqxrhx2ha4hl.png

gb19g61rze834idkqxrhx2ha4hl.png

694 ms

13i2g86m7v0wypxzuorrm9bisyl.jpg

13i2g86m7v0wypxzuorrm9bisyl.jpg

738 ms

vbrnh2f1vf5cblm2m9b69qfdw9l.jpg

vbrnh2f1vf5cblm2m9b69qfdw9l.jpg

768 ms

6826alax6oc2th8ew2adgej2m5l.jpg

6826alax6oc2th8ew2adgej2m5l.jpg

804 ms

fpsao0n6dfu2aiu4i7q24xrr08l.png

fpsao0n6dfu2aiu4i7q24xrr08l.png

745 ms

6mxhsu1btr4rtguoota8kq0cqkl.png

6mxhsu1btr4rtguoota8kq0cqkl.png

748 ms

quoa7t4sspk56d5wdapv7u4f7bl.png

quoa7t4sspk56d5wdapv7u4f7bl.png

745 ms

1sj0n271aeq5cbz33h6oa1gpq8l.jpg

1sj0n271aeq5cbz33h6oa1gpq8l.jpg

930 ms

wpcnyrn7ytsow8g0887kk74smul.png

wpcnyrn7ytsow8g0887kk74smul.png

817 ms

8zn3z8qki9ru965g2rt0f0zvpml.jpg

8zn3z8qki9ru965g2rt0f0zvpml.jpg

880 ms

vr6eq3moutra58jx0mpsz7ul31l.png

vr6eq3moutra58jx0mpsz7ul31l.png

818 ms

dcw52p0d4kqxpximhv9sgty3fbl.png

dcw52p0d4kqxpximhv9sgty3fbl.png

876 ms

4x9p3ucbkbffmdyqqrhznt5axdl.jpg

4x9p3ucbkbffmdyqqrhznt5axdl.jpg

837 ms

h7ged6tnp2kpkm93kng50et1vgl.jpg

h7ged6tnp2kpkm93kng50et1vgl.jpg

938 ms

4h40t88um9742stai0pbn256aal.jpg

4h40t88um9742stai0pbn256aal.jpg

900 ms

7hhd80f72xs8k0u510s8kbw0dtl.jpg

7hhd80f72xs8k0u510s8kbw0dtl.jpg

1047 ms

qgsb1wd0wbktljhm2i2iz76vt3l.jpg

qgsb1wd0wbktljhm2i2iz76vt3l.jpg

1017 ms

amw8xd8qjxf16lxvirx7si2t0il.jpg

amw8xd8qjxf16lxvirx7si2t0il.jpg

1033 ms

lodbyxk19e3ql1om5puy2727axl.png

lodbyxk19e3ql1om5puy2727axl.png

1072 ms

lpi-logo-grey-small.png

lpi-logo-grey-small.png

193 ms

tDbI2oqRg1oM3QBjjcaDkOr9rAA.ttf

tDbI2oqRg1oM3QBjjcaDkOr9rAA.ttf

237 ms

tDbV2oqRg1oM3QBjjcaDkOJGiRD7OwQ.ttf

tDbV2oqRg1oM3QBjjcaDkOJGiRD7OwQ.ttf

238 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

295 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

340 ms

tDbK2oqRg1oM3QBjjcaDkOr4nAfcGw.ttf

tDbK2oqRg1oM3QBjjcaDkOr4nAfcGw.ttf

341 ms

tDbX2oqRg1oM3QBjjcaDkOr4lLz5CwOnTQ.ttf

tDbX2oqRg1oM3QBjjcaDkOr4lLz5CwOnTQ.ttf

341 ms

foundation-icons.woff

foundation-icons.woff

382 ms

loader.gif

loader.gif

55 ms

pubads_impl.js

pubads_impl.js

207 ms

ppub_config

ppub_config

320 ms

collect

collect

88 ms

collect

collect

148 ms

collect

collect

129 ms

R4Igq3sWMG5.css

R4Igq3sWMG5.css

103 ms

hWUNSHlPpQ-.js

hWUNSHlPpQ-.js

222 ms

teTZ2tZqwkq.js

teTZ2tZqwkq.js

250 ms

ru8zNtgW1u3.js

ru8zNtgW1u3.js

314 ms

U_siWb4c7L_.js

U_siWb4c7L_.js

319 ms

p55HfXW__mM.js

p55HfXW__mM.js

313 ms

NsQyZQ9rSHN.js

NsQyZQ9rSHN.js

319 ms

js

js

61 ms

css

css

42 ms

formed-blue-small.png

formed-blue-small.png

56 ms

twof-generic.jpg

twof-generic.jpg

305 ms

collect

collect

265 ms

js

js

166 ms

272669747_1629768457358890_6928863362296188970_n.jpg

272669747_1629768457358890_6928863362296188970_n.jpg

83 ms

326283823_1319745568808258_7251484196128498983_n.jpg

326283823_1319745568808258_7251484196128498983_n.jpg

82 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

69 ms

ga-audiences

ga-audiences

107 ms

HoMN5oU548h.js

HoMN5oU548h.js

6 ms

6zg-_OZPqub.js

6zg-_OZPqub.js

14 ms

Accessibility Review

stjameswv.org accessibility score

91

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

stjameswv.org SEO score

84

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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

stjameswv.org

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