Tools & Wizards About Us
spcgreenville.org screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

spcgreenville.org

Second Presbyterian Church | Reaching Out, Folding In, Growing Up for the glory of God

Page Load Speed

3.2 sec in total

First Response

194 ms

Resources Loaded

2.6 sec

Page Rendered

368 ms

spcgreenville.org screenshot

About Website

Visit spcgreenville.org now to see the best up-to-date Spcgreenville content for United States and also check out these interesting facts you probably never knew about spcgreenville.org

Visit spcgreenville.org

Key Findings

We analyzed Spcgreenville.org page load time and found that the first response time was 194 ms and then it took 3 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

spcgreenville.org performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value3,250 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

spcgreenville.org

194 ms

spcgreenville.org

29 ms

all.min.css

7 ms

style.css

29 ms

style.min.css

59 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 39% of them (29 requests) were addressed to the original Spcgreenville.org, 24% (18 requests) were made to Web.sermonaudio.com and 11% (8 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Web.sermonaudio.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 262.4 kB (19%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Spcgreenville.org main page is 1.4 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 980.3 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 60.5 kB

  • Original 76.1 kB
  • After minification 75.1 kB
  • After compression 15.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. 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 60.5 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 68.4 kB

  • Original 980.3 kB
  • After minification 911.9 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. Spcgreenville images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 6.0 kB

  • Original 101.5 kB
  • After minification 101.5 kB
  • After compression 95.5 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

-55%

Potential reduce by 127.4 kB

  • Original 230.5 kB
  • After minification 230.4 kB
  • After compression 103.1 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. Spcgreenville.org needs all CSS files to be minified and compressed as it can save up to 127.4 kB or 55% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (75%)

Requests Now

59

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

spcgreenville.org

spcgreenville.org

194 ms

spcgreenville.org

spcgreenville.org

29 ms

all.min.css

all.min.css

7 ms

style.css

style.css

29 ms

style.min.css

style.min.css

59 ms

style.min.css

style.min.css

34 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

58 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

63 ms

email-subscribers-public.css

email-subscribers-public.css

35 ms

frontend.css

frontend.css

33 ms

css

css

73 ms

dashicons.min.css

dashicons.min.css

64 ms

ionicons.min.css

ionicons.min.css

73 ms

front-end.css

front-end.css

40 ms

style.css

style.css

52 ms

style-front.css

style-front.css

52 ms

ytprefs.min.css

ytprefs.min.css

54 ms

lity.min.css

lity.min.css

54 ms

jetpack.css

jetpack.css

66 ms

jquery.min.js

jquery.min.js

63 ms

jquery-migrate.min.js

jquery-migrate.min.js

62 ms

lity.min.js

lity.min.js

53 ms

ytprefs.min.js

ytprefs.min.js

56 ms

image-cdn.js

image-cdn.js

58 ms

email-subscribers-public.js

email-subscribers-public.js

63 ms

frontend.js

frontend.js

68 ms

hoverIntent.min.js

hoverIntent.min.js

61 ms

superfish.min.js

superfish.min.js

63 ms

superfish.args.min.js

superfish.args.min.js

63 ms

skip-links.min.js

skip-links.min.js

68 ms

menus.js

menus.js

63 ms

genesis-sample.js

genesis-sample.js

68 ms

fitvids.min.js

fitvids.min.js

68 ms

e-202435.js

e-202435.js

58 ms

analytics.js

analytics.js

157 ms

84dcca36f454deb7a2141ac00.js

84dcca36f454deb7a2141ac00.js

211 ms

a73649f57f193806aeca2cc47.js

a73649f57f193806aeca2cc47.js

237 ms

cropped-logo.png

cropped-logo.png

172 ms

home-hero.jpg

home-hero.jpg

146 ms

reftagger.js

reftagger.js

465 ms

Button-Logo.png

Button-Logo.png

167 ms

symbol-defs.svg

symbol-defs.svg

141 ms

CalvaryPresbyteryLogo.png

CalvaryPresbyteryLogo.png

143 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

159 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

173 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

198 ms

wlp2gwHKFkZgtmSR3NB0oRJfbwhW.ttf

wlp2gwHKFkZgtmSR3NB0oRJfbwhW.ttf

103 ms

wlppgwHKFkZgtmSR3NB0oRJX1C1GDNNV.ttf

wlppgwHKFkZgtmSR3NB0oRJX1C1GDNNV.ttf

104 ms

wlpogwHKFkZgtmSR3NB0oRJfajhRK_M.ttf

wlpogwHKFkZgtmSR3NB0oRJfajhRK_M.ttf

103 ms

wlprgwHKFkZgtmSR3NB0oRJfajDqDuNS_LA.ttf

wlprgwHKFkZgtmSR3NB0oRJfajDqDuNS_LA.ttf

104 ms

Flaticon.svg

Flaticon.svg

31 ms

Flaticon.woff

Flaticon.woff

164 ms

collect

collect

26 ms

1832 ms

1862 ms

1620 ms

cast_sender.js

cast_sender.js

16 ms

8292415266282.jpg

8292415266282.jpg

104 ms

OpenSans-Regular.1b0809d.ttf

OpenSans-Regular.1b0809d.ttf

56 ms

OpenSans-Light.ed41bed.ttf

OpenSans-Light.ed41bed.ttf

75 ms

OpenSans-SemiBold.a16d820.ttf

OpenSans-SemiBold.a16d820.ttf

68 ms

OpenSans-Bold.dbb97fd.ttf

OpenSans-Bold.dbb97fd.ttf

89 ms

OpenSans-Italic.20653d2.ttf

OpenSans-Italic.20653d2.ttf

89 ms

36d07a9.js

36d07a9.js

51 ms

38fa840.js

38fa840.js

53 ms

a38c858.js

a38c858.js

52 ms

0dc43ce.js

0dc43ce.js

66 ms

670f281.js

670f281.js

67 ms

0c45d77.js

0c45d77.js

67 ms

e526fbf.js

e526fbf.js

70 ms

fab413a.js

fab413a.js

72 ms

2541d64.js

2541d64.js

80 ms

e07663b.js

e07663b.js

87 ms

826241649465573.jpg

826241649465573.jpg

60 ms

826241650396941.jpg

826241650396941.jpg

47 ms

Accessibility Review

spcgreenville.org accessibility score

79

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

Buttons do not have an accessible name

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

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

Best Practices

spcgreenville.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

spcgreenville.org SEO score

79

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

spcgreenville.org

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