2.9 sec in total
281 ms
2.5 sec
169 ms
Click here to check amazing Open Runner content for France. Otherwise, check out these important facts you probably never knew about openrunner.com
Plot your next hike, bike or trail route, or choose among 6 million! Site and app created in France by outdoor sports enthusiasts.
Visit openrunner.comWe analyzed Openrunner.com page load time and found that the first response time was 281 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
openrunner.com performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value16.8 s
0/100
25%
Value14.7 s
1/100
10%
Value20,620 ms
0/100
30%
Value0.807
5/100
15%
Value33.1 s
0/100
10%
281 ms
310 ms
68 ms
95 ms
160 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 60% of them (60 requests) were addressed to the original Openrunner.com, 11% (11 requests) were made to Maps.googleapis.com and 9% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (957 ms) belongs to the original domain Openrunner.com.
Page size can be reduced by 2.0 MB (64%)
3.1 MB
1.1 MB
In fact, the total size of Openrunner.com main page is 3.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. 65% of websites need less resources to load. Javascripts take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 50.7 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 50.7 kB or 81% of the original size.
Potential reduce by 34.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. Open Runner images are well optimized though.
Potential reduce by 1.8 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.8 MB or 72% of the original size.
Potential reduce by 116.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. Openrunner.com needs all CSS files to be minified and compressed as it can save up to 116.0 kB or 82% of the original size.
Number of requests can be reduced by 59 (63%)
93
34
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Open 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 49 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
openrunner.com
281 ms
www.openrunner.com
310 ms
css
68 ms
yui-reset-min.css
95 ms
jquery-ui-1.8.2.custom.css
160 ms
site-or4.0-p-69.css
241 ms
slidorion-or.css
176 ms
colorpicker.css
175 ms
sliderkit-core.css
186 ms
fileuploader.css
190 ms
jquery.lightbox-0.5.css
236 ms
multi-select.css
259 ms
theme.or.css
260 ms
plusone.js
88 ms
js
90 ms
jquery-1.7.2.min.js
464 ms
jquery-ui-1.8.2.custom.min.js
483 ms
jquery-browdet.js
310 ms
jquery.lightbox-0.5.pack.js
312 ms
jquery.sliderkit.1.9.2.pack.js
341 ms
jquery.jcarousel.min.js
342 ms
prototype.js
481 ms
i18n_js.php
399 ms
openrunner-main4.0-p-69op10.js
682 ms
openrunner-extmaps4.0-p-69o.js
428 ms
advertisement.js
514 ms
scriptaculous.js
515 ms
modalbox-1.5.5.js
555 ms
geoip.php
556 ms
MarkerCluster-min.js
573 ms
fastinit.js
556 ms
GarminPackv1.js
773 ms
fileuploader2.js
649 ms
ckeditor.js
957 ms
colorpicker.js
634 ms
validation-1.5.4.1.js
668 ms
infobox_packed.js
727 ms
map-icons.js
756 ms
jquery.json-2.4.min.js
766 ms
jquery.multi-select.js
767 ms
cookiechoices2.js
791 ms
jquery.tablesorter.min.js
765 ms
widget-scroller.js
715 ms
jquery.df.min.js
691 ms
cb=gapi.loaded_0
20 ms
dc.js
32 ms
sprite-flag-or.png
152 ms
logo-or-240m.png
242 ms
sprite-tools-or-3.png
326 ms
back_outil.png
233 ms
bg_slide_2015.jpg
823 ms
spinner.gif
252 ms
PR1-final.jpg
319 ms
PRA4P-final.jpg
321 ms
PRA4L-final.jpg
326 ms
logo_or_sq_dotcom_h60px.png
347 ms
sprite-share-or.png
820 ms
effects.js
384 ms
-g5pDUSRgvxvOl5u-a_WHw.woff
68 ms
__utm.gif
14 ms
gpt.js
359 ms
common.js
66 ms
map.js
79 ms
util.js
181 ms
controls.js
180 ms
places_impl.js
79 ms
layers.js
70 ms
global-stats.php
166 ms
bestload-stats.php
333 ms
overlay.js
149 ms
measure.min.js
149 ms
ads.min.js
147 ms
logo_ign.gif
146 ms
logo_gp.gif
142 ms
IGN_logo_ministerio.png
273 ms
logoINPN-h25px.png
144 ms
logoCarmen-w50px.png
142 ms
pubads_impl_81.js
23 ms
onion.js
80 ms
container.html
104 ms
infowindow.js
123 ms
transparent.png
139 ms
css
84 ms
textlink-ads.jpg
53 ms
textlink-ads.jpg
45 ms
powered-by-google-on-white3.png
99 ms
autocomplete-icons.png
103 ms
marker.js
40 ms
google4.png
66 ms
mapcnt6.png
67 ms
sv5.png
64 ms
a.js
22 ms
tmapctrl.png
43 ms
cb_scout5.png
66 ms
tmapctrl4.png
50 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
26 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
41 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
50 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
56 ms
mq_logo.png
27 ms
openrunner.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
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
openrunner.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
openrunner.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
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Openrunner.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Openrunner.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.
openrunner.com
Open Graph description is not detected on the main page of Open 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: