Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

discoverychurchelgin.com

Discovery Church Elgin | A Church Where Change Takes Place | HOME

Page Load Speed

2.7 sec in total

First Response

194 ms

Resources Loaded

1.9 sec

Page Rendered

615 ms

discoverychurchelgin.com screenshot

About Website

Visit discoverychurchelgin.com now to see the best up-to-date Discovery Church Elgin content and also check out these interesting facts you probably never knew about discoverychurchelgin.com

Sunday In Person Service - Sunday  10:30am In Person And Live Streamfacebook Page Discovery Church Elgin+ Our Youtube Page Discovery Church, Elgin

Visit discoverychurchelgin.com

Key Findings

We analyzed Discoverychurchelgin.com page load time and found that the first response time was 194 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

discoverychurchelgin.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value27.8 s

0/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value550 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

discoverychurchelgin.com

194 ms

discoverychurchelgin.com

324 ms

application-2bcce868e9ecfb6e823536cc735d148692d206c63f81a06c7f037be829b462a9.css

42 ms

base-8cd9597679be4988227a11fee8f2ecb4007aaf3efa751ec7a117ffe2d4aafb32.css

56 ms

application-73c579df8ac31110f0b4fce5da584fa873208a32a374563cc27afe33fca3c7fc.js

67 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Discoverychurchelgin.com, 44% (17 requests) were made to S3.amazonaws.com and 13% (5 requests) were made to Cdn.cloversites.com. The less responsive or slowest element that took the longest time to load (983 ms) relates to the external source Google-analytics.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 189.8 kB (5%)

Content Size

3.7 MB

After Optimization

3.6 MB

In fact, the total size of Discoverychurchelgin.com main page is 3.7 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 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 189.5 kB

  • Original 212.4 kB
  • After minification 209.3 kB
  • After compression 22.8 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 189.5 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 124 B

  • Original 3.1 MB
  • After minification 3.1 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. Discovery Church Elgin images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 336.6 kB
  • After minification 336.6 kB
  • After compression 336.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 32 B

  • Original 123.5 kB
  • After minification 123.5 kB
  • After compression 123.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. Discoverychurchelgin.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (28%)

Requests Now

29

After Optimization

21

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

Accessibility Review

discoverychurchelgin.com accessibility score

71

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

discoverychurchelgin.com 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

High

Missing source maps for large first-party JavaScript

SEO Factors

discoverychurchelgin.com SEO score

91

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Discoverychurchelgin.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Discoverychurchelgin.com 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

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