3.6 sec in total
81 ms
3.3 sec
214 ms
Click here to check amazing Runningandthe City content. Otherwise, check out these important facts you probably never knew about runningandthecity.com
Why do you need a Biomechanics Coach? Very simple! Running is a skill and it needs to be mastered to avoid injuries. Over 80% of runners get injured every year, and most injuries are caused by a lack ...
Visit runningandthecity.comWe analyzed Runningandthecity.com page load time and found that the first response time was 81 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
runningandthecity.com performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value3.2 s
74/100
25%
Value11.9 s
4/100
10%
Value1,600 ms
12/100
30%
Value0
100/100
15%
Value26.6 s
0/100
10%
81 ms
270 ms
234 ms
72 ms
77 ms
Our browser made a total of 160 requests to load all elements on the main page. We found that 4% of them (6 requests) were addressed to the original Runningandthecity.com, 15% (24 requests) were made to Router.infolinks.com and 12% (19 requests) were made to S0.wp.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Pxl.iqm.com.
Page size can be reduced by 193.1 kB (16%)
1.2 MB
999.1 kB
In fact, the total size of Runningandthecity.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. 75% 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 874.8 kB which makes up the majority of the site volume.
Potential reduce by 153.3 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 153.3 kB or 76% of the original size.
Potential reduce by 2.9 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. Runningandthe City images are well optimized though.
Potential reduce by 36.7 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.
Potential reduce by 227 B
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. Runningandthecity.com has all CSS files already compressed.
Number of requests can be reduced by 111 (79%)
140
29
The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Runningandthe City. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
runningandthecity.com
81 ms
runningandthecity.com
270 ms
WkbsjAhTJyuIL2hLen5SZvNw3KE.js
234 ms
72 ms
style.css
77 ms
77 ms
72 ms
77 ms
css
88 ms
77 ms
74 ms
76 ms
email-decode.min.js
30 ms
hovercards.min.js
75 ms
wpgroho.js
77 ms
share-button.js
76 ms
77 ms
widgets.js
136 ms
sharing.min.js
77 ms
w.js
76 ms
analytics.js
42 ms
clujWdAjYf7zKoP6tzeLXyVThiQ.js
298 ms
conf
91 ms
importmap-polyfill.min.js
2 ms
cropped-922724_10151452712913051_2018525554_n.jpg
172 ms
pinit_fg_en_rect_gray_20.png
128 ms
581226f7747109b2857467255c40a1e155018a51d634207fb4dc2c5608023717
87 ms
body-bg.png
47 ms
post-ornament.png
47 ms
cropped-chicago-23_5093-large.jpeg
209 ms
orange-medium.png
56 ms
Qw3GZR9MED_6PSuS_50nEaVrfzgEbHoEig.ttf
160 ms
collect
40 ms
search-bg.png
42 ms
platform.js
123 ms
widgets.js
69 ms
sdk.js
135 ms
pinit.js
103 ms
master.html
120 ms
g.gif
121 ms
in.js
132 ms
button
197 ms
btn.js
131 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
148 ms
remote-login.php
195 ms
g.gif
110 ms
g.gif
110 ms
collect
188 ms
js
212 ms
ata.js
140 ms
USATF_horizontal.aspx
1827 ms
pinit_main.js
21 ms
rlt-proxy.js
20 ms
20 ms
sdk.js
83 ms
count.json
152 ms
settings
199 ms
button
71 ms
index.build.css
24 ms
index.build.js
78 ms
infolinks_main.js
156 ms
132 ms
widgetButton.91d9e0cb42c020d8c4b1.css
112 ms
widgetButton.cd8686eb1c51512964d7.js
114 ms
beacon.js
116 ms
impixu
113 ms
flat-t-button-white.svg
28 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
26 ms
button.856debeac157d9669cf51e73a08fbc93.js
24 ms
ice.js
61 ms
embeds
50 ms
tweet_button.2f70fb173b9000da126c79afe2098f02.en.html
57 ms
emaiuolo
87 ms
lcmanage
57 ms
gsd
55 ms
manage
74 ms
polyfills-3b821eda8863adcc4a4b.js
48 ms
runtime-a697c5a1ae32bd7e4d42.js
47 ms
modules.20f98d7498a59035a762.js
116 ms
main-fd9ef5eb169057cda26d.js
60 ms
_app-88bf420a57d49e33be53.js
160 ms
%5BscreenName%5D-c33f0b02841cffc3e9b4.js
177 ms
_buildManifest.js
177 ms
_ssgManifest.js
176 ms
doq.htm
322 ms
iqusync-1.26.min.js
49 ms
infolink
2099 ms
207 ms
224 ms
cksync
223 ms
iquid.js
105 ms
ima.js
174 ms
id5.js
148 ms
ppid.js
173 ms
sthr-us
77 ms
ImgSync
16 ms
sonobi-usync
56 ms
pixel
66 ms
qc-usync
49 ms
pixel
80 ms
eqv-us
55 ms
frwh-us
66 ms
apn-usync
115 ms
outh-usync
112 ms
tplift
112 ms
imd-usync
123 ms
mgid-us
121 ms
v1
542 ms
25 ms
zeta-usync
119 ms
190 ms
mnet-usync
90 ms
usermatch
36 ms
zmn-usync
135 ms
sovrn-usync
130 ms
33a-usync
127 ms
pixel
58 ms
ix-usync
114 ms
in_search.js
69 ms
bubble.js
64 ms
ima3.js
229 ms
container-4.0.html
89 ms
crum
138 ms
usermatchredir
62 ms
qora-usync
74 ms
ox-usync
70 ms
rum
167 ms
in_text.js
83 ms
intag_incontent.js
45 ms
getads.htm
265 ms
dcm
128 ms
pixel
121 ms
ImgSync
52 ms
RX-d6e4b70e-6327-437f-a2b3-30f13264d9fc-005
188 ms
ImgSync
118 ms
rum
117 ms
usersync.aspx
188 ms
loader.gif
137 ms
loader-bg.png
136 ms
generic
154 ms
crum
68 ms
i.match
170 ms
vidice.js
116 ms
ur-usync
49 ms
match
41 ms
disus
39 ms
usync.html
35 ms
generic
17 ms
generic
16 ms
match
14 ms
receive
43 ms
usync.js
3 ms
match
6 ms
Cap1_300x250_A.png
53 ms
match
6 ms
crum
28 ms
match
6 ms
iqm-us
37 ms
actionbar.css
2 ms
actionbar.js
9 ms
runningandthecity.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
runningandthecity.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
runningandthecity.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Runningandthecity.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 Runningandthecity.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.
runningandthecity.com
Open Graph data is detected on the main page of Runningandthe City. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: