2.3 sec in total
77 ms
2 sec
204 ms
Welcome to ford.mx homepage info - get ready to check Ford best content for Mexico right away, or after learning these important things about ford.mx
Conoce la Nueva Gama de Vehículos Ford: SUVs, Camiones de Trabajo, Autos Deportivos y Pickups. Con Motor de Tecnología Eléctrica, Híbrida o Gasolina
Visit ford.mxWe analyzed Ford.mx page load time and found that the first response time was 77 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
ford.mx performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value27.0 s
0/100
25%
Value15.4 s
0/100
10%
Value5,530 ms
0/100
30%
Value1.928
0/100
15%
Value30.3 s
0/100
10%
77 ms
55 ms
64 ms
53 ms
69 ms
Our browser made a total of 167 requests to load all elements on the main page. We found that 56% of them (94 requests) were addressed to the original Ford.mx, 7% (12 requests) were made to Cm.g.doubleclick.net and 5% (8 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (565 ms) belongs to the original domain Ford.mx.
Page size can be reduced by 2.6 MB (39%)
6.7 MB
4.1 MB
In fact, the total size of Ford.mx main page is 6.7 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 273.8 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 273.8 kB or 85% of the original size.
Potential reduce by 131.2 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. Ford images are well optimized though.
Potential reduce by 1.7 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.7 MB or 70% of the original size.
Potential reduce by 518.1 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. Ford.mx needs all CSS files to be minified and compressed as it can save up to 518.1 kB or 86% of the original size.
Number of requests can be reduced by 52 (36%)
146
94
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ford. 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 5 to 1 for CSS and as a result speed up the page load time.
ford.mx
77 ms
www.ford.mx
55 ms
foundation.css
64 ms
app.css
53 ms
app2.css
69 ms
tablet.css
14 ms
prod.min.js
14 ms
jquery-1.11.1.min.js
26 ms
MEX
503 ms
ebOneTag.js
138 ms
addthis_widget.js
9 ms
Satellite
21 ms
blank.gif
36 ms
Satellite
20 ms
Satellite
43 ms
Satellite
20 ms
Satellite
54 ms
Satellite
163 ms
Satellite
55 ms
gateway.js
156 ms
prod.min.js
36 ms
Antenna.Light.webfont.woff
146 ms
Serving
173 ms
loader-blue.gif
131 ms
Antenna.Extra-Light.webfont.woff
129 ms
icomoon.woff
130 ms
Antenna.Bold.webfont.woff
150 ms
icons.svg
144 ms
Satellite
252 ms
Satellite
255 ms
Satellite
41 ms
fbevents.js
195 ms
cc_af.js
190 ms
Satellite
182 ms
Satellite
177 ms
Satellite
17 ms
Satellite
185 ms
Satellite
183 ms
Satellite
183 ms
LightningBolt.js
187 ms
Satellite
169 ms
js
130 ms
300lo.json
40 ms
modal-bg.png
63 ms
Satellite
214 ms
Satellite
63 ms
Satellite
227 ms
Satellite
31 ms
Satellite
213 ms
Satellite
81 ms
Satellite
84 ms
Satellite
83 ms
Satellite
185 ms
Satellite
181 ms
Satellite
183 ms
Satellite
213 ms
Satellite
226 ms
Satellite
212 ms
Satellite
301 ms
Satellite
272 ms
Satellite
301 ms
Satellite
272 ms
Satellite
261 ms
Satellite
272 ms
Satellite
264 ms
Satellite
272 ms
Satellite
366 ms
Satellite
367 ms
Satellite
367 ms
Satellite
274 ms
Satellite
296 ms
Satellite
358 ms
Satellite
359 ms
Satellite
359 ms
Satellite
360 ms
Satellite
361 ms
Satellite
358 ms
Satellite
565 ms
sh.7c7179124ea24ac6ba46caac.html
38 ms
utag.js
154 ms
x71.html
57 ms
204 ms
s95156239119824
31 ms
Satellite
339 ms
layers.3643cb2e25fb91c29386.js
46 ms
js
44 ms
Satellite
371 ms
Satellite
371 ms
common.js
109 ms
map.js
136 ms
i.js
217 ms
Satellite
497 ms
jquery.min.js
131 ms
Satellite
495 ms
96 ms
Satellite
286 ms
Satellite
283 ms
pixel
77 ms
Satellite
369 ms
Satellite
368 ms
pixel
74 ms
Satellite
378 ms
Satellite
377 ms
Satellite
432 ms
Satellite
419 ms
Satellite
420 ms
pixel
41 ms
pixel
42 ms
pixel
42 ms
pixel
42 ms
Satellite
368 ms
utag.js
130 ms
util.js
29 ms
onion.js
28 ms
pixel
39 ms
pixel
39 ms
Satellite
332 ms
pixel
37 ms
pixel
36 ms
pixel
36 ms
pixel
34 ms
Satellite
362 ms
Satellite
361 ms
Satellite
386 ms
Satellite
387 ms
Satellite
435 ms
controls.js
28 ms
Satellite
441 ms
imp
66 ms
match-result
66 ms
Satellite
452 ms
Satellite
436 ms
match-result
65 ms
match-result
61 ms
match-result
61 ms
match-result
60 ms
Satellite
429 ms
transparent.png
183 ms
css
207 ms
google4.png
129 ms
mapcnt6.png
145 ms
sv5.png
146 ms
mobile.html
71 ms
tmapctrl.png
113 ms
tmapctrl4.png
127 ms
arrow-down.png
128 ms
imgs8.png
127 ms
event
34 ms
utag.1.js
33 ms
event
10 ms
js
39 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
66 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
90 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
114 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
115 ms
img
19 ms
iframe
27 ms
img
18 ms
img
18 ms
rt=ifr
14 ms
js
19 ms
5907
83 ms
g.json
24 ms
tpc=na_id
17 ms
32 ms
img
17 ms
362738.gif
7 ms
ford.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.
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
ford.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ford.mx 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
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
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ford.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 Ford.mx 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.
ford.mx
Open Graph description is not detected on the main page of Ford. 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: