4.9 sec in total
332 ms
4.2 sec
338 ms
Click here to check amazing ELA content for Spain. Otherwise, check out these important facts you probably never knew about ela.eus
Visit ela.eusWe analyzed Ela.eus page load time and found that the first response time was 332 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
ela.eus performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value8.2 s
2/100
25%
Value8.4 s
19/100
10%
Value410 ms
67/100
30%
Value0.224
56/100
15%
Value10.9 s
21/100
10%
332 ms
895 ms
113 ms
338 ms
238 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 92% of them (54 requests) were addressed to the original Ela.eus, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Statcounter.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Mrafundazioa.eus.
Page size can be reduced by 119.1 kB (10%)
1.2 MB
1.1 MB
In fact, the total size of Ela.eus main page is 1.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. 30% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 36.8 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 7.0 kB, which is 15% 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 36.8 kB or 79% of the original size.
Potential reduce by 66.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. ELA images are well optimized though.
Potential reduce by 15.8 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 15.8 kB or 54% of the original size.
Number of requests can be reduced by 11 (20%)
56
45
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ELA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
ela.eus
332 ms
eu
895 ms
reset-cachekey-9ddf7306ff8eec756490d3ba3feeeb77.css
113 ms
base-cachekey-6722ceb494007fd1f1ef86928c7399b2.css
338 ms
ela.theme-cachekey-864f5c4d0b4d5ce7f76f21bba6369e50.css
238 ms
resourcecollective.z3cform.datagridfielddatagridfield-cachekey-dc5af347e4debd3e8e06d420c76a205e.css
251 ms
ploneCustom-cachekey-d78b274b785e36ae50d05300c7c8d3f2.css
254 ms
resourceplone.app.jquery-cachekey-38926a96b0923c131a1f50bdec8a9b0a.js
560 ms
resourcedropdown-menu-cachekey-6d94780a6112916b27c2dd1c7209ce5c.js
267 ms
collective.js.jqueryui.custom.min-cachekey-82504e75f803239e8de3063933066b73.js
585 ms
jsmediaquery.js
369 ms
search.js
375 ms
resourcecollective.z3cform.datagridfielddatagridfield-cachekey-5abcc202e6b8101ec58851d4bb112c9b.js
398 ms
counter_xhtml.js
10 ms
urchin.js
9 ms
top.jpg
120 ms
image_mini
2050 ms
searchbutton.png
129 ms
logo.png
157 ms
mainmenu.gif
148 ms
logo_manurobles.gif
153 ms
image
1241 ms
image_mini
225 ms
image_mini
247 ms
image_mini
268 ms
image_mini
294 ms
image_mini
295 ms
image_mini
335 ms
image_mini
365 ms
image_mini
498 ms
image_mini
427 ms
image
436 ms
image
446 ms
pestaina.gif
482 ms
image
804 ms
a9b1422d-4f6e-4352-8e71-db25111d51d0.png
575 ms
blogtitlebottom.gif
564 ms
fca6d7a3-8240-48fd-a675-7ee2b047410a.png
597 ms
59a91bea-2c77-4a3b-90c0-34e94a768918.png
616 ms
a7c22800-ce4f-42c5-bb92-0566ecb43de6.png
673 ms
e6ea609f-d4b3-418c-9045-178995c7641f.png
702 ms
image
715 ms
inkesta-osakidetza
847 ms
epe-correos-banner
883 ms
2455e1bb-7740-448d-a9e8-964b52bc1376.jpeg
838 ms
a0c435e0-4ef8-4591-b30b-927ac8f7c4b4.jpeg
836 ms
image
930 ms
kartela-ilp-kanpaina
1500 ms
f7ea22db-7cc1-4f73-a565-08461eebafda.jpeg
967 ms
818b7622-4014-4425-b510-ca5298534a68.jpeg
966 ms
marxoak-8-2016
1485 ms
image
1062 ms
t.php
53 ms
__utm.gif
15 ms
Variable.woff
984 ms
image
1101 ms
8e65c938-5366-4b78-bb29-7cae32c04916.png
1168 ms
footer.gif
1064 ms
spinner.gif
1181 ms
ela.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
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
ela.eus 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
ela.eus 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
EU
EU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ela.eus can be misinterpreted by Google and other search engines. Our service has detected that Basque is used on the page, and it matches the claimed language. Our system also found out that Ela.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.
ela.eus
Open Graph description is not detected on the main page of ELA. 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: