5.4 sec in total
1.2 sec
3.7 sec
438 ms
Welcome to prorun.nl homepage info - get ready to check Pro Run best content for Belgium right away, or after learning these important things about prorun.nl
De beste trainingsschema's, hardlopen op vermogen en alles voor jouw PR. Meld je aan voor de nieuwsbrief en mis niets!
Visit prorun.nlWe analyzed Prorun.nl page load time and found that the first response time was 1.2 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
prorun.nl performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value10.3 s
0/100
25%
Value11.4 s
5/100
10%
Value710 ms
42/100
30%
Value0.023
100/100
15%
Value13.8 s
10/100
10%
1220 ms
1252 ms
22 ms
173 ms
168 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 74% of them (45 requests) were addressed to the original Prorun.nl, 8% (5 requests) were made to Tpc.googlesyndication.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Prorun.nl.
Page size can be reduced by 443.7 kB (27%)
1.6 MB
1.2 MB
In fact, the total size of Prorun.nl main page is 1.6 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 42.9 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 42.9 kB or 84% of the original size.
Potential reduce by 50.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. Pro Run images are well optimized though.
Potential reduce by 243.3 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 243.3 kB or 66% of the original size.
Potential reduce by 107.2 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. Prorun.nl needs all CSS files to be minified and compressed as it can save up to 107.2 kB or 85% of the original size.
Number of requests can be reduced by 30 (52%)
58
28
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pro Run. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
prorun.nl
1220 ms
www.prorun.nl
1252 ms
analytics.js
22 ms
jquery.js
173 ms
jquery.lightbox-0.4-min.js
168 ms
effects.js
170 ms
menu.js
168 ms
form.js
168 ms
jquery.cycle2.min.js
170 ms
responsive.js
250 ms
styles.css
249 ms
containers.css
334 ms
menu.css
251 ms
form.css
251 ms
responsive.css
254 ms
cookies.min.js
331 ms
glDatePicker.min.js
330 ms
glDatePicker.flatwhite.css
330 ms
css
29 ms
jquery.lightbox-0.5.css
330 ms
collect
12 ms
collect
59 ms
atrk.js
41 ms
gpt.js
25 ms
social_facebook.png
125 ms
social_twitter.png
125 ms
social_mail.png
124 ms
social_rss.png
126 ms
home.jpg
125 ms
zoekbtn.jpg
124 ms
logo.jpg
291 ms
20160120_145527runlog-banner.jpg
447 ms
calculator_btn.jpg
290 ms
headermenu_backgr.jpg
203 ms
4.jpg
203 ms
nieuwsbriefinschrijven_backgr.jpg
183 ms
pubads_impl_81.js
14 ms
20150731_000915.jpg
505 ms
OpenSansRegular.woff
495 ms
Museo300Regular.woff
331 ms
atrk.gif
84 ms
20150331_173602.jpg
406 ms
ads
124 ms
container.html
20 ms
test.png
407 ms
20160227_203839.jpg
340 ms
20160225_214903.jpg
420 ms
20160223_224649.jpg
408 ms
20160229_133300.jpg
496 ms
20150325_095241.jpg
574 ms
20150310_134126.jpg
728 ms
20160225_214103.jpg
484 ms
groot3.jpg
485 ms
groot7.jpg
475 ms
6.jpg
553 ms
footer_width.jpg
523 ms
5808042313612456238
53 ms
3207674014038159672
60 ms
2613537933834962916
88 ms
17473764804964657107
42 ms
osd.js
5 ms
prorun.nl 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.
prorun.nl 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
Page has valid source maps
prorun.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
NL
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prorun.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Prorun.nl main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
prorun.nl
Open Graph description is not detected on the main page of Pro Run. 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: