6.4 sec in total
928 ms
2.6 sec
2.9 sec
Click here to check amazing Ernesto Perez content. Otherwise, check out these important facts you probably never knew about ernestoperez.com
Member of SKCC#7163T
Visit ernestoperez.comWe analyzed Ernestoperez.com page load time and found that the first response time was 928 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ernestoperez.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value15.8 s
0/100
25%
Value12.1 s
4/100
10%
Value2,960 ms
3/100
30%
Value0
100/100
15%
Value16.2 s
6/100
10%
928 ms
35 ms
68 ms
115 ms
96 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 36% of them (39 requests) were addressed to the original Ernestoperez.com, 19% (21 requests) were made to Pixel.wp.com and 9% (10 requests) were made to Graph.facebook.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source I0.wp.com.
Page size can be reduced by 1.1 MB (60%)
1.9 MB
747.0 kB
In fact, the total size of Ernestoperez.com main page is 1.9 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. Javascripts take 986.1 kB which makes up the majority of the site volume.
Potential reduce by 109.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 109.8 kB or 75% of the original size.
Potential reduce by 2.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. Ernesto Perez images are well optimized though.
Potential reduce by 652.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 652.9 kB or 66% of the original size.
Potential reduce by 352.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. Ernestoperez.com needs all CSS files to be minified and compressed as it can save up to 352.2 kB or 80% of the original size.
Number of requests can be reduced by 82 (77%)
107
25
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ernesto Perez. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
ernestoperez.com
928 ms
cloudflare.min.js
35 ms
wp-emoji-release.min.js
68 ms
twentyfourteen.css
115 ms
openid.css
96 ms
mediaelementplayer.min.css
129 ms
wp-mediaelement.css
80 ms
css
73 ms
genericons.css
152 ms
style.css
155 ms
twentyfourteen.css
184 ms
lazyest-style.css
184 ms
_slideshow.css
186 ms
_ajax.css
189 ms
jetpack.css
201 ms
jquery.js
218 ms
jquery-migrate.min.js
196 ms
spin.js
209 ms
jquery.spin.js
217 ms
infinity.js
136 ms
jquery.cycle.js
136 ms
slideshow-shortcode.js
135 ms
photon.js
136 ms
devicepx-jetpack.js
20 ms
jetpack-carousel.js
205 ms
mediaelement-and-player.min.js
209 ms
wp-mediaelement.js
203 ms
gprofiles.js
128 ms
wpgroho.js
204 ms
masonry.min.js
205 ms
jquery.masonry.min.js
205 ms
functions.js
207 ms
lazyest-gallery.js
205 ms
wp-embed.min.js
208 ms
postmessage.js
206 ms
jquery.jetpack-resize.js
311 ms
jquery.inview.js
373 ms
queuehandler.js
382 ms
sharing.js
393 ms
e-201611.js
11 ms
ga.js
58 ms
IMG_1212.jpg
1248 ms
IMG_1215.jpg
307 ms
IMG_1222.jpg
1247 ms
IMG_1269.jpg
1248 ms
IMG_1280.jpg
1240 ms
cropped-HC6PE-Credencial1.jpg
1150 ms
loading.gif
315 ms
img.gif
189 ms
O7fZa5NwH_4
94 ms
Genericons.svg
1021 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
1 ms
www-embed-player-vfl8xM8me.css
26 ms
www-embed-player.js
44 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
944 ms
ad_status.js
949 ms
master.html
918 ms
hovercard.css
141 ms
services.css
163 ms
share
223 ms
g.gif
138 ms
graph.facebook.com
234 ms
share
250 ms
graph.facebook.com
337 ms
share
276 ms
graph.facebook.com
351 ms
share
276 ms
graph.facebook.com
357 ms
share
236 ms
graph.facebook.com
353 ms
share
231 ms
graph.facebook.com
359 ms
share
232 ms
graph.facebook.com
341 ms
share
282 ms
graph.facebook.com
448 ms
share
281 ms
graph.facebook.com
468 ms
share
243 ms
graph.facebook.com
460 ms
g.gif
111 ms
g.gif
111 ms
g.gif
111 ms
g.gif
111 ms
g.gif
111 ms
g.gif
114 ms
g.gif
114 ms
g.gif
112 ms
g.gif
113 ms
g.gif
112 ms
g.gif
111 ms
g.gif
116 ms
g.gif
114 ms
g.gif
116 ms
g.gif
113 ms
g.gif
115 ms
g.gif
115 ms
g.gif
116 ms
g.gif
116 ms
g.gif
115 ms
jquery.js
46 ms
postmessage.js
6 ms
jed.js
6 ms
underscore.min.js
7 ms
jquery.wpcom-proxy-request.js
1 ms
18 ms
13 ms
likes-rest.js
2 ms
batch
94 ms
ernestoperez.com 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-*] attributes do not match their roles
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
ernestoperez.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
ernestoperez.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ernestoperez.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ernestoperez.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.
ernestoperez.com
Open Graph data is detected on the main page of Ernesto Perez. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: