Report Summary

  • 19

    Performance

    Renders faster than
    37% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

lebara-mobile.dk

Billige mobilabonnementer og Mobilt Bredbånd

Page Load Speed

3.8 sec in total

First Response

545 ms

Resources Loaded

2.9 sec

Page Rendered

338 ms

lebara-mobile.dk screenshot

About Website

Welcome to lebara-mobile.dk homepage info - get ready to check Lebara Mobile best content right away, or after learning these important things about lebara-mobile.dk

Billige mobilabonnementer inkl. meget data og EU roaming

Visit lebara-mobile.dk

Key Findings

We analyzed Lebara-mobile.dk page load time and found that the first response time was 545 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

lebara-mobile.dk performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value9,330 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.069

96/100

15%

TTI (Time to Interactive)

Value35.2 s

0/100

10%

Network Requests Diagram

www.lebara.dk

545 ms

css

23 ms

bootstrap.css

353 ms

main.css

59 ms

bootstrap-datetimepicker.min.css

139 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Lebara-mobile.dk, 20% (18 requests) were made to Lebara.dk and 7% (6 requests) were made to Assets3.lebara.com. The less responsive or slowest element that took the longest time to load (545 ms) relates to the external source Lebara.dk.

Page Optimization Overview & Recommendations

Page size can be reduced by 931.7 kB (62%)

Content Size

1.5 MB

After Optimization

566.3 kB

In fact, the total size of Lebara-mobile.dk main page is 1.5 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. 65% of websites need less resources to load. CSS take 619.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 114.6 kB

  • Original 137.2 kB
  • After minification 95.8 kB
  • After compression 22.6 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 41.5 kB, which is 30% 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 114.6 kB or 84% of the original size.

Image Optimization

-10%

Potential reduce by 28.2 kB

  • Original 283.7 kB
  • After minification 255.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. Lebara Mobile images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 329.3 kB

  • Original 457.5 kB
  • After minification 416.1 kB
  • After compression 128.2 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 329.3 kB or 72% of the original size.

CSS Optimization

-74%

Potential reduce by 459.5 kB

  • Original 619.5 kB
  • After minification 614.7 kB
  • After compression 160.0 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. Lebara-mobile.dk needs all CSS files to be minified and compressed as it can save up to 459.5 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (59%)

Requests Now

66

After Optimization

27

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

Accessibility Review

lebara-mobile.dk accessibility score

66

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 match their roles

High

ARIA IDs are not unique

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

Heading elements are not in a sequentially-descending order

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lebara-mobile.dk best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

lebara-mobile.dk SEO score

81

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DA

  • Language Claimed

    DA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lebara-mobile.dk can be misinterpreted by Google and other search engines. Our service has detected that Danish is used on the page, and it matches the claimed language. Our system also found out that Lebara-mobile.dk 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 description is not detected on the main page of Lebara Mobile. 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: