8.7 sec in total
347 ms
8.3 sec
150 ms
Visit ehu.es now to see the best up-to-date EHU content for Spain and also check out these interesting facts you probably never knew about ehu.es
Visit ehu.esWe analyzed Ehu.es page load time and found that the first response time was 347 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ehu.es performance score
name
value
score
weighting
Value7.6 s
1/100
10%
Value12.0 s
0/100
25%
Value9.4 s
12/100
10%
Value250 ms
84/100
30%
Value0.088
93/100
15%
Value19.6 s
2/100
10%
347 ms
343 ms
110 ms
1223 ms
861 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Ehu.es, 97% (36 requests) were made to Ehu.eus. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Ehu.eus.
Page size can be reduced by 905.2 kB (61%)
1.5 MB
572.3 kB
In fact, the total size of Ehu.es main page is 1.5 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. 25% of websites need less resources to load. Javascripts take 759.8 kB which makes up the majority of the site volume.
Potential reduce by 27.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. 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 27.1 kB or 80% of the original size.
Potential reduce by 29.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. Obviously, EHU needs image optimization as it can save up to 29.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 519.6 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 519.6 kB or 68% of the original size.
Potential reduce by 328.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. Ehu.es needs all CSS files to be minified and compressed as it can save up to 328.6 kB or 82% of the original size.
Number of requests can be reduced by 13 (54%)
24
11
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EHU. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
ehu.es
347 ms
www.ehu.eus
343 ms
110 ms
en-home
1223 ms
css.jsp
861 ms
main.jsp
334 ms
main.jsp
458 ms
barebone.jsp
1029 ms
main.css
471 ms
main.js
195 ms
fondo_zn_menus.png
115 ms
ext_fondo_cabecera_gris.png
118 ms
logoehu.png
216 ms
fondo_elementos_form.png
111 ms
input_lupa.png
113 ms
ruta.png
119 ms
bullet_submenu_principal.png
222 ms
image_gallery
231 ms
fondo_criterios_orden.png
222 ms
layout_icon
353 ms
layout_icon
533 ms
layout_icon
333 ms
layout_icon
337 ms
new.png
330 ms
ico_calendario.png
341 ms
spacer.png
440 ms
_sprite.png
865 ms
image_gallery
461 ms
image_gallery
542 ms
image_gallery
478 ms
image_gallery
745 ms
pie_logo.png
571 ms
976 ms
piwik.js
742 ms
ehusans-regular-webfont.woff
633 ms
301 ms
368 ms
ehu.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
ehu.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ehu.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ehu.es can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ehu.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.
ehu.es
Open Graph description is not detected on the main page of EHU. 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: