Tools & Wizards About Us
firstchurchtoronto.com screenshot

Report Summary

  • 0

    Performance

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

firstchurchtoronto.com

First Church of Christ Scientist Toronto

Page Load Speed

1.7 sec in total

First Response

222 ms

Resources Loaded

1.4 sec

Page Rendered

78 ms

firstchurchtoronto.com screenshot

About Website

Welcome to firstchurchtoronto.com homepage info - get ready to check First Church Toronto best content right away, or after learning these important things about firstchurchtoronto.com

First Church of Christ Scientist, Toronto

Visit firstchurchtoronto.com

Key Findings

We analyzed Firstchurchtoronto.com page load time and found that the first response time was 222 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

firstchurchtoronto.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

firstchurchtoronto.com

222 ms

www.christiansciencetoronto.com

462 ms

jquery.min.js

7 ms

style.min.css

72 ms

styles.css

81 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Firstchurchtoronto.com, 74% (20 requests) were made to Christiansciencetoronto.com and 15% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (462 ms) relates to the external source Christiansciencetoronto.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 403.2 kB (35%)

Content Size

1.2 MB

After Optimization

763.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Firstchurchtoronto.com main page is 1.2 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. 25% of websites need less resources to load. Images take 625.4 kB which makes up the majority of the site volume.

HTML Optimization

-54%

Potential reduce by 460 B

  • Original 845 B
  • After minification 841 B
  • After compression 385 B

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 460 B or 54% of the original size.

Image Optimization

-1%

Potential reduce by 5.1 kB

  • Original 625.4 kB
  • After minification 620.3 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. First Church Toronto images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 109.2 kB

  • Original 197.5 kB
  • After minification 197.5 kB
  • After compression 88.3 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 109.2 kB or 55% of the original size.

CSS Optimization

-84%

Potential reduce by 288.6 kB

  • Original 343.5 kB
  • After minification 326.1 kB
  • After compression 54.9 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. Firstchurchtoronto.com needs all CSS files to be minified and compressed as it can save up to 288.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (84%)

Requests Now

25

After Optimization

4

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

firstchurchtoronto.com

firstchurchtoronto.com

222 ms

www.christiansciencetoronto.com

www.christiansciencetoronto.com

462 ms

jquery.min.js

jquery.min.js

7 ms

style.min.css

style.min.css

72 ms

styles.css

styles.css

81 ms

style.min.css

style.min.css

82 ms

Rich-Web-Slider-Widget.css

Rich-Web-Slider-Widget.css

81 ms

richwebicons.css

richwebicons.css

101 ms

bootstrap.min.css

bootstrap.min.css

150 ms

font-awesome.min.css

font-awesome.min.css

86 ms

jquery.bxslider.css

jquery.bxslider.css

97 ms

jquery.fancybox.css

jquery.fancybox.css

97 ms

style.css

style.css

102 ms

style.css

style.css

108 ms

pvc.min.css

pvc.min.css

116 ms

jquery.min.js

jquery.min.js

161 ms

jquery-migrate.min.js

jquery-migrate.min.js

125 ms

underscore.min.js

underscore.min.js

124 ms

backbone.min.js

backbone.min.js

129 ms

pvc.backbone.min.js

pvc.backbone.min.js

139 ms

core.min.js

core.min.js

147 ms

css

css

41 ms

css

css

47 ms

css

css

48 ms

css

css

48 ms

logo.jpg

logo.jpg

65 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQVIT9d4cw.ttf

28 ms

Accessibility Review

firstchurchtoronto.com accessibility score

67

Accessibility Issues

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

Best Practices

firstchurchtoronto.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

firstchurchtoronto.com SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

firstchurchtoronto.com

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