10.7 sec in total
656 ms
6 sec
4 sec
Click here to check amazing Funrun content for United States. Otherwise, check out these important facts you probably never knew about funrun.com
Register your student or make a pledge for your school’s Boosterthon Fun Run, Dance Fit, Fundraiser today!
Visit funrun.comWe analyzed Funrun.com page load time and found that the first response time was 656 ms and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
funrun.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value6.8 s
7/100
25%
Value4.6 s
70/100
10%
Value1,740 ms
10/100
30%
Value0
100/100
15%
Value9.1 s
33/100
10%
656 ms
295 ms
220 ms
1080 ms
3036 ms
Our browser made a total of 13 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Funrun.com, 8% (1 request) were made to Ajax.googleapis.com and 8% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Ajax.googleapis.com.
Page size can be reduced by 594.3 kB (40%)
1.5 MB
893.7 kB
In fact, the total size of Funrun.com main page is 1.5 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. 45% of websites need less resources to load. Images take 690.5 kB which makes up the majority of the site volume.
Potential reduce by 13.0 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 13.0 kB or 62% of the original size.
Potential reduce by 884 B
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. Funrun images are well optimized though.
Potential reduce by 182.4 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 182.4 kB or 62% of the original size.
Potential reduce by 398.0 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. Funrun.com needs all CSS files to be minified and compressed as it can save up to 398.0 kB or 83% of the original size.
Number of requests can be reduced by 6 (55%)
11
5
The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funrun. 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 as a result speed up the page load time.
login
656 ms
font-awesome.min.css
295 ms
bootstrap.min.1479496743.css
220 ms
styles.1502997476.css
1080 ms
jquery.min.js
3036 ms
bootstrap.min.1479496743.js
2865 ms
privacy.1464895092.js
2866 ms
jquery.cssmap.1464895092.js
2967 ms
site.common.1504120030.js
2938 ms
jquery.backstretch.min.1464895092.js
2938 ms
analytics.js
2999 ms
fontawesome-webfont.woff
1509 ms
dash_login_bg.jpg
155 ms
funrun.com accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
funrun.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
funrun.com SEO score
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funrun.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 Funrun.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.
funrun.com
Open Graph description is not detected on the main page of Funrun. 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: