5.9 sec in total
403 ms
5 sec
519 ms
Welcome to otp.es homepage info - get ready to check OTP best content right away, or after learning these important things about otp.es
Servicios de prevención de riesgos laborales. Asesoramiento en materia de condiciones de trabajo, higiene industrial, ergonomía, vigilancia de la salud...
Visit otp.esWe analyzed Otp.es page load time and found that the first response time was 403 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
otp.es performance score
name
value
score
weighting
Value10.8 s
0/100
10%
Value20.8 s
0/100
25%
Value14.3 s
1/100
10%
Value830 ms
35/100
30%
Value0
100/100
15%
Value23.3 s
1/100
10%
403 ms
546 ms
595 ms
425 ms
576 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Otp.es, 49% (60 requests) were made to Grupotp.org and 9% (11 requests) were made to W.sharethis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Grupotp.org.
Page size can be reduced by 859.0 kB (36%)
2.4 MB
1.6 MB
In fact, the total size of Otp.es main page is 2.4 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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 44.2 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 14.2 kB, which is 26% 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 44.2 kB or 82% of the original size.
Potential reduce by 33.0 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. OTP images are well optimized though.
Potential reduce by 591.0 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 591.0 kB or 64% of the original size.
Potential reduce by 190.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. Otp.es needs all CSS files to be minified and compressed as it can save up to 190.8 kB or 82% of the original size.
Number of requests can be reduced by 59 (51%)
116
57
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OTP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
otp.es
403 ms
www.grupotp.org
546 ms
style.css
595 ms
blue.css
425 ms
responsive.css
576 ms
font-awesome.min.css
10 ms
css
25 ms
swipebox.css
237 ms
jquery.min.js
819 ms
jquery.swipebox.min.js
543 ms
jquery.tabs.min.js
456 ms
jquery.jcarousel.min.js
864 ms
tinynav.min.js
682 ms
ultimate-custom.js
762 ms
jquery.tweet.min.js
911 ms
layerslider.css
895 ms
jquery-easing-1.3.js
994 ms
layerslider.kreaturamedia.jquery.js
1205 ms
prettyPhoto.css
1156 ms
jquery.prettyPhoto.js
1270 ms
jquery.validate.min.js
1336 ms
sendmail.js
1148 ms
buttons.js
12 ms
element.js
35 ms
view_webform.js
85 ms
reset.css
638 ms
dc.js
59 ms
embed
90 ms
header-bg.png
572 ms
logo.png
576 ms
social-icons.png
565 ms
button-small-gradient.png
566 ms
button-ico-star.png
568 ms
button-ico-refresh.png
568 ms
button-ico-download.png
575 ms
menu-active-left.png
575 ms
menu-active-right.png
577 ms
home-ico.png
578 ms
banner-shadow.png
578 ms
banner-gradient.png
627 ms
banner-web-otp.jpg
1168 ms
slider_vial.jpg
1199 ms
slider_MOS_web.png
1734 ms
forma2_mos.png
930 ms
12.jpg
1480 ms
fw3.jpg
1377 ms
fw2.jpg
1484 ms
main-bg.jpg
1392 ms
portfolio-three-column6.jpg
1546 ms
readmore-ico.png
1588 ms
Hmasters.jpg
1851 ms
portfolio-three-column8.jpg
1798 ms
splitter.jpg
1710 ms
prevencion-ajeno.jpg
1995 ms
formacion.jpg
2005 ms
blog.jpg
2120 ms
ISO_9001.png
2350 ms
ISO_14001.png
2315 ms
OHSAS_18001.png
2440 ms
footer-gradient.png
2260 ms
footer-shadow.png
2350 ms
address-ico.png
2340 ms
mail-ico.png
2440 ms
translateelement.css
69 ms
main.js
535 ms
phone-ico.png
2511 ms
EFpQQyG9GqCrobXxL-KRMfEr6Hm6RMS0v1dtXsGir4g.ttf
6 ms
s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf
12 ms
__utm.gif
15 ms
embed
497 ms
getAllAppDefault.esi
132 ms
skin.css
1982 ms
footer-logo.png
2118 ms
responsive-nav-bg.png
1998 ms
0992f33945a94632a64d2587cfa6f814embedcompiled_fastui.css
12 ms
0992f33945a94632a64d2587cfa6f814embedcompiled__en.js
23 ms
client.js
50 ms
element_main.js
53 ms
cb=gapi.loaded_0
57 ms
translate_24dp.png
73 ms
l
46 ms
cleardot.gif
44 ms
postmessageRelay
52 ms
getSegment.php
177 ms
checkOAuth.esi
27 ms
te_ctrl3.gif
14 ms
googlelogo_color_68x28dp.png
6 ms
loading.gif
26 ms
3193398744-postmessagerelay.js
43 ms
rpc:shindig_random.js
41 ms
te_bk.gif
19 ms
cb=gapi.loaded_0
3 ms
logo-plus.png
19 ms
googlelogo_color_46x16dp.png
19 ms
proxy.html
46 ms
blank.gif
11 ms
combined_v22.png
13 ms
cb=gapi.loaded_0
4 ms
t.dhj
10 ms
t.dhj
8 ms
events
200 ms
cm
19 ms
s-3271.xgi
7 ms
hbpix
26 ms
5 ms
8 ms
pixel
39 ms
pixel
17 ms
2981
26 ms
52154.gif
6 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
26 ms
buttons.ab966a004186897711de4a5ed256c924.css
19 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
5 ms
st.1188278743c14064d5e8ae56c8ada29c.js
10 ms
facebook_32.png
100 ms
twitter_32.png
17 ms
googleplus_32.png
19 ms
blogger_32.png
21 ms
meneame_32.png
21 ms
linkedin_32.png
18 ms
email_32.png
18 ms
skin.png
317 ms
webform-out.js
19 ms
otp.es accessibility score
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
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.
otp.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
otp.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 doesn't use 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 Otp.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 Otp.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.
otp.es
Open Graph description is not detected on the main page of OTP. 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: