7 sec in total
290 ms
6.3 sec
399 ms
Visit smartrunner.de now to see the best up-to-date Smart Runner content and also check out these interesting facts you probably never knew about smartrunner.de
track your trails and holidays with your mobile phone and share it with social networks – GPS tracking with SmartRunner
Visit smartrunner.deWe analyzed Smartrunner.de page load time and found that the first response time was 290 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
smartrunner.de performance score
290 ms
300 ms
652 ms
652 ms
32 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Smartrunner.de, 65% (98 requests) were made to Smartrunner.com and 12% (18 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Smartrunner.com.
Page size can be reduced by 1.7 MB (67%)
2.5 MB
804.1 kB
In fact, the total size of Smartrunner.de main page is 2.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. 70% of websites need less resources to load. Javascripts take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 39.2 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 39.2 kB or 72% of the original size.
Potential reduce by 82.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. Obviously, Smart Runner needs image optimization as it can save up to 82.9 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.5 MB
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 1.5 MB or 81% of the original size.
Potential reduce by 22.8 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. Smartrunner.de needs all CSS files to be minified and compressed as it can save up to 22.8 kB or 83% of the original size.
Number of requests can be reduced by 86 (60%)
143
57
The browser has sent 143 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Smart 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 70 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
smartrunner.de
290 ms
pages
300 ms
652 ms
Site.css
652 ms
jquery.min.js
32 ms
WebResource.axd
461 ms
ScriptResource.axd
462 ms
ScriptResource.axd
378 ms
ScriptResource.axd
567 ms
ScriptResource.axd
281 ms
webkit.js
374 ms
tooltip.js
1181 ms
FacebookUtils.js
514 ms
ScriptResource.axd
515 ms
ScriptResource.axd
554 ms
ScriptResource.axd
559 ms
ScriptResource.axd
562 ms
ScriptResource.axd
598 ms
ScriptResource.axd
647 ms
ScriptResource.axd
652 ms
ScriptResource.axd
654 ms
ScriptResource.axd
660 ms
ScriptResource.axd
663 ms
ScriptResource.axd
740 ms
ScriptResource.axd
744 ms
ScriptResource.axd
747 ms
ScriptResource.axd
754 ms
jsdebug
756 ms
all.js
149 ms
ga.js
37 ms
header_logo.png
751 ms
en.png
356 ms
sport_black_ca085551fd10492ca4807892a25cb060_32x32.png
644 ms
sport_black_7b399ae452f04b7595581520dc9da6a2_32x32.png
672 ms
sport_black_06f0dc4fffba4f51b77574cc38a606c2_32x32.png
689 ms
sport_black_0bd68fb1949b442f8731b3371580fc01_32x32.png
687 ms
sport_black_171f256f51184eca9f5885fa332442e4_32x32.png
776 ms
sport_black_2152e4ceb0dd48fcae1f95bdb417d9cc_32x32.png
1630 ms
sport_black_41b233ab67074e3cb1b00d802ee7fe22_32x32.png
1606 ms
sport_black_48f1aad0da3042059cfddc6a8c3645e9_32x32.png
1608 ms
sport_black_d5a6e4f22ac64d0d87a2ebab9b17cc4d_32x32.png
839 ms
sport_black_5ab041f101db485a8b57b01f8c703e14_32x32.png
841 ms
sport_black_55a178e7c6094122a36c8dd9ec0ccc10_32x32.png
896 ms
sport_black_2e53527355184feda67fd957dccc0146_32x32.png
1597 ms
sport_black_cf40ffb6ad7540188e312d8aa76daedf_32x32.png
938 ms
sport_black_ac37b23d2d094cd3b5ae2f6939ed0a21_32x32.png
1629 ms
feature_opti.png
2052 ms
feature_poi.png
2126 ms
userphotocut.ashx
1681 ms
userphotocut.ashx
1677 ms
__utm.gif
13 ms
userphotocut.ashx
1659 ms
userphotocut.ashx
1655 ms
userphotocut.ashx
1727 ms
facebook_follow.png
1960 ms
twitter_follow.png
1972 ms
WrapPlayerSwitch.aspx
1106 ms
sr_back_blackdia.png
1329 ms
menu_blue.png
1327 ms
submenu_blue.png
1407 ms
back.png
1801 ms
widget_header_back3.png
1425 ms
138 ms
footer.png
1333 ms
xd_arbiter.php
148 ms
xd_arbiter.php
259 ms
login_button.php
72 ms
xd_arbiter.php
110 ms
6K9Y3AoPUqO.js
395 ms
teE39sffXW8.png
453 ms
iqVGY7gYXlg.gif
469 ms
ScriptResource.axd
335 ms
UserPhotoCut.ashx
397 ms
player_switch_transparent.png
723 ms
UserPhotoCut.ashx
419 ms
UserPhotoCut.ashx
423 ms
UserPhotoCut.ashx
430 ms
UserPhotoCut.ashx
491 ms
PlayerSwitch.aspx
481 ms
maps
32 ms
jsapi
21 ms
lang_base.js
95 ms
DateParseEx.js
651 ms
animation.js
649 ms
baseVariables.js
644 ms
CalcDistancesAndTimes.js
646 ms
colorPickers.js
645 ms
DistanceMarkers.js
647 ms
googleEarthController.js
741 ms
kmlDomWalk.js
749 ms
mainRoute.js
748 ms
mapMain.js
747 ms
plotMain.js
750 ms
toolkitTime.js
900 ms
dtl.js
889 ms
dzc.js
889 ms
kdz.js
891 ms
mim.js
889 ms
pum.js
890 ms
SignificantFigures.js
989 ms
str.js
988 ms
exCanvas.min.js
1161 ms
jquery.flot.js
1345 ms
jquery.flot.crosshair.js
1164 ms
jquery-ui.min.js
50 ms
jquery-ui.css
49 ms
jquery-ui.css
50 ms
jquery.dd.js
993 ms
dd.css
1079 ms
jslider.css
1089 ms
jquery.dependClass.js
1105 ms
jquery.slider.js
1186 ms
common.js
5 ms
util.js
41 ms
marker.js
39 ms
play_40.png
172 ms
application_view_detail.png
158 ms
map_magnify.png
243 ms
control_play_blue.png
247 ms
map.js
28 ms
overlay.js
16 ms
poly.js
8 ms
StaticMapService.GetMapImage
111 ms
onion.js
39 ms
openhand_8_8.cur
63 ms
transparent.png
44 ms
ViewportInfoService.GetViewportInfo
86 ms
stats.js
39 ms
controls.js
34 ms
undo_poly.png
51 ms
infowindow.js
44 ms
css
57 ms
google4.png
43 ms
mapcnt6.png
31 ms
tmapctrl.png
17 ms
cb_scout5.png
38 ms
tmapctrl4.png
22 ms
imgs8.png
21 ms
vt
73 ms
vt
40 ms
vt
39 ms
vt
40 ms
vt
36 ms
vt
68 ms
vt
67 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
30 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
41 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
66 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
67 ms
AuthenticationService.Authenticate
122 ms
smartrunner.de SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Smartrunner.de 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 Smartrunner.de 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.
smartrunner.de
Open Graph description is not detected on the main page of Smart 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: