3.1 sec in total
Visit ef.no now to see the best up-to-date EF content for Norway and also check out these interesting facts you probably never knew about ef.no
EF tilbyr språkreiser, språkkurs, utveksling og studier i utlandet. Vi er verdens største private utdanningsselskap, og har mer enn 50 års erfaring.Visit ef.no
We analyzed Ef.no page load time and found that the first response time was 608 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
ef.no performance score
Our browser made a total of 49 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original Ef.no, 31% (15 requests) were made to Media.ef.com and 18% (9 requests) were made to Media2.ef.com. The less responsive or slowest element that took the longest time to load (608 ms) belongs to the original domain Ef.no.
Page size can be reduced by 913.4 kB (49%)
Potential reduce by 107.0 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 50.1 kB, which is 42% 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 107.0 kB or 89% of the original size.
Potential reduce by 14.0 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. EF images are well optimized though.
Potential reduce by 540.9 kB
Potential reduce by 251.5 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. Ef.no needs all CSS files to be minified and compressed as it can save up to 251.5 kB or 78% of the original size.
Number of requests can be reduced by 28 (62%)
ef.no accessibility score
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.
[aria-hidden="true"] elements contain focusable descendents
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.
Links do not have a discernible name
ef.no best practices score
Trust and Safety
Does not use HTTPS
Ensure CSP is effective against XSS attacks
Browser errors were logged to the console
Page has valid source maps
ef.no SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
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/).
Document uses legible font sizes
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ef.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ef.no 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.
Open Graph data is detected on the main page of EF. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: