5.3 sec in total
508 ms
4.5 sec
239 ms
Welcome to mondraker.com homepage info - get ready to check MONDRAKER best content for Germany right away, or after learning these important things about mondraker.com
We started in 2001 in Alicante. Our dream was to develop bikes capable of delivering performance for the mountain bikers who wanted something beyond what the market was offering. Even from our...
Visit mondraker.comWe analyzed Mondraker.com page load time and found that the first response time was 508 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
mondraker.com performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value34.8 s
0/100
25%
Value28.0 s
0/100
10%
Value19,940 ms
0/100
30%
Value0.258
48/100
15%
Value44.3 s
0/100
10%
508 ms
159 ms
354 ms
608 ms
768 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 87% of them (33 requests) were addressed to the original Mondraker.com, 5% (2 requests) were made to Fonts.googleapis.com and 5% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Mondraker.com.
Page size can be reduced by 307.4 kB (10%)
3.0 MB
2.7 MB
In fact, the total size of Mondraker.com main page is 3.0 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. 25% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 16.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. This page needs HTML code to be minified as it can gain 3.8 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 16.0 kB or 79% of the original size.
Potential reduce by 103.6 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. MONDRAKER images are well optimized though.
Potential reduce by 120.2 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 120.2 kB or 64% of the original size.
Potential reduce by 67.6 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. Mondraker.com needs all CSS files to be minified and compressed as it can save up to 67.6 kB or 85% of the original size.
Number of requests can be reduced by 14 (42%)
33
19
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MONDRAKER. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
mondraker.com
508 ms
159 ms
home.html
354 ms
main.css
608 ms
jquery-1.9.1.min.js
768 ms
elizoom-1.0.js
331 ms
jquery.fancybox-1.3.1.css
334 ms
jquery.fancybox-1.3.1.js
491 ms
jquery.jscrollpane.min.js
345 ms
jquery.jscrollpane.css
491 ms
main.js
504 ms
css
25 ms
jquery.easing.1.3.js
518 ms
jquery.animate-enhanced.min.js
651 ms
jquery.superslides.js
660 ms
superslides.css
671 ms
jquery.countdown.js
695 ms
css
14 ms
mondraker-logo.png
175 ms
nav.png
192 ms
world.png
180 ms
languages-bg.png
155 ms
lupa.gif
185 ms
banner-lauri-greenland.jpg
1490 ms
banner-dune-carbon-xr.jpg
1386 ms
banner-crafty-plus.jpg
1285 ms
new-collection-2016.jpg
1834 ms
banner-dune-carbon.jpg
1209 ms
separator.png
366 ms
arrow-right.png
542 ms
arrow-left.png
723 ms
SgBaq0dzhSGNMfqm2JX5ng.woff
22 ms
yVILXKVgPzaz72DegpV7Bg.woff
35 ms
twitter.png
894 ms
facebook.png
1078 ms
vimeo.png
1266 ms
youtube.png
1363 ms
ga.js
30 ms
mondraker.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-hidden="true"] elements contain focusable descendents
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
mondraker.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
Issues were logged in the Issues panel in Chrome Devtools
mondraker.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
ES
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mondraker.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 Spanish language. Our system also found out that Mondraker.com 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.
mondraker.com
Open Graph description is not detected on the main page of MONDRAKER. 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: