8.6 sec in total
498 ms
7.9 sec
175 ms
Click here to check amazing EHU content for Spain. Otherwise, check out these important facts you probably never knew about ehu.eus
Visit ehu.eusWe analyzed Ehu.eus page load time and found that the first response time was 498 ms and then it took 8.1 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.eus performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value8.6 s
1/100
25%
Value8.0 s
21/100
10%
Value150 ms
94/100
30%
Value0.082
94/100
15%
Value30.8 s
0/100
10%
498 ms
125 ms
577 ms
803 ms
243 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that all of those requests were addressed to Ehu.eus and no external sources were called. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Ehu.eus.
Page size can be reduced by 442.8 kB (68%)
655.6 kB
212.8 kB
In fact, the total size of Ehu.eus main page is 655.6 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. 25% of websites need less resources to load. Javascripts take 363.4 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 6.6 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 6.6 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 244.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 244.9 kB or 67% of the original size.
Potential reduce by 164.3 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.eus needs all CSS files to be minified and compressed as it can save up to 164.3 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.eus
498 ms
125 ms
en-home
577 ms
css.jsp
803 ms
main.jsp
243 ms
main.jsp
351 ms
barebone.jsp
924 ms
main.css
698 ms
main.js
126 ms
fondo_zn_menus.png
124 ms
ext_fondo_cabecera_gris.png
118 ms
logoehu.png
118 ms
fondo_elementos_form.png
120 ms
input_lupa.png
119 ms
ruta.png
119 ms
bullet_submenu_principal.png
233 ms
image_gallery
321 ms
fondo_criterios_orden.png
233 ms
layout_icon
469 ms
layout_icon
241 ms
layout_icon
257 ms
layout_icon
434 ms
new.png
347 ms
ico_calendario.png
357 ms
spacer.png
371 ms
_sprite.png
660 ms
image_gallery
626 ms
image_gallery
485 ms
image_gallery
500 ms
image_gallery
637 ms
pie_logo.png
581 ms
2112 ms
piwik.js
1191 ms
ehusans-regular-webfont.woff
778 ms
121 ms
1277 ms
ehu.eus 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.eus 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.eus 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.eus 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.eus 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.eus
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: