Report Summary

  • 22

    Performance

    Renders faster than
    42% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    86% of websites

  • 91

    SEO

    Google-friendlier than
    76% of websites

elisa.net

Elisa - Suomalaiset tietoliikenne- ja viihtymisen palvelut

Page Load Speed

3.9 sec in total

First Response

531 ms

Resources Loaded

3.3 sec

Page Rendered

74 ms

elisa.net screenshot

About Website

Click here to check amazing Elisa content for Finland. Otherwise, check out these important facts you probably never knew about elisa.net

Elisalta saat edulliset Saunalahti-liittymät, puhelimet sekä Elisa Viihteen ja videovuokraamon. Sähköpostit voit lukea Elisan Webmail-palvelusta.

Visit elisa.net

Key Findings

We analyzed Elisa.net page load time and found that the first response time was 531 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

elisa.net performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

www.elisa.net

531 ms

wp-emoji-release.min.js

519 ms

front.css

210 ms

settings.css

320 ms

fonts.css

629 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 69% of them (42 requests) were addressed to the original Elisa.net, 10% (6 requests) were made to Google.com and 3% (2 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Elisa.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (32%)

Content Size

3.2 MB

After Optimization

2.2 MB

In fact, the total size of Elisa.net main page is 3.2 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. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-9%

Potential reduce by 10 B

  • Original 108 B
  • After minification 108 B
  • After compression 98 B

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. This web page is already compressed.

Image Optimization

-4%

Potential reduce by 78.3 kB

  • Original 1.8 MB
  • After minification 1.7 MB

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. Elisa images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 808.1 kB

  • Original 1.2 MB
  • After minification 1.1 MB
  • After compression 349.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 808.1 kB or 70% of the original size.

CSS Optimization

-61%

Potential reduce by 153.7 kB

  • Original 250.8 kB
  • After minification 213.6 kB
  • After compression 97.1 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. Elisa.net needs all CSS files to be minified and compressed as it can save up to 153.7 kB or 61% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (54%)

Requests Now

57

After Optimization

26

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

Accessibility Review

elisa.net accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best Practices

elisa.net best practices score

92

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

SEO Factors

elisa.net SEO score

91

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FI

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elisa.net can be misinterpreted by Google and other search engines. Our service has detected that Finnish 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 Elisa.net main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Elisa. 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: