5.4 sec in total
475 ms
4.5 sec
350 ms
Visit havanna.mx now to see the best up-to-date Havanna content and also check out these interesting facts you probably never knew about havanna.mx
Conocé la experiencia Havanna
Visit havanna.mxWe analyzed Havanna.mx page load time and found that the first response time was 475 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
havanna.mx performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value14.0 s
0/100
25%
Value15.1 s
1/100
10%
Value330 ms
76/100
30%
Value0.658
8/100
15%
Value15.2 s
7/100
10%
475 ms
1160 ms
344 ms
25 ms
36 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Havanna.mx, 82% (31 requests) were made to Havanna.com.ar and 5% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Havanna.com.ar.
Page size can be reduced by 214.7 kB (25%)
875.1 kB
660.4 kB
In fact, the total size of Havanna.mx main page is 875.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. 20% of websites need less resources to load. Images take 651.9 kB which makes up the majority of the site volume.
Potential reduce by 17.3 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 17.3 kB or 80% of the original size.
Potential reduce by 67.6 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. Havanna images are well optimized though.
Potential reduce by 74.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 74.9 kB or 55% of the original size.
Potential reduce by 54.9 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. Havanna.mx needs all CSS files to be minified and compressed as it can save up to 54.9 kB or 84% of the original size.
Number of requests can be reduced by 15 (47%)
32
17
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Havanna. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
havanna.mx
475 ms
1160 ms
jquery-2.1.4.min.js
344 ms
jquery.min.js
25 ms
js
36 ms
dpagination.js
611 ms
index.css
616 ms
style.css
933 ms
shortcode.css
1010 ms
superfish.js
1618 ms
comment-reply.min.js
488 ms
wp-emoji-release.min.js
302 ms
wide.css
148 ms
font.css
162 ms
6
211 ms
back-body3.png
756 ms
logo.png
308 ms
back-menu.png
180 ms
foto-locales1.png
1117 ms
footer.png
169 ms
face.png
326 ms
twitter.png
357 ms
instagram.png
369 ms
analytics.js
33 ms
GillSansMT.woff
563 ms
IntroCondBlackFree.woff
597 ms
IntroCondLightFree.woff
1054 ms
collect
11 ms
estilos.css
333 ms
jquery.js
17 ms
swfobject.js
513 ms
js
50 ms
back-mapa.png
164 ms
logo-bares.png
155 ms
foto-local.jpg
476 ms
ubicacion.png
162 ms
getLocalidades
525 ms
Intro-Cond-Black-Free.woff
298 ms
havanna.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
button, link, and menuitem elements do not have accessible names.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
havanna.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
havanna.mx SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Havanna.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 Havanna.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.
havanna.mx
Open Graph description is not detected on the main page of Havanna. 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: