2.9 sec in total
251 ms
2.3 sec
289 ms
Visit oei.es now to see the best up-to-date OEI content for India and also check out these interesting facts you probably never knew about oei.es
La Secretaría General de la OEI se funda en 1949. Su sede se encuentra en Madrid.
Visit oei.esWe analyzed Oei.es page load time and found that the first response time was 251 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
oei.es performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value6.1 s
12/100
25%
Value6.7 s
36/100
10%
Value750 ms
39/100
30%
Value0
100/100
15%
Value8.4 s
39/100
10%
251 ms
508 ms
717 ms
8 ms
39 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Oei.es, 88% (28 requests) were made to Oei.int and 3% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (717 ms) relates to the external source Oei.int.
Page size can be reduced by 94.5 kB (4%)
2.2 MB
2.1 MB
In fact, the total size of Oei.es main page is 2.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 50.1 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 11.3 kB, which is 19% 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 50.1 kB or 84% of the original size.
Potential reduce by 44.4 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. OEI images are well optimized though.
Potential reduce by 6 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 0 B
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. Oei.es has all CSS files already compressed.
We found no issues to fix!
16
16
The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OEI. According to our analytics all requests are already optimized.
oei.es
251 ms
www.oei.es
508 ms
secretaria-general
717 ms
application-9cb803556e3d661b7fe02362b023797b46e9d34fd7e674be9dd29ac02ee1e42f.css
8 ms
application-e666357a2075a306be35.js
39 ms
application-b0d58f27a7d21e36453ed938838368cbd4de3a08548252c509611ad5ca6b313f.js
36 ms
embed
232 ms
Logo-OEI.png
54 ms
oei-unesco%20(1).jpg
58 ms
53686997714_b3caf2c1c3_k.jpg
52 ms
53673658331_d5764aab2f_k.jpg
57 ms
icon-select.png
52 ms
Captura%20de%20pantalla%202024-04-03%20175832%20(1).png
63 ms
UsoEditorial_RahulRamachandram.jpg
64 ms
oei-unesco%20(1).jpg
68 ms
PremioDDHH_redes_ES_X.png
65 ms
53686997714_b3caf2c1c3_k.jpg
80 ms
Mariano%20Jabonero-7.jpg
80 ms
fa-solid-900-cea79b345caf49d6223098b8a2b04d70273e8d7c6b9e3d03cf7f7a267793e9aa.ttf
76 ms
fa-regular-400-7d81a1a7cc07e1ab196e40496d3f4359e9759f79d8ec883a46675ee69912950b.ttf
652 ms
fa-brands-400-003f11541856a649a6c8235c6266c8936224c5d609e51442da24dc5556d14fbf.ttf
44 ms
53686997714_b3caf2c1c3_k.jpg
43 ms
Logo-OEI.png
58 ms
53673658331_d5764aab2f_k.jpg
54 ms
oei-unesco%20(1).jpg
54 ms
Captura%20de%20pantalla%202024-04-03%20175832%20(1).png
78 ms
UsoEditorial_RahulRamachandram.jpg
80 ms
PremioDDHH_redes_ES_X.png
77 ms
oei-unesco%20(1).jpg
75 ms
Mariano%20Jabonero-7.jpg
64 ms
53686997714_b3caf2c1c3_k.jpg
65 ms
js
55 ms
oei.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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
oei.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
Page has valid source maps
oei.es SEO score
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 Oei.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 Oei.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.
oei.es
Open Graph data is detected on the main page of OEI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: