6.9 sec in total
285 ms
6.1 sec
505 ms
Click here to check amazing EFNIL content. Otherwise, check out these important facts you probably never knew about efnil.org
Read more Read More Read More Read More Read More edit post Read More edit post Read More The Translation Centre for the Bodies of the European Union The…
Visit efnil.orgWe analyzed Efnil.org page load time and found that the first response time was 285 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
efnil.org performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value8.2 s
2/100
25%
Value9.1 s
14/100
10%
Value270 ms
82/100
30%
Value0
100/100
15%
Value8.0 s
43/100
10%
285 ms
3106 ms
207 ms
27 ms
397 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 97% of them (139 requests) were addressed to the original Efnil.org, 2% (3 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Efnil.org.
Page size can be reduced by 508.2 kB (41%)
1.3 MB
742.3 kB
In fact, the total size of Efnil.org main page is 1.3 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. 50% of websites need less resources to load. CSS take 526.9 kB which makes up the majority of the site volume.
Potential reduce by 218.3 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 218.3 kB or 88% of the original size.
Potential reduce by 123 B
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. EFNIL images are well optimized though.
Potential reduce by 289.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. Efnil.org needs all CSS files to be minified and compressed as it can save up to 289.7 kB or 55% of the original size.
Number of requests can be reduced by 114 (83%)
137
23
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EFNIL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 41 to 1 for CSS and as a result speed up the page load time.
efnil.org
285 ms
efnil.org
3106 ms
main.min.css
207 ms
css
27 ms
main.css
397 ms
style.min.css
410 ms
dashicons.min.css
414 ms
styles.css
319 ms
events-manager.min.css
504 ms
style.min.css
314 ms
style.min.css
413 ms
frontend-lite.min.css
420 ms
general.min.css
495 ms
eael-25.css
512 ms
elementor-icons.min.css
519 ms
swiper.min.css
519 ms
post-247.css
520 ms
all.min.css
595 ms
v4-shims.min.css
602 ms
post-25.css
609 ms
style.css
608 ms
um-crop.css
610 ms
um-modal.css
617 ms
jquery-ui.min.css
695 ms
tipsy.min.css
701 ms
um-raty.min.css
705 ms
fonticons-ii.min.css
620 ms
fonticons-fa.min.css
623 ms
select2.min.css
628 ms
um-styles.css
706 ms
um-profile.css
713 ms
um-account.css
724 ms
um-misc.css
718 ms
um-fileupload.css
719 ms
default.css
725 ms
default.date.css
803 ms
default.time.css
811 ms
simplebar.css
815 ms
css
19 ms
um-responsive.css
814 ms
um-old-default.css
709 ms
fontawesome.min.css
604 ms
solid.min.css
677 ms
language-cookie.js
597 ms
jquery.min.js
603 ms
jquery-migrate.min.js
598 ms
core.min.js
604 ms
mouse.min.js
600 ms
sortable.min.js
590 ms
datepicker.min.js
587 ms
resizable.min.js
591 ms
draggable.min.js
595 ms
controlgroup.min.js
595 ms
checkboxradio.min.js
596 ms
button.min.js
596 ms
dialog.min.js
593 ms
events-manager.min.js
707 ms
v4-shims.min.js
604 ms
um-gdpr.min.js
599 ms
frontend.min.js
597 ms
separate-accordion.js
597 ms
group-accordion.js
595 ms
general.min.js
605 ms
eael-25.js
726 ms
webpack.runtime.min.js
722 ms
frontend-modules.min.js
643 ms
waypoints.min.js
637 ms
frontend.min.js
634 ms
sticky-element.js
632 ms
underscore.min.js
629 ms
wp-util.min.js
690 ms
um-crop.min.js
612 ms
um-modal.min.js
607 ms
um-jquery-form.min.js
610 ms
um-fileupload.js
607 ms
picker.js
607 ms
picker.date.js
679 ms
picker.time.js
596 ms
imagesloaded.min.js
597 ms
masonry.min.js
607 ms
jquery.masonry.min.js
607 ms
simplebar.min.js
595 ms
um-functions.min.js
670 ms
um-responsive.min.js
605 ms
wp-polyfill-inert.min.js
603 ms
regenerator-runtime.min.js
607 ms
wp-polyfill.min.js
611 ms
hooks.min.js
621 ms
um-conditional.min.js
682 ms
select2.full.min.js
611 ms
en.js
612 ms
tipsy.min.js
610 ms
i18n.min.js
604 ms
um-raty.min.js
610 ms
um-scripts.min.js
604 ms
um-profile.min.js
606 ms
um-account.min.js
606 ms
post-pagination.js
597 ms
efnil-logo-v2-240x113.png
503 ms
en.svg
502 ms
bg.svg
556 ms
cs.svg
563 ms
da.svg
565 ms
de.svg
570 ms
el.svg
577 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
20 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
34 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
35 ms
fa-solid-900.woff
777 ms
fa-regular-400.woff
589 ms
et.svg
602 ms
fr.svg
596 ms
ga.svg
605 ms
hr.svg
675 ms
is.svg
602 ms
it.svg
606 ms
georgia-flag.svg
614 ms
lv.svg
678 ms
lt.svg
683 ms
mt.svg
681 ms
hu.svg
618 ms
nl.svg
616 ms
no.svg
688 ms
pl.svg
684 ms
ro.svg
672 ms
sk.svg
679 ms
sl.svg
619 ms
sr.svg
681 ms
fi.svg
685 ms
sv.svg
688 ms
efnil-home-bg-1-768x512.jpg
695 ms
Mobility-Scheme-unsplash-768x512.jpg
693 ms
project-elm-768x512.jpg
791 ms
project-elips-768x512.jpg
790 ms
project-master-768x512.jpg
693 ms
Ljubljana-group-photo-2024-300x163.jpg
676 ms
master-thesis-results-2023-300x221.jpg
678 ms
events-300x169.jpg
758 ms
20th-300x200.jpg
718 ms
cdt-europa.svg
715 ms
logo-ec-en.svg
782 ms
ECSPM-logo-2020.png
781 ms
european-center-of-modern-languages-300x102.jpg
780 ms
rgb_ele__logo-colour.svg
705 ms
efnil.org accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
efnil.org 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
efnil.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Efnil.org 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 Efnil.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.
efnil.org
Open Graph description is not detected on the main page of EFNIL. 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: