2.1 sec in total
193 ms
1.7 sec
223 ms
Visit itztli.es now to see the best up-to-date Itztli content and also check out these interesting facts you probably never knew about itztli.es
Itztli
Visit itztli.esWe analyzed Itztli.es page load time and found that the first response time was 193 ms and then it took 1.9 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.
itztli.es performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value8.0 s
2/100
25%
Value7.4 s
28/100
10%
Value860 ms
33/100
30%
Value0.197
63/100
15%
Value6.8 s
55/100
10%
193 ms
694 ms
27 ms
52 ms
54 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 73% of them (37 requests) were addressed to the original Itztli.es, 4% (2 requests) were made to Fonts.googleapis.com and 4% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (694 ms) belongs to the original domain Itztli.es.
Page size can be reduced by 577.0 kB (63%)
919.1 kB
342.1 kB
In fact, the total size of Itztli.es main page is 919.1 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. 45% of websites need less resources to load. Javascripts take 440.5 kB which makes up the majority of the site volume.
Potential reduce by 22.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 22.8 kB or 74% of the original size.
Potential reduce by 22.5 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. Obviously, Itztli needs image optimization as it can save up to 22.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 316.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 316.1 kB or 72% of the original size.
Potential reduce by 215.6 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. Itztli.es needs all CSS files to be minified and compressed as it can save up to 215.6 kB or 83% of the original size.
Number of requests can be reduced by 39 (80%)
49
10
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Itztli. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
itztli.es
193 ms
www.itztli.es
694 ms
modal.css
27 ms
k2.css
52 ms
normalize.css
54 ms
layout.css
50 ms
joomla.css
54 ms
system.css
52 ms
template.css
55 ms
menu.css
73 ms
font-awesome.css
75 ms
gk.stuff.css
80 ms
vm.css
81 ms
style1.css
78 ms
typography.style1.css
82 ms
css
26 ms
style.css
103 ms
jquery-1.11.2.min.js
7 ms
jquery-migrate-1.2.1.min.js
8 ms
chosen.jquery.min.js
8 ms
jquery.easing.min.js
14 ms
jquery-noconflict.js
125 ms
bootstrap.min.js
128 ms
mootools-core.js
170 ms
core.js
124 ms
mootools-more.js
226 ms
modal.js
126 ms
gk.scripts.js
134 ms
gk.menu.js
133 ms
fitvids.jquery.js
151 ms
script.jquery.js
150 ms
override.css
152 ms
style.min.css
357 ms
plugin.min.js
526 ms
platform.js
36 ms
widgets.js
132 ms
pinit.js
9 ms
small.desktop.css
27 ms
tablet.css
27 ms
small.tablet.css
27 ms
mobile.css
27 ms
webfont.js
65 ms
banner_paypal.jpg
66 ms
PinExt.png
13 ms
banner_marcas.jpg
100 ms
logo_chapultepec.png
78 ms
logo.png
53 ms
cookieconsent.silktide.com
174 ms
fontawesome-webfont.woff
50 ms
css
14 ms
gkfont.ttf
26 ms
itztli.es 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
itztli.es 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
itztli.es 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
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Itztli.es 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 Itztli.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.
itztli.es
Open Graph description is not detected on the main page of Itztli. 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: