Report Summary

  • 28

    Performance

    Renders faster than
    49% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 95% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

onecall.no

Mobilabonnement – Mobiltelefon – Mobilt bredbånd | OneCall

Page Load Speed

4.8 sec in total

First Response

720 ms

Resources Loaded

3.7 sec

Page Rendered

338 ms

onecall.no screenshot

About Website

Click here to check amazing One Call content for Norway. Otherwise, check out these important facts you probably never knew about onecall.no

OneCall tilbyr billige og enkle mobilabonnement og selger mobiltelefoner uten bindingstid.

Visit onecall.no

Key Findings

We analyzed Onecall.no page load time and found that the first response time was 720 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

onecall.no performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value1,120 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.286

42/100

15%

TTI (Time to Interactive)

Value8.0 s

43/100

10%

Network Requests Diagram

onecall.no

720 ms

bootstrap.min.css

50 ms

ionicons.min.css

43 ms

bootstrap_v2.css

227 ms

gs.css

346 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 55% of them (28 requests) were addressed to the original Onecall.no, 10% (5 requests) were made to Track.adform.net and 8% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Onecall.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 264.3 kB (18%)

Content Size

1.5 MB

After Optimization

1.2 MB

In fact, the total size of Onecall.no 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. 25% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 19.8 kB

  • Original 25.7 kB
  • After minification 22.8 kB
  • After compression 5.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 2.9 kB, which is 11% 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 19.8 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.1 MB
  • After minification 1.1 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. One Call images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 102.8 kB

  • Original 204.9 kB
  • After minification 181.9 kB
  • After compression 102.1 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 102.8 kB or 50% of the original size.

CSS Optimization

-83%

Potential reduce by 141.6 kB

  • Original 171.0 kB
  • After minification 168.0 kB
  • After compression 29.4 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. Onecall.no needs all CSS files to be minified and compressed as it can save up to 141.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (61%)

Requests Now

44

After Optimization

17

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

Accessibility Review

onecall.no accessibility score

98

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

Links do not have a discernible name

Best Practices

onecall.no 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

High

Page has valid source maps

SEO Factors

onecall.no SEO score

100

Search Engine Optimization Advices

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

    NO

  • Encoding

    UTF-8

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