Tools & Wizards About Us

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

churchill.ca

Town of Churchill - Home

Page Load Speed

3.6 sec in total

First Response

56 ms

Resources Loaded

3.1 sec

Page Rendered

396 ms

About Website

Visit churchill.ca now to see the best up-to-date Churchill content and also check out these interesting facts you probably never knew about churchill.ca

Located on the shores of Hudson Bay, the Town of Churchill and the surrounding area are steeped in history as old as Canada. Archaeology in the area shows evidence of human presence dating back 4,000 ...

Visit churchill.ca

Key Findings

We analyzed Churchill.ca page load time and found that the first response time was 56 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

churchill.ca performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value22.7 s

0/100

25%

SI (Speed Index)

Value43.6 s

0/100

10%

TBT (Total Blocking Time)

Value1,420 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.211

59/100

15%

TTI (Time to Interactive)

Value23.7 s

1/100

10%

Network Requests Diagram

churchill.ca

56 ms

churchill.ca

182 ms

bootstrap.min.css

87 ms

font-awesome.min.css

50 ms

all.min.css

101 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 31% of them (36 requests) were addressed to the original Churchill.ca, 19% (22 requests) were made to Churchill.municipalwebsites.ca and 16% (18 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Churchill.municipalwebsites.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 672.0 kB (12%)

Content Size

5.7 MB

After Optimization

5.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Churchill.ca main page is 5.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 4.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 73.3 kB

  • Original 88.9 kB
  • After minification 69.6 kB
  • After compression 15.7 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. This page needs HTML code to be minified as it can gain 19.3 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 73.3 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 54.2 kB

  • Original 4.8 MB
  • After minification 4.7 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. Churchill images are well optimized though.

JavaScript Optimization

-38%

Potential reduce by 169.8 kB

  • Original 442.6 kB
  • After minification 349.9 kB
  • After compression 272.8 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 169.8 kB or 38% of the original size.

CSS Optimization

-82%

Potential reduce by 374.8 kB

  • Original 458.5 kB
  • After minification 389.2 kB
  • After compression 83.7 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. Churchill.ca needs all CSS files to be minified and compressed as it can save up to 374.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (61%)

Requests Now

84

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

churchill.ca accessibility score

72

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

churchill.ca best practices score

67

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

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

churchill.ca SEO score

90

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

Links do not have descriptive text

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 Churchill.ca 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 Churchill.ca 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 description is not detected on the main page of Churchill. 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: