Tools & Wizards About Us
epc.org screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

epc.org

EPC | A Global Movement of Evangelical Presbyterian Churches

Page Load Speed

3.5 sec in total

First Response

162 ms

Resources Loaded

3.2 sec

Page Rendered

149 ms

epc.org screenshot

About Website

Welcome to epc.org homepage info - get ready to check EPC best content for United States right away, or after learning these important things about epc.org

Visit epc.org

Key Findings

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

epc.org performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value470 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.771

5/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

epc.org

162 ms

stylesheet0.635686511501270000.css

20 ms

stylesheet34.635215985442030000.css

31 ms

stylesheet42.634977660432400000.css

607 ms

stylesheet46.635811254268000000.css

42 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 68% of them (47 requests) were addressed to the original Epc.org, 12% (8 requests) were made to Google.com and 7% (5 requests) were made to Api.blackbaud.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Epc.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 381.8 kB (29%)

Content Size

1.3 MB

After Optimization

939.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Epc.org main page is 1.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. 65% of websites need less resources to load. Images take 730.7 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 30.3 kB

  • Original 41.2 kB
  • After minification 40.8 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 30.3 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 25.1 kB

  • Original 730.7 kB
  • After minification 705.7 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. EPC images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 287.3 kB

  • Original 499.0 kB
  • After minification 451.7 kB
  • After compression 211.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 287.3 kB or 58% of the original size.

CSS Optimization

-78%

Potential reduce by 39.2 kB

  • Original 50.2 kB
  • After minification 45.0 kB
  • After compression 11.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. Epc.org needs all CSS files to be minified and compressed as it can save up to 39.2 kB or 78% of the original size.

Requests Breakdown

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

Requests Now

61

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

epc.org

epc.org

162 ms

stylesheet0.635686511501270000.css

stylesheet0.635686511501270000.css

20 ms

stylesheet34.635215985442030000.css

stylesheet34.635215985442030000.css

31 ms

stylesheet42.634977660432400000.css

stylesheet42.634977660432400000.css

607 ms

stylesheet46.635811254268000000.css

stylesheet46.635811254268000000.css

42 ms

IE8Menu.css

IE8Menu.css

38 ms

WebResource.axd

WebResource.axd

45 ms

BBAPI-min.js

BBAPI-min.js

45 ms

Bbnccore-min.js

Bbnccore-min.js

69 ms

jquery.min.js

jquery.min.js

37 ms

jquery-ui.min.js

jquery-ui.min.js

52 ms

jquery.validate.js

jquery.validate.js

54 ms

additional-methods.js

additional-methods.js

65 ms

jquery.maskedinput-1.1.4.js

jquery.maskedinput-1.1.4.js

57 ms

EventCalendarPrinter.js

EventCalendarPrinter.js

60 ms

wz_tooltip.js

wz_tooltip.js

77 ms

tip_centerwindow.js

tip_centerwindow.js

74 ms

tip_followscroll.js

tip_followscroll.js

75 ms

ScriptResource.axd

ScriptResource.axd

89 ms

ScriptResource.axd

ScriptResource.axd

78 ms

webkit.js

webkit.js

87 ms

document.doc

document.doc

90 ms

document.doc

document.doc

1628 ms

font-awesome.min.css

font-awesome.min.css

5 ms

document.doc

document.doc

93 ms

EPClogo2015.png

EPClogo2015.png

80 ms

HomePageBottomTabWorship.jpg

HomePageBottomTabWorship.jpg

44 ms

HomePageBottomTabSteeple.jpg

HomePageBottomTabSteeple.jpg

64 ms

HomePageBottomTabCalendar.jpg

HomePageBottomTabCalendar.jpg

44 ms

facebook.png

facebook.png

43 ms

flickr.png

flickr.png

63 ms

google.png

google.png

62 ms

linkedin.png

linkedin.png

63 ms

pinterest.png

pinterest.png

62 ms

twitter-2.png

twitter-2.png

64 ms

youtube.png

youtube.png

73 ms

EPCseal2015.png

EPCseal2015.png

71 ms

document.doc

document.doc

538 ms

document.doc

document.doc

1552 ms

document.doc

document.doc

1037 ms

cse.js

cse.js

51 ms

stylesheet36.634669196126930000.css

stylesheet36.634669196126930000.css

519 ms

document.doc

document.doc

50 ms

bbi

bbi

43 ms

ga.js

ga.js

35 ms

12 ms

navArrow.png

navArrow.png

46 ms

jsapi

jsapi

38 ms

__utm.gif

__utm.gif

16 ms

bbi.min.css

bbi.min.css

8 ms

bbnc-carousel.custom-part.min.js

bbnc-carousel.custom-part.min.js

14 ms

default+en.css

default+en.css

13 ms

default.css

default.css

50 ms

default+en.I.js

default+en.I.js

16 ms

index.php

index.php

43 ms

default.css

default.css

131 ms

async-ads.js

async-ads.js

99 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

46 ms

small-logo.png

small-logo.png

73 ms

search_box_icon.png

search_box_icon.png

74 ms

clear.gif

clear.gif

72 ms

HomePageRotatorGA2016_12-370.jpg

HomePageRotatorGA2016_12-370.jpg

207 ms

HomePageRotator1BLUE-unity12-370.jpg

HomePageRotator1BLUE-unity12-370.jpg

180 ms

HomePageRotator2BLUE-liberty12-370.jpg

HomePageRotator2BLUE-liberty12-370.jpg

230 ms

HomePageRotator3BLUE-charity12-370.jpg

HomePageRotator3BLUE-charity12-370.jpg

200 ms

HomePageRotator4BLUE-truth12-370.jpg

HomePageRotator4BLUE-truth12-370.jpg

190 ms

left_arrow.png

left_arrow.png

33 ms

right_arrow.png

right_arrow.png

518 ms

iubenda.js

iubenda.js

9 ms

Accessibility Review

epc.org accessibility score

77

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

ARIA IDs are not unique

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.

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

Links do not have a discernible name

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

epc.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

epc.org SEO score

85

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

epc.org

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