Tools & Wizards About Us

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

o2.se

Corporate - OX2

Page Load Speed

7.1 sec in total

First Response

341 ms

Resources Loaded

6.3 sec

Page Rendered

401 ms

About Website

Welcome to o2.se homepage info - get ready to check O 2 best content right away, or after learning these important things about o2.se

OX2 accelerates access to renewable energy. We see ourselves becoming the leading provider of renewable energy solutions globally, thereby powering the great shift.

Visit o2.se

Key Findings

We analyzed O2.se page load time and found that the first response time was 341 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

o2.se performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.04

99/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

o2.se

341 ms

www.o2.se

744 ms

www.ox2.com

1030 ms

language-selector.css

117 ms

style.css

217 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original O2.se, 52% (49 requests) were made to Ox2.com and 18% (17 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Ox2.com.

Page Optimization Overview & Recommendations

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

Content Size

2.0 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 74.4 kB

  • Original 87.8 kB
  • After minification 84.7 kB
  • After compression 13.4 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 74.4 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 39.0 kB

  • Original 804.6 kB
  • After minification 765.7 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. O 2 images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 624.9 kB

  • Original 966.6 kB
  • After minification 931.8 kB
  • After compression 341.8 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 624.9 kB or 65% of the original size.

CSS Optimization

-85%

Potential reduce by 92.7 kB

  • Original 108.9 kB
  • After minification 80.3 kB
  • After compression 16.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. O2.se needs all CSS files to be minified and compressed as it can save up to 92.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (57%)

Requests Now

82

After Optimization

35

  • Images
  • JavaScript
  • CSS

The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of O 2. 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 16 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

o2.se accessibility score

90

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Best Practices

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

SEO Factors

o2.se SEO score

86

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Language Claimed

    SV

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise O2.se can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Swedish language. Our system also found out that O2.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

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