1.8 sec in total
415 ms
1.1 sec
296 ms
Visit pozoazul.com now to see the best up-to-date Pozo Azul content and also check out these interesting facts you probably never knew about pozoazul.com
Un rancho de 2000 acres se ha convertido en el destino de aventura de elección en Costa Rica, a sólo 90 minutos de San José o el Volcán Arenal o 2 horas de Puerto Limón, usted disfrutará de una amplia...
Visit pozoazul.comWe analyzed Pozoazul.com page load time and found that the first response time was 415 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
pozoazul.com performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value1.4 s
100/100
25%
Value1.4 s
100/100
10%
Value0 ms
100/100
30%
Value0.032
100/100
15%
Value1.4 s
100/100
10%
415 ms
144 ms
145 ms
199 ms
162 ms
Our browser made a total of 34 requests to load all elements on the main page. We found that 94% of them (32 requests) were addressed to the original Pozoazul.com, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (520 ms) belongs to the original domain Pozoazul.com.
Page size can be reduced by 93.1 kB (17%)
539.3 kB
446.2 kB
In fact, the total size of Pozoazul.com main page is 539.3 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 422.7 kB which makes up the majority of the site volume.
Potential reduce by 15.4 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 2.5 kB, which is 12% 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 15.4 kB or 74% of the original size.
Potential reduce by 23.9 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. Pozo Azul images are well optimized though.
Potential reduce by 48.6 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 48.6 kB or 55% of the original size.
Potential reduce by 5.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. Pozoazul.com needs all CSS files to be minified and compressed as it can save up to 5.2 kB or 76% of the original size.
Number of requests can be reduced by 9 (27%)
33
24
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pozo Azul. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
pozoazul.com
415 ms
flashobject.js
144 ms
funciones.js
145 ms
js-galeria.js
199 ms
styles.css
162 ms
styletemplate.css
161 ms
jquery-1.3.2.min.js
309 ms
logo05.png
95 ms
logo04.png
105 ms
logo06.png
96 ms
fondo-header.jpg
77 ms
header.jpg
182 ms
linea-top.png
170 ms
sp2.png
191 ms
eng1.png
175 ms
fondo-cuerpo.jpg
179 ms
fondo-menu.jpg
180 ms
logos2.jpg
325 ms
L2.jpg
249 ms
L3.jpg
256 ms
L1.jpg
257 ms
titu-index.jpg
274 ms
caballos13.jpg
353 ms
rapelpsd.jpg
519 ms
caminata10.jpg
420 ms
ciclismo13.jpg
391 ms
canopy12.jpg
347 ms
indexfoto1.jpg
476 ms
indexfoto2.jpg
449 ms
indexfoto3.jpg
520 ms
footer.jpg
466 ms
fondo-footer.jpg
367 ms
ga.js
7 ms
__utm.gif
11 ms
pozoazul.com 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
pozoazul.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
pozoazul.com 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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pozoazul.com 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 Pozoazul.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.
pozoazul.com
Open Graph description is not detected on the main page of Pozo Azul. 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: