8.3 sec in total
1.8 sec
6 sec
499 ms
Click here to check amazing Marhhe content. Otherwise, check out these important facts you probably never knew about marhhe.es
Distribución y Venta de Vehículos Innovadores, ágiles y eficientes. Proyectos e instalaciones de puntos de recarga para vehículos eléctricos. Marhhe
Visit marhhe.esWe analyzed Marhhe.es page load time and found that the first response time was 1.8 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
marhhe.es performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value7.8 s
3/100
25%
Value15.8 s
0/100
10%
Value780 ms
37/100
30%
Value0.376
28/100
15%
Value12.2 s
15/100
10%
1766 ms
64 ms
127 ms
240 ms
339 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 82% of them (70 requests) were addressed to the original Marhhe.es, 12% (10 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Marhhe.es.
Page size can be reduced by 195.8 kB (7%)
2.8 MB
2.6 MB
In fact, the total size of Marhhe.es main page is 2.8 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. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 55.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. 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 55.0 kB or 80% of the original size.
Potential reduce by 93 B
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. Marhhe images are well optimized though.
Potential reduce by 42.8 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 42.8 kB or 15% of the original size.
Potential reduce by 97.9 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. Marhhe.es needs all CSS files to be minified and compressed as it can save up to 97.9 kB or 30% of the original size.
Number of requests can be reduced by 46 (64%)
72
26
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Marhhe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
marhhe.es
1766 ms
analytics.js
64 ms
wp-emoji-release.min.js
127 ms
validationEngine.jquery.css
240 ms
Defaults.css
339 ms
style.min.css
326 ms
style.css
341 ms
styles.css
334 ms
yith_wcas_ajax_search.css
347 ms
prettyPhoto.css
351 ms
jquery.selectBox.css
565 ms
js_composer.min.css
691 ms
masterslider.main.css
506 ms
custom.css
493 ms
ultimate.min.css
841 ms
bootstrap.css
543 ms
plugins.css
685 ms
theme_elements.css
747 ms
theme.css
728 ms
theme_shop.css
723 ms
skin_1.css
859 ms
style.css
798 ms
css
48 ms
jquery.js
925 ms
jquery-migrate.min.js
883 ms
jquery.blockUI.min.js
876 ms
add-to-cart.min.js
913 ms
woocommerce-add-to-cart.js
978 ms
ultimate-params.min.js
956 ms
plugins.min.js
1107 ms
jquery.blueimp-gallery.min.js
1006 ms
jquery.selectBox.min.js
1028 ms
jquery.yith-wcwl.js
1038 ms
scripts.js
1100 ms
js.cookie.min.js
1143 ms
woocommerce.min.js
1140 ms
cart-fragments.min.js
1185 ms
yith-autocomplete.min.js
1186 ms
jquery.prettyPhoto.min.js
1247 ms
collect
13 ms
js
64 ms
comment-reply.min.js
1127 ms
jquery.easing.min.js
1015 ms
masterslider.min.js
1007 ms
theme.min.js
960 ms
wp-embed.min.js
1047 ms
js_composer_front.min.js
1024 ms
jquery-appear.min.js
1016 ms
ultimate_bg.min.js
1017 ms
custom.min.js
918 ms
collect
49 ms
marhhe-1.png
397 ms
blank.gif
396 ms
air-turbine-1.png
204 ms
Captura.png
210 ms
electric-car.png
394 ms
factory15-1.png
217 ms
sar9xvui-150x150.png
395 ms
Gocycle-Caracteristicas-1.jpg
396 ms
g3-1.jpg
437 ms
smartcity-1.png
638 ms
electro.png
449 ms
relacion-ciudadano-ayuntamiento-empresa1s.png
671 ms
P70704-125015-450x231.jpg
480 ms
IMG_20170513_142953_1-450x231.jpg
576 ms
logo.png
493 ms
payments1.png
565 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
63 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
80 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
102 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
101 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf
118 ms
fontawesome-webfont.woff
695 ms
Simple-Line-Icons.ttf
614 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVc.ttf
101 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkaVc.ttf
118 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVc.ttf
100 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVc.ttf
119 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVc.ttf
119 ms
bginicio2.jpg
868 ms
loading-2.gif
291 ms
bginicio2.jpg
487 ms
compra-de-energia-1.jpg
448 ms
e-mobility-web-2.jpg
544 ms
Gepida-Bike-Marhhe.jpg
773 ms
marhhe.es 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
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.
marhhe.es 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
marhhe.es SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Marhhe.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Marhhe.es 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.
marhhe.es
Open Graph description is not detected on the main page of Marhhe. 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: