4.1 sec in total
426 ms
3.6 sec
118 ms
Click here to check amazing Globus content. Otherwise, check out these important facts you probably never knew about globus.es
Visit globus.esWe analyzed Globus.es page load time and found that the first response time was 426 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
globus.es performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value12.2 s
0/100
25%
Value12.2 s
3/100
10%
Value620 ms
48/100
30%
Value0.17
70/100
15%
Value12.5 s
14/100
10%
426 ms
149 ms
278 ms
663 ms
265 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 96% of them (51 requests) were addressed to the original Globus.es, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Globus.es.
Page size can be reduced by 207.0 kB (26%)
794.7 kB
587.7 kB
In fact, the total size of Globus.es main page is 794.7 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 529.6 kB which makes up the majority of the site volume.
Potential reduce by 12.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 12.3 kB or 82% of the original size.
Potential reduce by 17.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. Globus images are well optimized though.
Potential reduce by 151.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 151.2 kB or 69% of the original size.
Potential reduce by 25.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. Globus.es needs all CSS files to be minified and compressed as it can save up to 25.6 kB or 84% of the original size.
Number of requests can be reduced by 11 (21%)
52
41
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Globus. 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.
globus.es
426 ms
global.css
149 ms
ajax.js
278 ms
jquery.min.js
663 ms
banner-rotator.css
265 ms
jquery.easing.1.3.min.js
261 ms
jquery.banner-rotator.js
576 ms
bg_top.jpg
183 ms
logobn.jpg
315 ms
igual.jpg
178 ms
bg_tg.jpg
173 ms
mas.jpg
198 ms
bg_cg.jpg
191 ms
bg_f.jpg
322 ms
bg_mu.jpg
292 ms
70_imatge_gestor.jpg
319 ms
67_imatge_gestor.jpg
339 ms
53_imatge_gestor.jpg
334 ms
50_imatge_gestor.jpg
423 ms
52_imatge_gestor.jpg
462 ms
51_imatge_gestor.jpg
441 ms
54_imatge_gestor.jpg
447 ms
55_imatge_gestor.jpg
458 ms
56_imatge_gestor.jpg
486 ms
57_imatge_gestor.jpg
536 ms
68_imatge_gestor.jpg
562 ms
58_imatge_gestor.jpg
587 ms
59_imatge_gestor.jpg
629 ms
60_imatge_gestor.jpg
639 ms
61_imatge_gestor.jpg
666 ms
62_imatge_gestor.jpg
650 ms
63_imatge_gestor.jpg
683 ms
64_imatge_gestor.jpg
716 ms
65_imatge_gestor.jpg
754 ms
6_principal.jpg
949 ms
9_principal.jpg
1237 ms
10_principal.jpg
1077 ms
15_principal.jpg
937 ms
bg_peu.jpg
860 ms
logo_p.jpg
869 ms
issuu.jpg
1002 ms
twitter_small.jpg
1013 ms
vimeo_small.jpg
1048 ms
ga.js
4 ms
__utm.gif
12 ms
flikr_small.jpg
910 ms
pinterest_small.jpg
978 ms
loader.gif
971 ms
br-assets.png
990 ms
65_imatge.jpg
1306 ms
70_imatge.jpg
1478 ms
64_imatge.jpg
713 ms
63_imatge.jpg
257 ms
globus.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
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
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
globus.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
globus.es SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Globus.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish 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 Globus.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.
globus.es
Open Graph description is not detected on the main page of Globus. 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: