Tools & Wizards About Us
runfor102.org screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

runfor102.org

2023 — Run for 102 Race to the Finish — Race Roster — Registration, Marketing, Fundraising

Page Load Speed

1.6 sec in total

First Response

13 ms

Resources Loaded

1 sec

Page Rendered

595 ms

runfor102.org screenshot

About Website

Welcome to runfor102.org homepage info - get ready to check Run For 102 best content right away, or after learning these important things about runfor102.org

Run for 102 Race to the Finish 9311 Shields Avenue, Brookfield, IL, USA - Run for 102 Race to the FinishSave the date! Run for 102… - April 30, 2023

Visit runfor102.org

Key Findings

We analyzed Runfor102.org page load time and found that the first response time was 13 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

runfor102.org performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value1,110 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.282

43/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

runfor102.org

13 ms

run-for-102-race-to-the-finish

335 ms

fbevents.js

55 ms

gtm.js

153 ms

css2

98 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Runfor102.org, 39% (25 requests) were made to Raceroster.com and 19% (12 requests) were made to Cdn.raceroster.com. The less responsive or slowest element that took the longest time to load (392 ms) relates to the external source Cdn.raceroster.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 660.2 kB (31%)

Content Size

2.1 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Runfor102.org main page is 2.1 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 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 177.8 kB

  • Original 201.9 kB
  • After minification 138.0 kB
  • After compression 24.1 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 63.9 kB, which is 32% 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 177.8 kB or 88% of the original size.

Image Optimization

-28%

Potential reduce by 481.0 kB

  • Original 1.7 MB
  • After minification 1.2 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. Obviously, Run For 102 needs image optimization as it can save up to 481.0 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 1.5 kB

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

Requests Breakdown

Number of requests can be reduced by 31 (62%)

Requests Now

50

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

runfor102.org

runfor102.org

13 ms

run-for-102-race-to-the-finish

run-for-102-race-to-the-finish

335 ms

fbevents.js

fbevents.js

55 ms

gtm.js

gtm.js

153 ms

css2

css2

98 ms

public-facing.1709306757.css

public-facing.1709306757.css

19 ms

google-recaptcha.1681217771.css

google-recaptcha.1681217771.css

97 ms

lightbox2.1709306757.css

lightbox2.1709306757.css

48 ms

cookie-banner.1700159227.css

cookie-banner.1700159227.css

48 ms

ad-banners.1698416621.css

ad-banners.1698416621.css

96 ms

event-details.1709306757.css

event-details.1709306757.css

96 ms

leaderboards.1681217771.css

leaderboards.1681217771.css

47 ms

froala-view.1706126349.css

froala-view.1706126349.css

106 ms

sdk.js

sdk.js

91 ms

public-facing.1709306757.js

public-facing.1709306757.js

121 ms

csrf-form-input.1681217771.js

csrf-form-input.1681217771.js

90 ms

csrf-ajax-prefilter.1697726761.js

csrf-ajax-prefilter.1697726761.js

102 ms

data-dog.1681217770.js

data-dog.1681217770.js

124 ms

mailcheck.1694528796.js

mailcheck.1694528796.js

123 ms

google-recaptcha.1681217771.js

google-recaptcha.1681217771.js

173 ms

api.js

api.js

134 ms

prevent-double-submission.1681217771.js

prevent-double-submission.1681217771.js

124 ms

authentication.1707405538.js

authentication.1707405538.js

124 ms

confirm-dialog.1681217771.js

confirm-dialog.1681217771.js

125 ms

lightbox2.1709306757.js

lightbox2.1709306757.js

132 ms

ad-banners.1698416621.js

ad-banners.1698416621.js

184 ms

cookie-banner.1700159227.js

cookie-banner.1700159227.js

170 ms

event-details.1709306757.js

event-details.1709306757.js

171 ms

widgets.js

widgets.js

272 ms

7726744frqxamguq._original.png

7726744frqxamguq._original.png

378 ms

njk6rdv9dm44w2ez._cropped.png

njk6rdv9dm44w2ez._cropped.png

258 ms

b9fcfdtpbc4vcejj._cropped.png

b9fcfdtpbc4vcejj._cropped.png

198 ms

p4bgneyzygwyt3k4._cropped.png

p4bgneyzygwyt3k4._cropped.png

258 ms

nkvf9wprdyg39bck._cropped.jpg

nkvf9wprdyg39bck._cropped.jpg

258 ms

ftcv7nz4efkvdnvd._cropped.jpg

ftcv7nz4efkvdnvd._cropped.jpg

308 ms

rzprada564vg5r2b._cropped.jpg

rzprada564vg5r2b._cropped.jpg

365 ms

ye267qkjry4rgmsq._original.png

ye267qkjry4rgmsq._original.png

392 ms

user-eo.svg

user-eo.svg

260 ms

settings-additional-event-details.svg

settings-additional-event-details.svg

263 ms

settings-questions.svg

settings-questions.svg

361 ms

race-roster-logo-white.png

race-roster-logo-white.png

364 ms

sdk.js

sdk.js

101 ms

js

js

104 ms

analytics.js

analytics.js

158 ms

destination

destination

135 ms

recaptcha__en.js

recaptcha__en.js

206 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

173 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

174 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

199 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

332 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

338 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQNig.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQNig.ttf

211 ms

6057f0f7f9a9a68b2eed.woff

6057f0f7f9a9a68b2eed.woff

70 ms

126e4e16f5400ed7fb99.woff

126e4e16f5400ed7fb99.woff

115 ms

92ee10240bc7f84042de.woff

92ee10240bc7f84042de.woff

65 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVc.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVc.ttf

211 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVc.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVc.ttf

218 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVc.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVc.ttf

217 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

145 ms

linkid.js

linkid.js

65 ms

collect

collect

27 ms

collect

collect

61 ms

settings

settings

128 ms

ga-audiences

ga-audiences

52 ms

Accessibility Review

runfor102.org accessibility score

91

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.

Best Practices

runfor102.org 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

runfor102.org SEO score

93

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

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 Runfor102.org 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 Runfor102.org 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

runfor102.org

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