7.4 sec in total
208 ms
7 sec
177 ms
Visit mobo.mx now to see the best up-to-date MOBO content and also check out these interesting facts you probably never knew about mobo.mx
Visit mobo.mxWe analyzed Mobo.mx page load time and found that the first response time was 208 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mobo.mx performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value6.6 s
8/100
25%
Value7.5 s
27/100
10%
Value3,080 ms
2/100
30%
Value0.09
92/100
15%
Value21.9 s
1/100
10%
208 ms
204 ms
227 ms
339 ms
128 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Mobo.mx, 96% (100 requests) were made to Mobo.com.mx and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.4 sec) relates to the external source Mobo.com.mx.
Page size can be reduced by 1.2 MB (13%)
9.6 MB
8.4 MB
In fact, the total size of Mobo.mx main page is 9.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. 55% of websites need less resources to load. Images take 9.0 MB which makes up the majority of the site volume.
Potential reduce by 15.4 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 15.4 kB or 77% of the original size.
Potential reduce by 751.8 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. MOBO images are well optimized though.
Potential reduce by 385.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 385.3 kB or 72% of the original size.
Potential reduce by 79.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. Mobo.mx needs all CSS files to be minified and compressed as it can save up to 79.2 kB or 86% of the original size.
Number of requests can be reduced by 32 (32%)
101
69
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MOBO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
mobo.mx
208 ms
www.mobo.com.mx
204 ms
index.php
227 ms
style.css
339 ms
contentslider.css
128 ms
ddsmoothmenu.css
196 ms
slider.css
147 ms
list.css
148 ms
jquery.fancybox-1.3.1.css
259 ms
jquery.min14.js
772 ms
contentslider.js
295 ms
jquery.anythingslider.js
370 ms
anythingslider.js
261 ms
jcarousellite_1.0.1.js
397 ms
scroller.js
330 ms
ddaccordion.js
374 ms
acordn.js
409 ms
paging.js
399 ms
switch.js
445 ms
jquery.fancybox-1.3.1.js
450 ms
lightbox.js
464 ms
cufon-yui.js
469 ms
Trebuchet_MS_400-Trebuchet_MS_700-Trebuchet_MS_italic_700-Trebuchet_MS_italic_400.font.js
668 ms
cufon.js
519 ms
animatedcollapse.js
526 ms
toglrcollapse.js
527 ms
jquery-1.11.0.min.js
904 ms
jsg.js
594 ms
jquery-latest.min.js
5 ms
slg.min.js
599 ms
slg.js
594 ms
slg.css
680 ms
wt-rotator.css
662 ms
jquery.easing.1.3.min.js
677 ms
jquery.wt-rotator.min.js
897 ms
stmenu.js
681 ms
ga.js
36 ms
index.php
151 ms
space.gif
68 ms
botones_01.png
77 ms
botones_02.png
69 ms
botones_03.png
75 ms
botones_04.png
57 ms
botones_05.png
113 ms
cel_1_1.png
133 ms
cel_2_1.png
135 ms
cel_3_1.png
149 ms
cel_4_1.jpg
153 ms
botones_06.png
168 ms
cat_1_1.png
197 ms
cat_2_1.png
200 ms
botones_07.png
225 ms
botones_08.png
227 ms
home.gif
228 ms
semi.png
223 ms
repair.png
262 ms
desbloqueo.png
266 ms
tiempo.png
280 ms
glass.png
301 ms
banner_bolsatrabajo.jpg
1336 ms
cellrepair.jpg
446 ms
seminuevos.jpg
456 ms
motorola.jpg
535 ms
twink.jpg
1467 ms
BMWCRNAZIPHONE5.jpg
376 ms
IBTCRAWIPHONE5%202200.jpg
526 ms
IPDPAG01IPHONE5G.jpg
815 ms
MVLSMR4.jpg
5403 ms
CAME02IPHONE4G.jpg
603 ms
MLIFL6IPHONE.jpg
604 ms
PGEHSBIPHONE5G.jpg
690 ms
IPDCU0IPHONE5GGRIS.jpg
671 ms
VARPLM01NEGRA.jpg
708 ms
__utm.gif
11 ms
IPDCBUBL2IPHONE5G.jpg
714 ms
DCLDPFU01TABLETS7.jpg
751 ms
PGESHBIPHONE5G.jpg
784 ms
DCLDFR1MORRAL7.jpg
816 ms
CAMACGUSB1.jpg
899 ms
IPDCU0IPHONE5GTURQUE.jpg
816 ms
c.jpg
828 ms
c4.jpg
870 ms
home1.jpg
880 ms
home2.jpg
1120 ms
home3.jpg
1002 ms
iconos.jpg
929 ms
crumb2.png
966 ms
crumb_seprator.gif
1033 ms
c2.jpg
1007 ms
c3.jpg
1068 ms
left_head.gif
1078 ms
semi2.png
84 ms
botones_01_01.png
70 ms
botones_01_02.png
85 ms
botones_01_03.png
69 ms
botones_01_04.png
81 ms
botones_01_05.png
57 ms
botones_01_06.png
114 ms
botones_01_07.png
141 ms
botones_01_08.png
143 ms
botones_01_09.png
167 ms
c_1_2.png
169 ms
c_2_2.png
166 ms
c_3_2.png
174 ms
mobo.mx 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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
mobo.mx 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
Browser errors were logged to the console
Page has valid source maps
mobo.mx SEO score
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
ES
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobo.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish 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 Mobo.mx 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.
mobo.mx
Open Graph description is not detected on the main page of MOBO. 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: