1.7 sec in total
43 ms
1.4 sec
178 ms
Click here to check amazing Fernando Martinez content for Mexico. Otherwise, check out these important facts you probably never knew about fernandomartinez.mx
Fernando Arturo Martínez Aguilar: Experto en inbound marketing para empresas de México, programador y especialista en posicionamiento web.
Visit fernandomartinez.mxWe analyzed Fernandomartinez.mx page load time and found that the first response time was 43 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
fernandomartinez.mx performance score
name
value
score
weighting
Value1.6 s
94/100
10%
Value2.5 s
90/100
25%
Value23.9 s
0/100
10%
Value15,780 ms
0/100
30%
Value0.188
65/100
15%
Value36.2 s
0/100
10%
43 ms
323 ms
30 ms
39 ms
580 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 20% of them (15 requests) were addressed to the original Fernandomartinez.mx, 59% (45 requests) were made to Cdn.shopify.com and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (580 ms) relates to the external source Shopify.com.
Page size can be reduced by 83.8 kB (4%)
2.3 MB
2.2 MB
In fact, the total size of Fernandomartinez.mx main page is 2.3 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.0 MB which makes up the majority of the site volume.
Potential reduce by 36.6 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 36.6 kB or 75% of the original size.
Potential reduce by 10.1 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. Fernando Martinez images are well optimized though.
Potential reduce by 37.1 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 37.1 kB or 18% of the original size.
Potential reduce by 0 B
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.
Number of requests can be reduced by 9 (13%)
71
62
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fernando Martinez. 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 as a result speed up the page load time.
fernandomartinez.mx
43 ms
www.fernandomartinez.mx
323 ms
load.sumome.com
30 ms
bdg_secured_by_pp_2line.png
39 ms
www.shopify.com
580 ms
email-decode.min.js
17 ms
133c8ee20ab6e3de6e155004989f1cf7.js
221 ms
fernando-martinez.png
92 ms
fernando-martinez-especialista-en-inbound-marketing.jpg
148 ms
ecommerce-mistakes.jpg
166 ms
como-aprovechar-instagram-stories-en-tu-marketing.png
171 ms
marketing-automotriz-en-los-juegos-olimpicos.png
219 ms
porque-deberias-considerar-el-inbound-marketing.png
300 ms
marketing-realidad-virtual.png
376 ms
5-ideas-para-fortalecer-tu-marketing-digital-en-redes-sociales.png
385 ms
sumome.js
23 ms
a9c876d8845491bc4777eb4fa405cca0.css
333 ms
gtm.js
124 ms
fontawesome-webfont.woff
169 ms
avion.woff
125 ms
analytics.js
32 ms
hotjar-1245145.js
115 ms
jquery.min.js
46 ms
collect
41 ms
collect
42 ms
collect
336 ms
js
55 ms
collect
337 ms
js
259 ms
home-76C36TVR.css
167 ms
339113bc828c2c7ab760a434e1703b93.webp
244 ms
59c9580201098febc263baf2cf90550b.png
241 ms
1d6091ce14b313a3c9a19f237df898bb.svgz
205 ms
c99f9bb49ec7dec96678765339586edc.svgz
203 ms
68388f12ce9faef230ada91e20f69cc2.svgz
149 ms
04f205245f06d35f87b53d2ee1ba5969.svgz
312 ms
d8428f5c0d6ecc96260b1eafaf173341.svgz
316 ms
40a70b395afc3c391953470089e1f58a.svgz
309 ms
29a20784f322b566e3f71ebb2bf9d6bb.svgz
310 ms
cf32724c718f09d23eef5489f79bf6b9.svgz
314 ms
cd55dad309f3f66eb1b1fd5d6642e0f5.svgz
312 ms
b450e474f3bfd464cfe5b6fcd8898c0b.svgz
328 ms
6ba4ddb8ff7a023fc6b50baae7545327.svgz
334 ms
702bc0fe7229acdef65d55f7ae1422ab.svgz
332 ms
de31ef32fb09a2d9f77119fd110ea6c6.svgz
337 ms
f3ed9ee7ea392d376acc1508613c45fc.svgz
332 ms
417301e08872b3bb26b3eb9f66a1be15.svgz
338 ms
d6b0f1bf898eb9c237be5736edcf5c81.svgz
354 ms
68a396597aff07c2aa75e1c96a7b99c1.svgz
363 ms
7513d2889de95ef0e01a95d970c4ec41.svgz
365 ms
588ae6c3404d22f5a482edf04c053aa6.svgz
360 ms
99655287608ae75a0afc5b3cf27ace73.svgz
389 ms
88903dcc49157f65e0c11dd1bbab1042.svgz
358 ms
d7c2832fee460b4e7b90d2620f0149e6.svgz
382 ms
a5338c3f79a6e291b743e0149035a5fa.svgz
379 ms
671c798183eab1529bbc4abb287fa2b3.svgz
397 ms
2106514f331beeeae3475bfb029d3330.svgz
391 ms
4a49a74df0056108b39f9f8657ed3a85.svgz
392 ms
fa87c2035b450b03766d25537d3056ed.svgz
403 ms
80f475ddd49655a5fbbb3ca479c78213.svgz
404 ms
45f080d8ca27225884ba1714123870c3.svgz
426 ms
de19891ee27475ae8f8880223ef1ac4a.svgz
415 ms
62c82332fcc9e4df60ff570deb675d3e.svgz
421 ms
b19e0c0d8f45827afd3a9b73f8a145a0.svgz
429 ms
6a1ff42b8323326c31f69e7559a7bd14.svgz
426 ms
modules.4d9dd1518dc89987e57a.js
233 ms
cf717a7b1fbd3b1f4160cf39a1c96e19.svgz
277 ms
f5d0030128dfafb20b4b20353078a461.svgz
257 ms
21927a034afd34391db39cf2b7ecf709.svgz
252 ms
layers-75e27771a1461d41eeea6d3776873fcf0dca705afb334adadb0c7dc0a20b0404.svg
248 ms
infinity-ea665cc8ef4b2379465495ba43cd5cdbba88cd70dd51c6fa59aec331fd2336be.svg
214 ms
partners-d453b53d9ff10a630080d24563478935f3d1b10de8eb15bef9f13fe58be3f8de.svg
143 ms
dev-82bdbe630a35ca679000d2177f4e32d44b5455e906f0a7ff628c3eadbee38c8e.svg
174 ms
fc4cebbadfd9af383ccd031219260b7d.svg
156 ms
bc2165e8963e937c15a77355632344df.webp
175 ms
ga-audiences
82 ms
fernandomartinez.mx 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
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
fernandomartinez.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fernandomartinez.mx 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
![]()
ES
![]()
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fernandomartinez.mx 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 Fernandomartinez.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.
fernandomartinez.mx
Open Graph description is not detected on the main page of Fernando Martinez. 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: