Tools & Wizards About Us
challengerunner.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

challengerunner.com

Free Online Fitness Challenge Management System - ChallengeRunner

Page Load Speed

1.3 sec in total

First Response

15 ms

Resources Loaded

1.2 sec

Page Rendered

127 ms

challengerunner.com screenshot

About Website

Visit challengerunner.com now to see the best up-to-date Challenge Runner content for United States and also check out these interesting facts you probably never knew about challengerunner.com

ChallengeRunner.com is a fast, effective and affordable way to manage your employee or client weight-loss and fitness challenges.

Visit challengerunner.com

Key Findings

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

Performance Metrics

challengerunner.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value1,010 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.127

82/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

challengerunner.com

15 ms

challengerunner.com

36 ms

bootstrap.min.css

74 ms

css

102 ms

css

133 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 55% of them (47 requests) were addressed to the original Challengerunner.com, 6% (5 requests) were made to Cdnjs.cloudflare.com and 5% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (374 ms) relates to the external source Cdnjs.cloudflare.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 295.9 kB (25%)

Content Size

1.2 MB

After Optimization

866.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Challengerunner.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. 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. Javascripts take 513.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 72.1 kB

  • Original 88.6 kB
  • After minification 65.3 kB
  • After compression 16.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. This page needs HTML code to be minified as it can gain 23.3 kB, which is 26% 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 72.1 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 11.1 kB

  • Original 354.5 kB
  • After minification 343.5 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. Challenge Runner images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 114.9 kB

  • Original 513.2 kB
  • After minification 513.2 kB
  • After compression 398.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 114.9 kB or 22% of the original size.

CSS Optimization

-47%

Potential reduce by 97.9 kB

  • Original 206.1 kB
  • After minification 163.0 kB
  • After compression 108.2 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. Challengerunner.com needs all CSS files to be minified and compressed as it can save up to 97.9 kB or 47% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (57%)

Requests Now

76

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

challengerunner.com

challengerunner.com

15 ms

challengerunner.com

challengerunner.com

36 ms

bootstrap.min.css

bootstrap.min.css

74 ms

css

css

102 ms

css

css

133 ms

pe-icon-7-stroke.css

pe-icon-7-stroke.css

18 ms

animate.min.css

animate.min.css

53 ms

flexslider.css

flexslider.css

53 ms

header.css

header.css

87 ms

utilities.css

utilities.css

49 ms

style2.css

style2.css

102 ms

all.css

all.css

64 ms

font-awesome.min.css

font-awesome.min.css

114 ms

default.css

default.css

121 ms

streamline-icon.css

streamline-icon.css

123 ms

styles-5.css

styles-5.css

116 ms

cookieconsent.min.css

cookieconsent.min.css

121 ms

typed.min.js

typed.min.js

126 ms

countUp.min.js

countUp.min.js

94 ms

sdk.js

sdk.js

108 ms

widgets.js

widgets.js

109 ms

in.js

in.js

112 ms

element.js

element.js

341 ms

svg-injector.min.js

svg-injector.min.js

345 ms

jquery.min.js

jquery.min.js

346 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

107 ms

jarallax.min.js

jarallax.min.js

373 ms

cookieconsent.min.js

cookieconsent.min.js

374 ms

bootstrap-hover-dropdown.min.js

bootstrap-hover-dropdown.min.js

117 ms

jquery.inview.min.js

jquery.inview.min.js

122 ms

isMobile.min.js

isMobile.min.js

123 ms

back-to-top.js

back-to-top.js

122 ms

jquery.placeholder.js

jquery.placeholder.js

339 ms

jquery.fitvids.js

jquery.fitvids.js

342 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

342 ms

main.js

main.js

338 ms

w41.js

w41.js

338 ms

analytics.js

analytics.js

318 ms

CRLogo60.png

CRLogo60.png

161 ms

svg3_1.jpg

svg3_1.jpg

163 ms

clientlogo1.png

clientlogo1.png

160 ms

clientlogo2.png

clientlogo2.png

164 ms

clientlogo3.png

clientlogo3.png

161 ms

clientlogo4.png

clientlogo4.png

160 ms

ParallaxPants.png

ParallaxPants.png

167 ms

App_Store_Badge.png

App_Store_Badge.png

166 ms

android.png

android.png

165 ms

fitbit.png

fitbit.png

167 ms

garmin.png

garmin.png

208 ms

fit_72x72.png

fit_72x72.png

208 ms

coros.png

coros.png

208 ms

withings.png

withings.png

208 ms

wahoo.png

wahoo.png

208 ms

polar.png

polar.png

208 ms

samsunghealth.jpg

samsunghealth.jpg

242 ms

applehealthtransparent.png

applehealthtransparent.png

241 ms

strava.png

strava.png

242 ms

suunto.png

suunto.png

241 ms

uafitness.png

uafitness.png

241 ms

oura.png

oura.png

242 ms

sdk.js

sdk.js

151 ms

S6uyw4BMUTPHjx4wWyWtFCc.ttf

S6uyw4BMUTPHjx4wWyWtFCc.ttf

118 ms

S6u9w4BMUTPHh7USSwiPHA3q5d0.ttf

S6u9w4BMUTPHh7USSwiPHA3q5d0.ttf

247 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX9-p7K4GLs.ttf

276 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX9-p7K4GLs.ttf

274 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

247 ms

Pe-icon-7-stroke.woff

Pe-icon-7-stroke.woff

248 ms

fbevents.js

fbevents.js

40 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

185 ms

collect

collect

103 ms

collect

collect

65 ms

settings

settings

104 ms

like.php

like.php

242 ms

FollowCompany.js

FollowCompany.js

136 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

3 ms

embeds

embeds

29 ms

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

22 ms

moosend-tracking.min.js

moosend-tracking.min.js

99 ms

FollowCompany

FollowCompany

1 ms

FollowCompany

FollowCompany

137 ms

vwgziwe0FNr.js

vwgziwe0FNr.js

63 ms

gWpQpSsEGQ-.png

gWpQpSsEGQ-.png

57 ms

8mdfvg7u0c5ycz7dl7uv2e5fq

8mdfvg7u0c5ycz7dl7uv2e5fq

26 ms

in.js

in.js

13 ms

cwphtfsvdwm4k6n91alllgs6q

cwphtfsvdwm4k6n91alllgs6q

126 ms

Accessibility Review

challengerunner.com accessibility score

88

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

challengerunner.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

challengerunner.com SEO score

100

Search Engine Optimization Advices

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

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

challengerunner.com

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