6.1 sec in total
2 sec
3.9 sec
225 ms
Visit globalo2.es now to see the best up-to-date GLOBAL O2 content and also check out these interesting facts you probably never knew about globalo2.es
Consultoria en Calidad ISO 9001 Medio Ambiente ISO 14001 Seguridad ISO 45001 ISO 22320 ISO 39001 Energía ISO 50001 UNE 166002 Tel 91.425.47.71
Visit globalo2.esWe analyzed Globalo2.es page load time and found that the first response time was 2 sec and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
globalo2.es performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value16.0 s
0/100
25%
Value29.4 s
0/100
10%
Value17,350 ms
0/100
30%
Value0.032
100/100
15%
Value34.7 s
0/100
10%
1961 ms
111 ms
214 ms
218 ms
222 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 80% of them (72 requests) were addressed to the original Globalo2.es, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Wd-edge.sharethis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Globalo2.es.
Page size can be reduced by 999.5 kB (61%)
1.7 MB
652.3 kB
In fact, the total size of Globalo2.es main page is 1.7 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. 50% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 62.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. 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 62.0 kB or 85% of the original size.
Potential reduce by 15.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. GLOBAL O2 images are well optimized though.
Potential reduce by 842.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 842.9 kB or 79% of the original size.
Potential reduce by 78.7 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. Globalo2.es needs all CSS files to be minified and compressed as it can save up to 78.7 kB or 82% of the original size.
Number of requests can be reduced by 52 (60%)
87
35
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GLOBAL O2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
globalo2.es
1961 ms
style.css
111 ms
prettyPhoto.css
214 ms
style.css
218 ms
styles.css
222 ms
cli-style.css
223 ms
styles.css
224 ms
jquery.min.js
33 ms
tubepress.js
228 ms
jquery.easing.1.3.js
323 ms
swfobject.js
323 ms
cufon-yui.js
329 ms
Museo.font.js
682 ms
hoverIntent.js
330 ms
jquery.bgiframe.min.js
339 ms
superfish.js
427 ms
supersubs.js
431 ms
jquery.prettyPhoto.js
439 ms
jquery.nivo.slider.js
440 ms
jquery.cycle.js
451 ms
jquery.innerfade.js
533 ms
jquery.quicksand.js
538 ms
flowplayer.3.2.4.js
546 ms
screen.js
549 ms
ie6w_top.js
561 ms
comment-reply.min.js
639 ms
modernizr-2.6.2.min.js
645 ms
jquery.cookie.js
655 ms
cookielawinfo.js
658 ms
jquery.cycle.all.min.js
676 ms
buttons.js
11 ms
blue.css
743 ms
jquery.form.min.js
751 ms
scripts.js
760 ms
reset.css
671 ms
base.css
688 ms
screen.css
693 ms
print.css
755 ms
ga.js
142 ms
aenor1.png
333 ms
Globalo2.png
223 ms
search_bg.png
222 ms
search_btn.png
222 ms
calidad2.jpg
224 ms
medioAmbiente2.jpg
223 ms
seguridad4.jpg
334 ms
energia.jpg
426 ms
analisisRiesgoAmbiental1.jpg
433 ms
servicios.png
251 ms
sombraVertical.png
326 ms
areas.png
333 ms
sectores.png
339 ms
businessman_woman1-60x60.png
432 ms
star_full1-60x60.png
441 ms
truck-60x60.png
443 ms
btn-canaltv.png
561 ms
presentacion-corporativa.jpg
532 ms
empresa.png
540 ms
sombra.png
541 ms
nuestrosValores.png
550 ms
CONTACTO.png
553 ms
youtube.png
636 ms
linkedin.png
649 ms
twitter.png
650 ms
rss.png
657 ms
Global-o2-pie.png
661 ms
big_box_bottom_bg.png
653 ms
separator.gif
719 ms
sombra_grande_down.png
733 ms
bullet_arrow_blue.png
734 ms
sombra_grande_up.png
742 ms
footer_separator.gif
747 ms
getAllAppDefault.esi
257 ms
slider_nav_selected1.png
568 ms
slider_nav1.png
632 ms
__utm.gif
16 ms
getSegment.php
11 ms
checkOAuth.esi
83 ms
t.dhj
51 ms
t.dhj
31 ms
cm
30 ms
s-3271.xgi
7 ms
hbpix
88 ms
9 ms
9 ms
xrefid.xgi
6 ms
pixel
22 ms
pixel
19 ms
2981
40 ms
lightbox_video2.png
113 ms
globalo2.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 input fields do not have accessible names
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
globalo2.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
globalo2.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 Globalo2.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 Globalo2.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.
globalo2.es
Open Graph data is detected on the main page of GLOBAL O2. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: