5.8 sec in total
283 ms
5.2 sec
331 ms
Click here to check amazing AEK content for Spain. Otherwise, check out these important facts you probably never knew about aek.org
Visit aek.orgWe analyzed Aek.org page load time and found that the first response time was 283 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.
aek.org performance score
name
value
score
weighting
Value12.6 s
0/100
10%
Value13.0 s
0/100
25%
Value19.1 s
0/100
10%
Value1,130 ms
23/100
30%
Value0.035
100/100
15%
Value19.2 s
2/100
10%
283 ms
286 ms
1976 ms
205 ms
217 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Aek.org, 70% (76 requests) were made to Aek.eus and 10% (11 requests) were made to W.sharethis.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Aek.eus.
Page size can be reduced by 821.2 kB (54%)
1.5 MB
692.2 kB
In fact, the total size of Aek.org 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. 40% of websites need less resources to load. Javascripts take 787.6 kB which makes up the majority of the site volume.
Potential reduce by 43.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 6.6 kB, which is 12% 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 43.1 kB or 80% of the original size.
Potential reduce by 36.3 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. AEK images are well optimized though.
Potential reduce by 566.1 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 566.1 kB or 72% of the original size.
Potential reduce by 175.7 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. Aek.org needs all CSS files to be minified and compressed as it can save up to 175.7 kB or 82% of the original size.
Number of requests can be reduced by 55 (54%)
102
47
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AEK. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
aek.org
283 ms
www.aek.org
286 ms
1976 ms
style.css
205 ms
modal.css
217 ms
attachments_hide.css
218 ms
attachments_list.css
219 ms
jcemediabox.css
224 ms
style.css
225 ms
bootstrap.min.css
316 ms
bootstrap-responsive.min.css
333 ms
bootstrap-extended.css
326 ms
finder.css
335 ms
featcats.css
335 ms
style.css
336 ms
mootools-core.js
428 ms
core.js
420 ms
jquery.min.js
537 ms
jquery-noconflict.js
421 ms
jquery-migrate.min.js
451 ms
punycode.js
452 ms
validate.js
519 ms
mootools-more.js
749 ms
modal.js
530 ms
attachments_refresh.js
557 ms
caption.js
561 ms
bootstrap.min.js
622 ms
jcemediabox.js
641 ms
template.js
648 ms
jquery.autocomplete.min.js
656 ms
featcats.js
669 ms
css
22 ms
template.css
722 ms
style.css
746 ms
buttons.js
7 ms
logo_h.png
145 ms
eu.gif
146 ms
es.gif
144 ms
fr.gif
143 ms
postit.png
145 ms
glyphicons-halflings.png
145 ms
santutxukoa.jpg
325 ms
Deustuko_Mintzodromoa_Martxoak_17.jpg
845 ms
b_90_90_16777215_1542_laudiokogalakr.jpg
214 ms
b_90_90_16777215_1615_405azala.jpg
230 ms
b_90_90_16777215_1606_OSASUNA_PATRI.jpg
225 ms
b_90_90_16777215_1619_Guztiok-izan-beharko-ginateke-feminista_Azala-158x300.png
239 ms
pixel.png
316 ms
fb.png
327 ms
twitter.png
339 ms
youtube.png
354 ms
flickr.png
425 ms
rss.png
426 ms
Google_Play_logo.png
431 ms
App_Store_Badge.png
444 ms
b_90_90_16777215_1277_forukobarnetegia.jpg
468 ms
b_90_90_16777215_1588_euskarairakasleikast.JPG
535 ms
tresnak.jpg
535 ms
bannerra_300x300.Ordua_aldatuta.gif
672 ms
foot.png
685 ms
jc_blog.gif
555 ms
gk5FxslNkTTHtojXrkp-xJhsE6jcpsD2oq89kgohWx0.ttf
109 ms
popup.html
587 ms
tooltip.html
604 ms
getAllAppDefault.esi
149 ms
ahize.png
559 ms
aizu.png
637 ms
praktikatu.png
637 ms
kulturgintza.png
644 ms
bilatu.png
664 ms
glyphicons-halflings-white.png
669 ms
ikastaroak.png
738 ms
estekak.png
737 ms
getSegment.php
11 ms
checkOAuth.esi
4 ms
t.dhj
68 ms
t.dhj
42 ms
cm
27 ms
s-3271.xgi
17 ms
8 ms
hbpix
98 ms
19 ms
xrefid.xgi
6 ms
pixel
21 ms
pixel
15 ms
2981
28 ms
corner-tl.png
211 ms
corner-tr.png
235 ms
corner-bl.png
241 ms
corner-br.png
270 ms
A3_barnetegiTxikiakweb.jpg
542 ms
loader.gif
321 ms
close.png
106 ms
prev.png
127 ms
next.png
123 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
26 ms
buttons.ab966a004186897711de4a5ed256c924.css
16 ms
getCount2.php
46 ms
getCount2.php
47 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
7 ms
st.1188278743c14064d5e8ae56c8ada29c.js
12 ms
email_counter.png
21 ms
bubble_arrow.png
22 ms
facebook_counter.png
23 ms
Facebook_bubble_arrow.png
22 ms
twitter_counter.png
23 ms
Twitter_bubble_arrow.png
25 ms
googleplus_16.png
22 ms
aek.org 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
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.
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.
aek.org 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
aek.org 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 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 Aek.org 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 Aek.org 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.
aek.org
Open Graph description is not detected on the main page of AEK. 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: