8.5 sec in total
1.5 sec
6.7 sec
274 ms
Welcome to princesax.es homepage info - get ready to check Princ Es Ax best content right away, or after learning these important things about princesax.es
Visit princesax.esWe analyzed Princesax.es page load time and found that the first response time was 1.5 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
princesax.es performance score
1545 ms
765 ms
667 ms
669 ms
775 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 90% of them (80 requests) were addressed to the original Princesax.es, 2% (2 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Princesax.es.
Page size can be reduced by 859.4 kB (40%)
2.2 MB
1.3 MB
In fact, the total size of Princesax.es main page is 2.2 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 52.9 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 52.9 kB or 89% of the original size.
Potential reduce by 71.0 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. Princ Es Ax images are well optimized though.
Potential reduce by 478.8 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 478.8 kB or 73% of the original size.
Potential reduce by 256.7 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. Princesax.es needs all CSS files to be minified and compressed as it can save up to 256.7 kB or 85% of the original size.
Number of requests can be reduced by 43 (51%)
85
42
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Princ Es Ax. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
princesax.es
1545 ms
wp-emoji-release.min.js
765 ms
jquery.bxslider.css
667 ms
testimonials-widget.css
669 ms
prettyPhoto.css
775 ms
wp-video-lightbox.css
670 ms
styles.css
670 ms
all-skins.css
1128 ms
style2-os.css
884 ms
lightbox.css
887 ms
font-awesome.css
1085 ms
light_style.css
991 ms
css
24 ms
css
36 ms
style-red.css
1305 ms
logo_image.css
1098 ms
additional_link_nodisplay.css
1100 ms
description_nodisplay.css
1206 ms
scrolllink_display.css
1300 ms
style.css
1314 ms
font-awesome.css
4 ms
font-awesome-corp.css
1318 ms
font-awesome-ext.css
1339 ms
font-awesome-social.css
1421 ms
jquery.js
1849 ms
jquery-migrate.min.js
1521 ms
jquery.prettyPhoto.js
1617 ms
video-lightbox.js
1535 ms
flowplayer.min.js
1667 ms
easy-columns.css
1635 ms
jquery.form.min.js
1559 ms
scripts.js
1567 ms
jquery.colorbox.js
1752 ms
gallery-all.js
1664 ms
jquery.hugeitmicro.min.js
1804 ms
collapse.js
1885 ms
comment-reply.min.js
1787 ms
bootstrap.js
2095 ms
masonry.min.js
1991 ms
jquery.isotope.min.js
1610 ms
scripts.js
1531 ms
wp-embed.min.js
1553 ms
vidbg.min.js
1627 ms
bootstrap.css
1315 ms
headbg.jpg
434 ms
mainbg-4.png
520 ms
2016-03-16-16.12.05-360x198.jpg
216 ms
2016-03-16-16.12.05-283x156.jpg
215 ms
2016-03-16-16.12.05-220x121.jpg
218 ms
2016-03-16-16.12.05-310x171.jpg
223 ms
DSC9046-1-360x198.jpg
540 ms
DSC9046-1-283x156.jpg
434 ms
DSC9046-1-220x121.jpg
437 ms
DSC9046-1-310x171.jpg
542 ms
IMG-20151207-WA0009-360x198.jpg
758 ms
IMG-20151207-WA0009-283x156.jpg
651 ms
IMG-20151207-WA0009-220x121.jpg
653 ms
IMG-20151207-WA0009-310x171.jpg
731 ms
IMG-20160308-WA0003-360x198.jpg
867 ms
IMG-20160308-WA0003-283x156.jpg
761 ms
IMG-20160308-WA0003-220x121.jpg
867 ms
IMG-20160308-WA0003-310x171.jpg
871 ms
IMG-20160226-WA0007-360x198.jpg
1053 ms
IMG-20160226-WA0007-283x156.jpg
974 ms
IMG-20160226-WA0007-220x121.jpg
980 ms
IMG-20160226-WA0007-310x171.jpg
1187 ms
IMG-20151026-WA0002-360x198.jpg
1085 ms
IMG-20151026-WA0002-283x156.jpg
1092 ms
IMG-20151026-WA0002-220x121.jpg
1191 ms
IMG-20151026-WA0002-310x171.jpg
1192 ms
IMG-20160127-WA0002-360x198.jpg
1376 ms
IMG-20160127-WA0002-283x156.jpg
1411 ms
IMG-20160127-WA0002-220x121.jpg
1415 ms
IMG-20160127-WA0002-310x171.jpg
1512 ms
IMG-20160118-WA0003-1-360x198.jpg
1516 ms
IMG-20160118-WA0003-1-283x156.jpg
1409 ms
IMG-20160118-WA0003-1-220x121.jpg
1591 ms
IMG-20160118-WA0003-1-310x171.jpg
1731 ms
embed
206 ms
headlinered.png
1726 ms
patternbg1.png
1840 ms
FUDHvzEKSJww3kCxuiAo2A.ttf
34 ms
0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf
34 ms
fontawesome-webfont.woff
33 ms
ajax-loader.gif
1520 ms
princesax.es
2044 ms
js
42 ms
init_embed.js
30 ms
blackbackground.png
2445 ms
princesax.es SEO score
N/A
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Princesax.es 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), while the claimed language is Spanish. Our system also found out that Princesax.es 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.
princesax.es
Open Graph description is not detected on the main page of Princ Es Ax. 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: