9.9 sec in total
980 ms
6.6 sec
2.4 sec
Visit eema.org now to see the best up-to-date Eema content and also check out these interesting facts you probably never knew about eema.org
Explore the latest in e-security and digital identity technologies, including multi-factor authentication, identity management, encryption, and more.
Visit eema.orgWe analyzed Eema.org page load time and found that the first response time was 980 ms and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
eema.org performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value10.4 s
0/100
25%
Value12.6 s
3/100
10%
Value1,770 ms
10/100
30%
Value0.078
95/100
15%
Value14.3 s
9/100
10%
980 ms
150 ms
303 ms
303 ms
409 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 68% of them (86 requests) were addressed to the original Eema.org, 20% (26 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Eema.org.
Page size can be reduced by 210.5 kB (6%)
3.8 MB
3.6 MB
In fact, the total size of Eema.org main page is 3.8 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. Only a small number of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 141.9 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 28.6 kB, which is 17% 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 141.9 kB or 85% of the original size.
Potential reduce by 68.5 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. Eema images are well optimized though.
Potential reduce by 100 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 60 (60%)
100
40
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eema. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
www.eema.org
980 ms
iframe_api
150 ms
js
303 ms
style.min.css
303 ms
cf7mls.css
409 ms
animate.min.css
419 ms
styles.css
404 ms
ctf-styles.min.css
401 ms
aos.css
404 ms
slick.css
404 ms
bootstrap.min.css
494 ms
bootstrap-multiselect.css
487 ms
style.css
558 ms
responsive.css
488 ms
front.min.css
492 ms
addtoany.min.css
487 ms
mailin-front.css
556 ms
page.js
283 ms
jquery.min.js
625 ms
jquery-migrate.min.js
540 ms
addtoany.min.js
554 ms
jquery.slimscroll.min.js
557 ms
aos.js
615 ms
bootstrap.min.js
615 ms
bootstrap-multiselect.js
693 ms
player.js
696 ms
slick.min.js
698 ms
shorten.js
725 ms
custom-eema.js
734 ms
front.min.js
740 ms
mailin-front.js
739 ms
ctf-scripts.min.js
867 ms
cf7mls.js
1122 ms
index.js
1123 ms
index.js
1124 ms
navigation.js
1124 ms
wpcf7-recaptcha-controls.js
1166 ms
api.js
271 ms
sharethis.js
278 ms
www-widgetapi.js
221 ms
wp-emoji-release.min.js
989 ms
analytics.js
59 ms
collect
21 ms
css2
39 ms
css2
53 ms
eso.e18d3993.js
15 ms
logo.svg
361 ms
search-icon.svg
330 ms
EEMA-NetworkGraphic.jpg
331 ms
btn-arrow-red.svg
358 ms
EEMA-Fosters-Cross-Project-Collaboration-for-EU-Funded-Initiatives-1-Copy-1050x840.png
3432 ms
placeholder-10x5.png
331 ms
spielfeld3-1050x628.png
3429 ms
oid.jpg
2912 ms
EEMA-Annual-2022-29-1050x840.jpg
418 ms
EEMA-Annual-2022-27-1050x840.jpg
553 ms
bg-pattern.svg
360 ms
stock.jpg
435 ms
placeholder-10x4.png
548 ms
btn-arrow-white.svg
2446 ms
stock1.jpg
2913 ms
isse-12.jpg
2913 ms
red-bg.png
3381 ms
ISSE14-Copy-1100x950.jpg
3348 ms
ISSE22-scaled-1400x865-cc.jpg
3398 ms
placeholder-10x6.png
3345 ms
EEMA-Fosters-Cross-Project-Collaboration-for-EU-Funded-Initiatives-1-900x500-cc.png
3685 ms
glass-resized.png
3397 ms
de4a-resized.png
3408 ms
locard-resized.png
3411 ms
futuretrust-resized.png
3410 ms
LIGHTestWhiteLogo.jpg
3411 ms
FutureID-2.jpg
3412 ms
C4E.png
3410 ms
SSEDIC.png
3655 ms
stork-resized.png
3400 ms
bg-pattern-white.svg
3400 ms
EEMA-Documents-PDF2.svg
3416 ms
placeholder-10x9.png
3417 ms
twitter-r.svg
3375 ms
twitter.svg
3375 ms
insta.svg
3375 ms
linkedin.svg
3377 ms
youtube.svg
3395 ms
Vimeo-Insignia-2.svg
3367 ms
twitter.svg
3368 ms
linkedin.svg
3367 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3aPw.ttf
2558 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zAkA.ttf
2723 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i94_AkA.ttf
2539 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rAkA.ttf
2705 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vAkA.ttf
2708 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nAkA.ttf
2705 ms
rnCu-xNNww_2s0amA9M8qtHEafM.ttf
3008 ms
rnCu-xNNww_2s0amA9M8qrXHafM.ttf
2708 ms
rnCt-xNNww_2s0amA9M8kn0.ttf
2990 ms
rnCu-xNNww_2s0amA9M8qonFafM.ttf
3008 ms
rnCu-xNNww_2s0amA9M8qqXCafM.ttf
2990 ms
rnCu-xNNww_2s0amA9M8qsHDafM.ttf
3003 ms
rnCu-xNNww_2s0amA9M8qt3AafM.ttf
3009 ms
rnCs-xNNww_2s0amA9uSsF3G.ttf
3002 ms
rnCs-xNNww_2s0amA9v2s13G.ttf
3001 ms
rnCr-xNNww_2s0amA-M-.ttf
3007 ms
rnCs-xNNww_2s0amA9vKsV3G.ttf
3006 ms
rnCs-xNNww_2s0amA9vmtl3G.ttf
3037 ms
rnCs-xNNww_2s0amA9uCt13G.ttf
3039 ms
rnCs-xNNww_2s0amA9uetF3G.ttf
3039 ms
plus.svg
3347 ms
submit-arrow.svg
3295 ms
recaptcha__en.js
2905 ms
1f7e2.svg
2731 ms
icons.30.svg.js
2077 ms
sm.23.html
2241 ms
search-icon.svg
2592 ms
twitter.svg
2596 ms
insta.svg
2593 ms
6xK1dSBYKcSV-LCoeQqfX1RYOo3qPa7g.ttf
570 ms
6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZMkhdr.ttf
560 ms
6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZYokRdr.ttf
560 ms
6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZY4lBdr.ttf
565 ms
6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZclRdr.ttf
563 ms
6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZklxdr.ttf
564 ms
linkedin.svg
921 ms
youtube.svg
1001 ms
Vimeo-Insignia-2.svg
1002 ms
arrow-white-right.svg
1004 ms
arrow-red-right.svg
575 ms
eema.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
Image elements do not have [alt] attributes
Links do not have a discernible name
eema.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
Browser errors were logged to the console
eema.org 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 Eema.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 Eema.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.
eema.org
Open Graph data is detected on the main page of Eema. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: