1.6 sec in total
180 ms
1.2 sec
190 ms
Click here to check amazing Efta content for Belgium. Otherwise, check out these important facts you probably never knew about efta.int
Visit efta.intWe analyzed Efta.int page load time and found that the first response time was 180 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
efta.int performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value10.2 s
0/100
25%
Value6.3 s
42/100
10%
Value300 ms
79/100
30%
Value1.191
1/100
15%
Value12.7 s
13/100
10%
180 ms
185 ms
83 ms
155 ms
171 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 71% of them (32 requests) were addressed to the original Efta.int, 18% (8 requests) were made to Google.com and 7% (3 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (549 ms) belongs to the original domain Efta.int.
Page size can be reduced by 308.6 kB (30%)
1.0 MB
707.8 kB
In fact, the total size of Efta.int main page is 1.0 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. 45% of websites need less resources to load. Images take 599.4 kB which makes up the majority of the site volume.
Potential reduce by 39.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 39.3 kB or 76% of the original size.
Potential reduce by 38.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. Efta images are well optimized though.
Potential reduce by 121.5 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 121.5 kB or 53% of the original size.
Potential reduce by 109.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. Efta.int needs all CSS files to be minified and compressed as it can save up to 109.3 kB or 81% of the original size.
Number of requests can be reduced by 15 (37%)
41
26
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Efta. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
efta.int
180 ms
www.efta.int
185 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
83 ms
css__Y7RzWn5bacy54HCmezXs8SPaMSbX2p3claszqCJA78.css
155 ms
css_MnXiytJtb186Ydycnpwpw34cuUsHaKc80ey5LiQXhSY.css
171 ms
css_k-q5TanFWvDKP_KgwGxC8LqM6u2EzWrEHBJQX1knZck.css
163 ms
css_uk3hth21Fqkoq_34gZPeUHv-EnaOFoGMsGg0OG-M4RQ.css
175 ms
js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js
242 ms
js_puaYKIZExM0PgipaghSHNvp-k3ZMb4bKSo1ABt5zd9A.js
174 ms
js_p1Crw9-UWziALd8CRaGwmAmY2Qh-fhSOVhRqucOWOL0.js
229 ms
js_F4TfbSVCFukbcDTlZsVyyqUZ-FiVABOsG1Fk9HTyOac.js
261 ms
js_paiTaEsc1HNeBS2rkLc1NrprKrFnApv70kuY8awAaTI.js
266 ms
analytics.js
25 ms
logo.png
83 ms
pic-header3.jpg
164 ms
2016-02-26-Tiblisi-600-1.jpg
228 ms
2016-02-23-PC-Processed-Malmstrom-400-1.jpg
244 ms
Work-Life-Balance.jpg
161 ms
2016-02-18-andrea-scheller-600.jpg
244 ms
trainees-bxl-2015-2016-660pxl.jpg
352 ms
this-is-efta-2015.jpg
351 ms
annual_report_2014.JPG
353 ms
bulletin-2015-cover-256pxl.jpg
388 ms
efta-at-a-glance-2015.jpg
352 ms
efta-bulletin-september-2014-cover.jpg
406 ms
EFTA-Bulletin-2013.jpg
481 ms
sidebar-logo1.png
403 ms
sidebar-logo2.png
406 ms
sidebar-logo3.png
411 ms
cse.js
61 ms
gradient.png
438 ms
gradient2.png
469 ms
buttons.png
470 ms
fontawesome-webfont.woff
549 ms
collect
14 ms
cse.js
95 ms
jsapi
82 ms
default+en.css
8 ms
default.css
47 ms
default+en.I.js
14 ms
default.css
48 ms
async-ads.js
63 ms
google_custom_search_watermark.gif
46 ms
small-logo.png
38 ms
nav_logo114.png
8 ms
efta.int 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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
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.
efta.int 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
General
Impact
Issue
Detected JavaScript libraries
efta.int 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
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 Efta.int 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 Efta.int 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.
efta.int
Open Graph description is not detected on the main page of Efta. 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: