Tools & Wizards About Us
wsbc.org screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

wsbc.org

Home - West Shore Baptist Church

Page Load Speed

5.9 sec in total

First Response

1.1 sec

Resources Loaded

4.2 sec

Page Rendered

654 ms

wsbc.org screenshot

About Website

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

West Shore Baptist Church exists to make disciples who believe our God and live out His word, belong to one another in community, bridge the Gospel to those who do not yet know Christ, and become more...

Visit wsbc.org

Key Findings

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

Performance Metrics

wsbc.org performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value71.6 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.062

97/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

www.wsbc.org

1089 ms

font-awesome.min.css

477 ms

jquery-3.7.1.min.js

159 ms

jquery-ui.min.js

649 ms

jquery-ui.min.css

499 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 8% of them (9 requests) were addressed to the original Wsbc.org, 25% (29 requests) were made to Fonts.googleapis.com and 24% (28 requests) were made to S5.radiantwebtools.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source S5.radiantwebtools.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.5 MB (15%)

Content Size

16.3 MB

After Optimization

13.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wsbc.org main page is 16.3 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. 55% of websites need less resources to load. Images take 15.6 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 19.7 kB

  • Original 25.3 kB
  • After minification 25.0 kB
  • After compression 5.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 19.7 kB or 78% of the original size.

Image Optimization

-15%

Potential reduce by 2.3 MB

  • Original 15.6 MB
  • After minification 13.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. Obviously, Wsbc needs image optimization as it can save up to 2.3 MB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-30%

Potential reduce by 121.0 kB

  • Original 402.6 kB
  • After minification 397.5 kB
  • After compression 281.6 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 121.0 kB or 30% of the original size.

CSS Optimization

-4%

Potential reduce by 9.2 kB

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

Requests Breakdown

Number of requests can be reduced by 82 (81%)

Requests Now

101

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wsbc. 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 65 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.wsbc.org

www.wsbc.org

1089 ms

font-awesome.min.css

font-awesome.min.css

477 ms

jquery-3.7.1.min.js

jquery-3.7.1.min.js

159 ms

jquery-ui.min.js

jquery-ui.min.js

649 ms

jquery-ui.min.css

jquery-ui.min.css

499 ms

jquery.scrollTo.min.js

jquery.scrollTo.min.js

502 ms

jquery.tagit.custom.js

jquery.tagit.custom.js

506 ms

jquery.tagit.css

jquery.tagit.css

513 ms

select2.min.js

select2.min.js

560 ms

select2.min.css

select2.min.css

591 ms

jquery.cookie.js

jquery.cookie.js

591 ms

popup.js

popup.js

596 ms

main.js

main.js

606 ms

util.js

util.js

643 ms

style.css

style.css

241 ms

aurora-variables.css

aurora-variables.css

680 ms

aurora.css

aurora.css

683 ms

aurora-modules.css

aurora-modules.css

689 ms

aurora-dialog.css

aurora-dialog.css

698 ms

d142105c.js

d142105c.js

44 ms

screen.css

screen.css

485 ms

main.js

main.js

492 ms

content.css

content.css

725 ms

content.js

content.js

729 ms

mightyslider.css

mightyslider.css

490 ms

mightyslider.animate.css

mightyslider.animate.css

490 ms

animate.min.css

animate.min.css

495 ms

screen.css

screen.css

522 ms

slider.js

slider.js

573 ms

tweenlite.js

tweenlite.js

667 ms

mightyslider.js

mightyslider.js

1392 ms

mightyslider.animate.plugin.min.js

mightyslider.animate.plugin.min.js

582 ms

screen.css

screen.css

585 ms

screen.css

screen.css

1103 ms

t6592.css

t6592.css

382 ms

jquery.browser.js

jquery.browser.js

767 ms

classic-10_7.css

classic-10_7.css

29 ms

mc-validate.js

mc-validate.js

52 ms

loader.js

loader.js

21 ms

css

css

30 ms

woff.css

woff.css

29 ms

style.css

style.css

178 ms

style.css

style.css

91 ms

style.css

style.css

92 ms

style.css

style.css

90 ms

style.css

style.css

181 ms

style.css

style.css

180 ms

style.css

style.css

182 ms

style.css

style.css

269 ms

style.css

style.css

271 ms

style.css

style.css

274 ms

style.css

style.css

274 ms

style.css

style.css

360 ms

style.css

style.css

364 ms

style.css

style.css

366 ms

style.css

style.css

365 ms

animate.min.css

animate.min.css

549 ms

css

css

18 ms

css

css

23 ms

css

css

24 ms

css

css

25 ms

css

css

25 ms

css

css

26 ms

css

css

34 ms

css

css

39 ms

css

css

39 ms

css

css

40 ms

css

css

42 ms

css

css

41 ms

css

css

52 ms

css

css

54 ms

css

css

56 ms

css

css

54 ms

css

css

58 ms

css

css

56 ms

css

css

68 ms

css

css

73 ms

css

css

69 ms

css

css

95 ms

css

css

71 ms

css

css

75 ms

css

css

84 ms

css

css

86 ms

css

css

88 ms

css

css

87 ms

west_short_updated2.png

west_short_updated2.png

182 ms

ABOUT_US.png

ABOUT_US.png

863 ms

NEXT_STEPS.png

NEXT_STEPS.png

848 ms

SERMONS.png

SERMONS.png

1060 ms

powered_by_radiant.png

powered_by_radiant.png

260 ms

font

font

74 ms

font

font

89 ms

font

font

69 ms

font

font

73 ms

font

font

73 ms

font

font

79 ms

font

font

79 ms

font

font

105 ms

font

font

79 ms

font

font

79 ms

font

font

79 ms

font

font

78 ms

font

font

85 ms

font

font

156 ms

font

font

201 ms

font

font

204 ms

font

font

140 ms

font

font

151 ms

font

font

187 ms

font

font

149 ms

font

font

270 ms

font

font

214 ms

font

font

275 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

263 ms

Page_1.png

Page_1.png

1210 ms

8AAnjaY2BgYGQAghu7bvGC6MeKj8KgdBoATRYHAwA=

8AAnjaY2BgYGQAghu7bvGC6MeKj8KgdBoATRYHAwA=

2 ms

Page_2.png

Page_2.png

1219 ms

Accessibility Review

wsbc.org accessibility score

87

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

wsbc.org best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

wsbc.org SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

wsbc.org

Open Graph data is detected on the main page of Wsbc. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: