2.5 sec in total
688 ms
1.6 sec
246 ms
Visit cuba.to now to see the best up-to-date Cuba content and also check out these interesting facts you probably never knew about cuba.to
The best place to backorder/drop purchase expiring ccTLD domain names
Visit cuba.toWe analyzed Cuba.to page load time and found that the first response time was 688 ms and then it took 1.8 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.
cuba.to performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value4.9 s
29/100
25%
Value3.2 s
92/100
10%
Value110 ms
98/100
30%
Value0
100/100
15%
Value4.2 s
85/100
10%
688 ms
207 ms
7 ms
626 ms
175 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 55% of them (23 requests) were addressed to the original Cuba.to, 14% (6 requests) were made to Tpc.googlesyndication.com and 12% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (688 ms) belongs to the original domain Cuba.to.
Page size can be reduced by 59.8 kB (32%)
185.1 kB
125.2 kB
In fact, the total size of Cuba.to main page is 185.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. 30% of websites need less resources to load. Images take 102.8 kB which makes up the majority of the site volume.
Potential reduce by 30.1 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 6.9 kB, which is 19% 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 30.1 kB or 82% of the original size.
Potential reduce by 1.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. Cuba images are well optimized though.
Potential reduce by 23.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 23.9 kB or 59% of the original size.
Potential reduce by 4.8 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. Cuba.to needs all CSS files to be minified and compressed as it can save up to 4.8 kB or 88% of the original size.
Number of requests can be reduced by 19 (46%)
41
22
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cuba. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
cuba.to
688 ms
cuba.css
207 ms
show_ads.js
7 ms
ga.js
626 ms
cuba.jpg
175 ms
com.jpg
157 ms
slogan_eng.jpg
286 ms
back.gif
159 ms
home.gif
175 ms
go.gif
175 ms
directorio_eng.jpg
211 ms
directorio_end.jpg
240 ms
playa.jpg
245 ms
mascota-jardines-del-rey.jpg
355 ms
nh-parque-central.jpg
353 ms
sol-palmeras.jpg
287 ms
paradisus-rio-de-oro.jpg
308 ms
arcoriris.jpg
321 ms
14.jpg
418 ms
directorio_bg.jpg
359 ms
ca-pub-4172765971253062.js
58 ms
zrt_lookup.html
52 ms
show_ads_impl.js
55 ms
noticias.jpg
347 ms
separador.jpg
353 ms
destinos.jpg
388 ms
recomendado.jpg
386 ms
ads
344 ms
osd.js
18 ms
ads
293 ms
ads
289 ms
11201373089270006759
41 ms
abg.js
44 ms
m_js_controller.js
62 ms
googlelogo_color_112x36dp.png
42 ms
8014852937356845947
49 ms
s
89 ms
x_button_blue2.png
105 ms
favicon
105 ms
nessie_icon_tiamat_white.png
42 ms
__utm.gif
36 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
28 ms
cuba.to 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
cuba.to 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
General
Impact
Issue
Detected JavaScript libraries
cuba.to SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cuba.to can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Cuba.to main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
cuba.to
Open Graph description is not detected on the main page of Cuba. 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: