Tools & Wizards About Us
challengerpark.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

challengerpark.com

All Inclusive Barrier Free Play |Calgary| CalgaryRotaryChallengerPark

Page Load Speed

2.1 sec in total

First Response

130 ms

Resources Loaded

1.9 sec

Page Rendered

63 ms

challengerpark.com screenshot

About Website

Click here to check amazing Challenger Park content. Otherwise, check out these important facts you probably never knew about challengerpark.com

Calgary Rotary Challenger Park is an all inclusive barrier free park for people of all abilities to enjoy sports fields, meeting rooms, basketball and tennis courts. Located in Calgary. CalgaryRotaryC...

Visit challengerpark.com

Key Findings

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

Performance Metrics

challengerpark.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

www.challengerpark.com

130 ms

minified.js

44 ms

focus-within-polyfill.js

88 ms

polyfill.min.js

41 ms

thunderbolt-commons.b70ee867.bundle.min.js

151 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Challengerpark.com, 39% (15 requests) were made to Static.parastorage.com and 32% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (632 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 525.6 kB (54%)

Content Size

969.5 kB

After Optimization

443.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Challengerpark.com main page is 969.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. HTML takes 587.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 458.3 kB

  • Original 587.0 kB
  • After minification 585.2 kB
  • After compression 128.6 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 458.3 kB or 78% of the original size.

Image Optimization

-25%

Potential reduce by 19.2 kB

  • Original 78.2 kB
  • After minification 59.0 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. Obviously, Challenger Park needs image optimization as it can save up to 19.2 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-16%

Potential reduce by 48.1 kB

  • Original 304.3 kB
  • After minification 304.3 kB
  • After compression 256.2 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 48.1 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (29%)

Requests Now

34

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.challengerpark.com

www.challengerpark.com

130 ms

minified.js

minified.js

44 ms

focus-within-polyfill.js

focus-within-polyfill.js

88 ms

polyfill.min.js

polyfill.min.js

41 ms

thunderbolt-commons.b70ee867.bundle.min.js

thunderbolt-commons.b70ee867.bundle.min.js

151 ms

main.317ed945.bundle.min.js

main.317ed945.bundle.min.js

153 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

149 ms

lodash.min.js

lodash.min.js

132 ms

react.production.min.js

react.production.min.js

150 ms

react-dom.production.min.js

react-dom.production.min.js

154 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

154 ms

CRCP.jpeg

CRCP.jpeg

348 ms

bundle.min.js

bundle.min.js

70 ms

handshake.png

handshake.png

452 ms

2a683d_a0681e73ca1e42bf982def60d2827ae4~mv2.png

2a683d_a0681e73ca1e42bf982def60d2827ae4~mv2.png

512 ms

2a683d_9904a89c18b64467875fb7ce92f94d22~mv2.png

2a683d_9904a89c18b64467875fb7ce92f94d22~mv2.png

535 ms

2a683d_86f45cdbc01a4478b2edab9abf93af60~mv2.png

2a683d_86f45cdbc01a4478b2edab9abf93af60~mv2.png

519 ms

2a683d_21e6d73ab7b544b2801c10eec1465b29~mv2.png

2a683d_21e6d73ab7b544b2801c10eec1465b29~mv2.png

632 ms

TLM%20white.png

TLM%20white.png

525 ms

136 ms

127 ms

131 ms

131 ms

129 ms

122 ms

167 ms

167 ms

159 ms

161 ms

158 ms

155 ms

deprecation-en.v5.html

deprecation-en.v5.html

6 ms

bolt-performance

bolt-performance

23 ms

deprecation-style.v5.css

deprecation-style.v5.css

5 ms

right-arrow.svg

right-arrow.svg

15 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

6 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

6 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

6 ms

Accessibility Review

challengerpark.com accessibility score

87

Accessibility Issues

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

challengerpark.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

challengerpark.com SEO score

92

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

challengerpark.com

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