Report Summary

  • 20

    Performance

    Renders faster than
    40% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    65% of websites

  • 93

    SEO

    Google-friendlier than
    88% of websites

ef.no

EF Education First - Norge

Page Load Speed

3.1 sec in total

First Response

608 ms

Resources Loaded

2.3 sec

Page Rendered

236 ms

ef.no screenshot

About Website

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

Key Findings

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.

Performance Metrics

ef.no performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value4,030 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

Network Requests Diagram

www.ef.no

608 ms

fonts.css

39 ms

central-header.min.css

41 ms

centralefcom-global-footer-naked.min.css

38 ms

main.css

48 ms

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 Optimization Overview & Recommendations

Page size can be reduced by 913.4 kB (49%)

Content Size

1.9 MB

After Optimization

939.4 kB

In fact, the total size of Ef.no main page is 1.9 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 785.3 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 107.0 kB

  • Original 119.8 kB
  • After minification 69.7 kB
  • After compression 12.8 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.

Image Optimization

-2%

Potential reduce by 14.0 kB

  • Original 626.9 kB
  • After minification 612.9 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.

JavaScript Optimization

-69%

Potential reduce by 540.9 kB

  • Original 785.3 kB
  • After minification 767.2 kB
  • After compression 244.4 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 540.9 kB or 69% of the original size.

CSS Optimization

-78%

Potential reduce by 251.5 kB

  • Original 320.8 kB
  • After minification 319.1 kB
  • After compression 69.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. 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.

Requests Breakdown

Number of requests can be reduced by 28 (62%)

Requests Now

45

After Optimization

17

The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

ef.no accessibility score

94

Accessibility Issues

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

High

[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.

Impact

Issue

High

Links do not have a discernible name

Best Practices

ef.no best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ef.no SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    NO

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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.

Social Sharing Optimization

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: