Tools & Wizards About Us
stthomasparishnc.org screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

stthomasparishnc.org

St. Thomas Episcopal Church

Page Load Speed

964 ms in total

First Response

39 ms

Resources Loaded

621 ms

Page Rendered

304 ms

stthomasparishnc.org screenshot

About Website

Click here to check amazing St Thomas Parishnc content. Otherwise, check out these important facts you probably never knew about stthomasparishnc.org

Visit stthomasparishnc.org

Key Findings

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

stthomasparishnc.org performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value440 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.209

60/100

15%

TTI (Time to Interactive)

Value11.9 s

16/100

10%

Network Requests Diagram

stthomasparishnc.org

39 ms

stthomasparishnc.org

67 ms

style.min.css

21 ms

style-coblocks-1.css

28 ms

style-coblocks-extensions.css

85 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 90% of them (62 requests) were addressed to the original Stthomasparishnc.org, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to B2t.4f1.myftpupload.com. The less responsive or slowest element that took the longest time to load (255 ms) relates to the external source B2t.4f1.myftpupload.com.

Page Optimization Overview & Recommendations

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

Content Size

4.6 MB

After Optimization

4.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 40.6 kB

  • Original 51.5 kB
  • After minification 47.5 kB
  • After compression 10.9 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 40.6 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 6.1 kB

  • Original 4.4 MB
  • After minification 4.4 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 Thomas Parishnc images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 8.6 kB

  • Original 83.3 kB
  • After minification 82.8 kB
  • After compression 74.7 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

-5%

Potential reduce by 4.2 kB

  • Original 82.7 kB
  • After minification 80.7 kB
  • After compression 78.5 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. Stthomasparishnc.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 42 (66%)

Requests Now

64

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stthomasparishnc.org

stthomasparishnc.org

39 ms

stthomasparishnc.org

stthomasparishnc.org

67 ms

style.min.css

style.min.css

21 ms

style-coblocks-1.css

style-coblocks-1.css

28 ms

style-coblocks-extensions.css

style-coblocks-extensions.css

85 ms

style-coblocks-animation.css

style-coblocks-animation.css

50 ms

ft-carousel.css

ft-carousel.css

38 ms

ft-portfolio.css

ft-portfolio.css

40 ms

prettyPhoto.css

prettyPhoto.css

46 ms

ft-sermons.css

ft-sermons.css

40 ms

ft-shortcodes.css

ft-shortcodes.css

43 ms

ft-slider.css

ft-slider.css

54 ms

pagenavi-css.css

pagenavi-css.css

51 ms

style.min.css

style.min.css

61 ms

latest.css

latest.css

67 ms

style.css

style.css

65 ms

css

css

38 ms

css

css

55 ms

jquery.min.js

jquery.min.js

66 ms

jquery-migrate.min.js

jquery-migrate.min.js

68 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

78 ms

custom.js

custom.js

98 ms

launchprettyphoto.js

launchprettyphoto.js

76 ms

lightbox.js

lightbox.js

97 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

97 ms

js

js

112 ms

coblocks-animation.js

coblocks-animation.js

111 ms

tiny-swiper.js

tiny-swiper.js

135 ms

coblocks-tinyswiper-initializer.js

coblocks-tinyswiper-initializer.js

133 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

133 ms

jquery.elastislide.js

jquery.elastislide.js

136 ms

thickbox.js

thickbox.js

137 ms

underscore-before.js

underscore-before.js

135 ms

underscore.min.js

underscore.min.js

138 ms

underscore-after.js

underscore-after.js

141 ms

shortcode.min.js

shortcode.min.js

140 ms

media-upload.min.js

media-upload.min.js

179 ms

jquery.tabify.js

jquery.tabify.js

141 ms

jquery.countdown.js

jquery.countdown.js

142 ms

menu.js

menu.js

143 ms

effects.js

effects.js

142 ms

St.-Thomas-Favicon.png

St.-Thomas-Favicon.png

131 ms

StThomasWebBackground.png

StThomasWebBackground.png

50 ms

St.-Thomas-Episcopal-Church.png

St.-Thomas-Episcopal-Church.png

39 ms

st.-Thomas-Church.jpg

st.-Thomas-Church.jpg

49 ms

St.-Thomas-Memorial-Garden.jpg

St.-Thomas-Memorial-Garden.jpg

48 ms

Glebe-House-scaled.jpg

Glebe-House-scaled.jpg

53 ms

20_39_19_309_New_Parish_Hall_Fotor_Fotor-scaled.jpg

20_39_19_309_New_Parish_Hall_Fotor_Fotor-scaled.jpg

61 ms

unnamed-3-scaled-e1611076426107.jpg

unnamed-3-scaled-e1611076426107.jpg

70 ms

carousel_bg.jpg

carousel_bg.jpg

64 ms

St-Thomas-Church-Desktop-1-e1610724602809.jpg

St-Thomas-Church-Desktop-1-e1610724602809.jpg

66 ms

DSC02489-scaled-e1610470041501.jpg

DSC02489-scaled-e1610470041501.jpg

69 ms

Palm-Sunday-scaled-e1640026058725.jpg

Palm-Sunday-scaled-e1640026058725.jpg

125 ms

custom_quote_bg.jpg

custom_quote_bg.jpg

125 ms

welcome-1-e1610559765337-300x258.jpg

welcome-1-e1610559765337-300x258.jpg

208 ms

Epis-Church-image-300x300.jpg

Epis-Church-image-300x300.jpg

215 ms

LuminaryNight-300x225.jpg

LuminaryNight-300x225.jpg

175 ms

Bonfire-Night-300x225.jpg

Bonfire-Night-300x225.jpg

151 ms

prev.png

prev.png

22 ms

next.png

next.png

21 ms

carousel_divider.png

carousel_divider.png

39 ms

Ycm2sZJORluHnXbIfmlR-w.woff

Ycm2sZJORluHnXbIfmlR-w.woff

81 ms

RWmMoKWR9v4ksMfaWd_JN9XFiaI.woff

RWmMoKWR9v4ksMfaWd_JN9XFiaI.woff

90 ms

loadingAnimation.gif

loadingAnimation.gif

30 ms

St.-Thomas-Favicon.png

St.-Thomas-Favicon.png

255 ms

ft_slider_bullet_a.png

ft_slider_bullet_a.png

19 ms

ft_slider_bullet.png

ft_slider_bullet.png

19 ms

prev.png

prev.png

17 ms

next.png

next.png

18 ms

Accessibility Review

stthomasparishnc.org accessibility score

85

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.

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

stthomasparishnc.org SEO score

82

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

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

stthomasparishnc.org

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