3.7 sec in total
247 ms
2.9 sec
560 ms
Click here to check amazing Community Runnersworld content for United States. Otherwise, check out these important facts you probably never knew about community.runnersworld.com
Hearst Magazines Search and Information Page
Visit community.runnersworld.comWe analyzed Community.runnersworld.com page load time and found that the first response time was 247 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.
community.runnersworld.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value5.0 s
27/100
25%
Value4.1 s
80/100
10%
Value30 ms
100/100
30%
Value0.018
100/100
15%
Value5.1 s
75/100
10%
247 ms
34 ms
114 ms
80 ms
74 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 10% of them (9 requests) were addressed to the original Community.runnersworld.com, 11% (10 requests) were made to Assets.adobedtm.com and 9% (8 requests) were made to B.scorecardresearch.com. The less responsive or slowest element that took the longest time to load (764 ms) relates to the external source Assets.adobedtm.com.
Page size can be reduced by 979.7 kB (67%)
1.5 MB
491.9 kB
In fact, the total size of Community.runnersworld.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. 65% of websites need less resources to load. Javascripts take 918.2 kB which makes up the majority of the site volume.
Potential reduce by 120.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 120.0 kB or 85% of the original size.
Potential reduce by 7.3 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. Community Runnersworld images are well optimized though.
Potential reduce by 574.0 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 574.0 kB or 63% of the original size.
Potential reduce by 278.4 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. Community.runnersworld.com needs all CSS files to be minified and compressed as it can save up to 278.4 kB or 83% of the original size.
Number of requests can be reduced by 69 (82%)
84
15
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Community Runnersworld. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
community.runnersworld.com
247 ms
gpt.js
34 ms
satelliteLib-9ef46ccbdeecaf248ce80c4092b18144a304f95a.js
114 ms
css
80 ms
header.css
74 ms
hoopla-1449104434000.css
170 ms
ver21.2.b122.864bff6-1449104434000.css
82 ms
css
44 ms
header.js
97 ms
analytics.js
41 ms
footer.js
596 ms
common-ver21.2.b122.864bff6-1450108617119.js
247 ms
pubads_impl_81.js
13 ms
container.html
8 ms
pql
20 ms
beacon.js
143 ms
chartbeat_mab.js
196 ms
controltag
141 ms
satellite-53e0f51c49e9ca0dfb000312.js
253 ms
satellite-55be913c3365300014000016.js
248 ms
collect
164 ms
logo.png
105 ms
ads
326 ms
collect
108 ms
collect
110 ms
light-gray.png
110 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
110 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
111 ms
fontawesome-webfont.woff
206 ms
controltag.js.3269b976cac0388f80dbfdb09d96a4e7
60 ms
X1g_KwGeBV3ajZIXQ9VnDibsRidxnYrfzLNRqJkHfFo.ttf
153 ms
41 ms
i.js
91 ms
OBAN_GMIMEQuilsGMBaseAwareiMediaA1854FY1516_RegimenYellow_GetCoupon_xxx_728x90_15_2_Static.jpg
331 ms
surly.js
280 ms
rs.js
289 ms
moatad.js
188 ms
surly.js
281 ms
OBAN_TMOLVQuilsTMPOLVTA1849FY1516_Regimen_GetCoupon_xxx_300x250_15_2_Static.jpg
325 ms
osd.js
256 ms
satellite-5530fef93737350017ea0400.js
374 ms
satellite-55e9a2ff3637390017000431.js
127 ms
s-code-contents-d9e2bb1a111ccd66d5ed3cd9f03a420f4489dcbd.js
281 ms
satellite-55e444963961370014000796.html
136 ms
satellite-5530145f333536624d8c0500.html
171 ms
satellite-55d378c239396600170001ab.html
227 ms
satellite-56125efe376639439c0000a8.html
764 ms
init1.js
159 ms
ba.html
45 ms
4.gif
46 ms
p
37 ms
rpc.flow
46 ms
vce_st.js
38 ms
sbhK2lTE.js
35 ms
rpc.flow
41 ms
p
32 ms
pixel.gif
24 ms
fbevents.js
135 ms
45460.js
29 ms
pixel.gif
29 ms
cTrvNaRi.html
29 ms
p
25 ms
p
31 ms
p
40 ms
p
41 ms
moatcontent.js
41 ms
pixel.gif
32 ms
bouncev2.cc0069615a.css
37 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
72 ms
box_77_top-right.png
23 ms
c_50_us.png
21 ms
pixel.gif
5 ms
dbg52463.moatads.com
35 ms
d5i9o0tpq9sa1.cloudfront.net
36 ms
pixel.gif
29 ms
95 ms
vglnk.js
39 ms
s37717351596802
7 ms
pixel.gif
22 ms
pixel.gif
41 ms
pixel.gif
4 ms
chartbeat.js
69 ms
optout_check
66 ms
get
72 ms
tag.aspx
28 ms
generic
19 ms
genericusersync.ashx
19 ms
generic
22 ms
ping
10 ms
utsync.ashx
70 ms
ping
23 ms
tpsync.ashx
9 ms
community.runnersworld.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
community.runnersworld.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
community.runnersworld.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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Community.runnersworld.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 Community.runnersworld.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.
community.runnersworld.com
Open Graph description is not detected on the main page of Community Runnersworld. 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: