Tools & Wizards About Us
telenor.se screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

telenor.se

Page Load Speed

2.8 sec in total

First Response

1 sec

Resources Loaded

1.6 sec

Page Rendered

184 ms

telenor.se screenshot

About Website

Welcome to telenor.se homepage info - get ready to check Telenor best content for Sweden right away, or after learning these important things about telenor.se

Se alla aktuella erbjudanden på mobiler, abonnemang, bredband och Tv | Telenor

Visit telenor.se

Key Findings

We analyzed Telenor.se page load time and found that the first response time was 1 sec and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

telenor.se performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value980 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.412

24/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

www.telenor.se

1026 ms

launch-ENc27e41b1c4ec4914ac423cdec30d2d47.min.js

25 ms

commons~articleSpecification~fixed~main~mobile~mobilePurchaseFlow~myTelenor~shared~bc93cd35.9a2aad3802cc37c0b39e.css

122 ms

commons~main~myTelenor~bc93cd35.c0df1993fbe8191cdb61.css

124 ms

main.f299157bd8bee60c439b.css

129 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Telenor.se, 84% (21 requests) were made to Static.telenor.se and 4% (1 request) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Telenor.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 493.0 kB (42%)

Content Size

1.2 MB

After Optimization

671.6 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Telenor.se main page is 1.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. 45% of websites need less resources to load. Javascripts take 909.5 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 125.5 kB

  • Original 141.1 kB
  • After minification 131.0 kB
  • After compression 15.5 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 125.5 kB or 89% of the original size.

JavaScript Optimization

-40%

Potential reduce by 367.0 kB

  • Original 909.5 kB
  • After minification 909.5 kB
  • After compression 542.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 367.0 kB or 40% of the original size.

CSS Optimization

-0%

Potential reduce by 427 B

  • Original 114.1 kB
  • After minification 114.1 kB
  • After compression 113.6 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. Telenor.se has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 19 (90%)

Requests Now

21

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

www.telenor.se

www.telenor.se

1026 ms

launch-ENc27e41b1c4ec4914ac423cdec30d2d47.min.js

launch-ENc27e41b1c4ec4914ac423cdec30d2d47.min.js

25 ms

commons~articleSpecification~fixed~main~mobile~mobilePurchaseFlow~myTelenor~shared~bc93cd35.9a2aad3802cc37c0b39e.css

commons~articleSpecification~fixed~main~mobile~mobilePurchaseFlow~myTelenor~shared~bc93cd35.9a2aad3802cc37c0b39e.css

122 ms

commons~main~myTelenor~bc93cd35.c0df1993fbe8191cdb61.css

commons~main~myTelenor~bc93cd35.c0df1993fbe8191cdb61.css

124 ms

main.f299157bd8bee60c439b.css

main.f299157bd8bee60c439b.css

129 ms

commons~fixed~mobile~mobilePurchaseFlow~shared~bc93cd35.26697379d344bd940275.css

commons~fixed~mobile~mobilePurchaseFlow~shared~bc93cd35.26697379d344bd940275.css

167 ms

shared.c2432d6476b362c0b055.css

shared.c2432d6476b362c0b055.css

173 ms

fixed.824ce3835fd57a83f43b.css

fixed.824ce3835fd57a83f43b.css

171 ms

mobile.4873604f60b7b485efb2.css

mobile.4873604f60b7b485efb2.css

168 ms

mobilePurchaseFlow.089ff72f769414901794.css

mobilePurchaseFlow.089ff72f769414901794.css

167 ms

myTelenor.3b141c0ef3d307396cd2.css

myTelenor.3b141c0ef3d307396cd2.css

173 ms

find.js

find.js

80 ms

jquery-3.6.3.min.js

jquery-3.6.3.min.js

222 ms

polyfills.7e0e3a3b2cbadb006a9a.js

polyfills.7e0e3a3b2cbadb006a9a.js

13 ms

runtime.bc8e0b6f17cb69a839ba.js

runtime.bc8e0b6f17cb69a839ba.js

4 ms

commons~articleSpecification~fixed~main~mobile~mobilePurchaseFlow~myTelenor~shared~bc93cd35.9a2aad3802cc37c0b39e.js

commons~articleSpecification~fixed~main~mobile~mobilePurchaseFlow~myTelenor~shared~bc93cd35.9a2aad3802cc37c0b39e.js

5 ms

commons~articleSpecification~fixed~main~mobile~mobilePurchaseFlow~myTelenor~shared~7274e1de.eac7ee954cd77aed39ec.js

commons~articleSpecification~fixed~main~mobile~mobilePurchaseFlow~myTelenor~shared~7274e1de.eac7ee954cd77aed39ec.js

7 ms

commons~articleSpecification~fixed~main~mobile~mobilePurchaseFlow~myTelenor~shared~f170b6bb.93f55355126eb3309bf0.js

commons~articleSpecification~fixed~main~mobile~mobilePurchaseFlow~myTelenor~shared~f170b6bb.93f55355126eb3309bf0.js

8 ms

commons~main~myTelenor~bc93cd35.c0df1993fbe8191cdb61.js

commons~main~myTelenor~bc93cd35.c0df1993fbe8191cdb61.js

12 ms

main.f299157bd8bee60c439b.js

main.f299157bd8bee60c439b.js

6 ms

commons~fixed~mobile~mobilePurchaseFlow~shared~bc93cd35.26697379d344bd940275.js

commons~fixed~mobile~mobilePurchaseFlow~shared~bc93cd35.26697379d344bd940275.js

12 ms

shared.c2432d6476b362c0b055.js

shared.c2432d6476b362c0b055.js

15 ms

telenorlight_woff.woff

telenorlight_woff.woff

3 ms

framework-icons.woff

framework-icons.woff

8 ms

telenor_woff.woff

telenor_woff.woff

9 ms

Accessibility Review

telenor.se accessibility score

77

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-*] attributes do not have valid values

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

High

Some elements have a [tabindex] value greater than 0

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

telenor.se 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

telenor.se SEO score

86

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    SV

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Telenor.se can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Swedish. Our system also found out that Telenor.se 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

telenor.se

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