3 sec in total
351 ms
1.9 sec
738 ms
Visit alejandroherrero.com now to see the best up-to-date Alejandro Herrero content and also check out these interesting facts you probably never knew about alejandroherrero.com
Visit alejandroherrero.comWe analyzed Alejandroherrero.com page load time and found that the first response time was 351 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
alejandroherrero.com performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value3.4 s
66/100
25%
Value4.2 s
77/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.7 s
97/100
10%
351 ms
340 ms
420 ms
216 ms
314 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 57% of them (20 requests) were addressed to the original Alejandroherrero.com, 14% (5 requests) were made to Fonts.gstatic.com and 11% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (459 ms) belongs to the original domain Alejandroherrero.com.
Page size can be reduced by 329.5 kB (47%)
701.7 kB
372.3 kB
In fact, the total size of Alejandroherrero.com main page is 701.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 345.0 kB which makes up the majority of the site volume.
Potential reduce by 17.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. This page needs HTML code to be minified as it can gain 3.1 kB, which is 14% 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 17.4 kB or 79% of the original size.
Potential reduce by 4.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. Alejandro Herrero images are well optimized though.
Potential reduce by 228.9 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 228.9 kB or 66% of the original size.
Potential reduce by 78.4 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. Alejandroherrero.com needs all CSS files to be minified and compressed as it can save up to 78.4 kB or 44% of the original size.
Number of requests can be reduced by 13 (50%)
26
13
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Alejandro Herrero. 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 5 to 1 for CSS and as a result speed up the page load time.
alejandroherrero.com
351 ms
www.alejandroherrero.com
340 ms
jquery.min.js
420 ms
jquery.scrolly.min.js
216 ms
skel.min.js
314 ms
init.js
212 ms
api.js
45 ms
jquery-1.10.2.min.js
26 ms
script.js
208 ms
404.php
146 ms
style.css
113 ms
style-desktop.css
115 ms
css
23 ms
font-awesome.min.css
111 ms
recaptcha__en.js
178 ms
pic00.jpg
282 ms
bg.png
277 ms
2015-11-19.09.53.35.jpg
275 ms
2015-11-01-Visita-a-Silla-Valencia-Cementerio-Pueblo-034.jpg
459 ms
2015-11-04.02.11.01-1.jpg
357 ms
2015-11-19.09.53.27.jpg
357 ms
2015-11-19.09.53.36.jpg
360 ms
2015-12-18.06.24.05.jpg
359 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
42 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
52 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
72 ms
fontawesome-webfont.woff
326 ms
anchor
41 ms
styles__ltr.css
10 ms
-FHGegChvKELgmHNPF97Aj33qC9PBXl7UyexHItfpAU.js
15 ms
webworker.js
20 ms
logo_48.png
13 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
69 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
81 ms
recaptcha__en.js
13 ms
alejandroherrero.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
alejandroherrero.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
alejandroherrero.com SEO score
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alejandroherrero.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Alejandroherrero.com 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.
alejandroherrero.com
Open Graph description is not detected on the main page of Alejandro Herrero. 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: