6.6 sec in total
341 ms
5.2 sec
1 sec
Visit pangea.es now to see the best up-to-date PANGEA content for Spain and also check out these interesting facts you probably never knew about pangea.es
¡La tienda de viajes más grande del mundo te espera! Asesores expertos en viajes a medida, miles de m2, eventos… ¡Más que una agencia de viajes!
Visit pangea.esWe analyzed Pangea.es page load time and found that the first response time was 341 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
pangea.es performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value6.1 s
12/100
25%
Value7.1 s
31/100
10%
Value910 ms
31/100
30%
Value0.514
15/100
15%
Value13.8 s
10/100
10%
341 ms
334 ms
1698 ms
113 ms
222 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 39% of them (27 requests) were addressed to the original Pangea.es, 33% (23 requests) were made to D12xfnpxdgf5zf.cloudfront.net and 6% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Pangea.es.
Page size can be reduced by 1.6 MB (45%)
3.6 MB
2.0 MB
In fact, the total size of Pangea.es main page is 3.6 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. 60% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 61.0 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 18.7 kB, which is 25% 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 61.0 kB or 83% of the original size.
Potential reduce by 178.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. PANGEA images are well optimized though.
Potential reduce by 778.2 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 778.2 kB or 69% of the original size.
Potential reduce by 571.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. Pangea.es needs all CSS files to be minified and compressed as it can save up to 571.2 kB or 87% of the original size.
Number of requests can be reduced by 22 (34%)
64
42
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PANGEA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
pangea.es
341 ms
www.pangea.es
334 ms
www.pangea.es
1698 ms
fontlato-400-700.css
113 ms
normalize.min.css
222 ms
swiper.min.css
322 ms
select2.min.css
323 ms
styles.css
781 ms
jquery-1.11.2.min.js
551 ms
jquery-ui-1.11.4.min.js
952 ms
jquery.ui.touch-punch.min.js
349 ms
locale.js
424 ms
plugins.min.js
987 ms
components.min.js
694 ms
keyboard.css
529 ms
jquery.keyboard.js
1153 ms
gtm.js
366 ms
phplNkCng56cf069d0eaa0_340x375.jpeg
783 ms
141775808
461 ms
141875136
438 ms
phpktUHoM56ebd9986e372_340x375.jpeg
816 ms
phpeRYma456ebeb74b2cd7_340x375.jpeg
812 ms
phpebIpis56cd8a6820b39_340x375.jpeg
816 ms
phplAF2VG56eaa48227831_340x375.jpeg
900 ms
phplDuoDx56ebf6f69dd58_340x375.jpeg
814 ms
phpCqiIGj560d19b96d880_340x375.jpeg
993 ms
phpFbMfXf56c3089eeee75_627x404.jpeg
1153 ms
phpovQW3256b9ea1e9566c_627x404.jpeg
1145 ms
phpuSyPkO56b9ea49554ba_313x218.jpeg
1138 ms
phpP9VVb356b9ea847ff04_470x363.jpeg
1140 ms
php4Fh7Sx56b9eaaed7fd0_627x404.jpeg
1252 ms
phpr7gOKS56b9eadcbccda_470x363.jpeg
1387 ms
white-lines.jpg
547 ms
icons.png
548 ms
spheres.png
631 ms
white-lines.gif
860 ms
white-lines-footer.gif
365 ms
logo-footer.png
300 ms
icons-footer.png
812 ms
Lato-Regular.woff
476 ms
Lato-Bold.woff
726 ms
Geometria-Bold.woff
726 ms
phpf3frJg56d8319b5fb9f_1600x1075.jpeg
1239 ms
phpc4c60l56d945d154715_744x670.jpeg
1210 ms
phptq6Ohh56dd6aa10bda3_330x360.jpeg
1221 ms
phpbCZFvJ56d9d9e2b063c_330x360.jpeg
1222 ms
php9Ds3Bq55f16e44829ea_330x360.jpeg
1322 ms
php6G46BJ56e927c8e1b63_330x360.jpeg
1459 ms
phpXtM9Sa55e436c124238_330x360.jpeg
1547 ms
phpQQ4VxX55e41b9565a38_330x360.jpeg
1553 ms
phpVYpl9Y56cf076bae0df_1024x370.jpeg
1546 ms
phpLKZwNX56266c609b506_1600x800.jpeg
1655 ms
logo-home.png
498 ms
iadvize.js
653 ms
analytics.js
61 ms
linkid.js
34 ms
ec.js
34 ms
player.js
233 ms
player.css
210 ms
ga.js
151 ms
vuid.min.js
223 ms
collect
62 ms
collect
294 ms
__utm.gif
147 ms
__utm.gif
132 ms
proxy.html
131 ms
539044179.webp
140 ms
nr-885.min.js
101 ms
storage.local.php
94 ms
689d5b4562
108 ms
pangea.es 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
[aria-*] attributes do not match their roles
[aria-*] attributes do not have valid values
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
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
pangea.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
pangea.es SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Pangea.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 Pangea.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.
pangea.es
Open Graph description is not detected on the main page of PANGEA. 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: