Tools & Wizards About Us
origin.no screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 0

    Best Practices

  • 85

    SEO

    Google-friendlier than
    56% of websites

origin.no

Origin

Page Load Speed

6.6 sec in total

First Response

321 ms

Resources Loaded

5.9 sec

Page Rendered

412 ms

origin.no screenshot

About Website

Click here to check amazing Origin content. Otherwise, check out these important facts you probably never knew about origin.no

Visit origin.no

Key Findings

We analyzed Origin.no page load time and found that the first response time was 321 ms and then it took 6.3 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

origin.no performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value5.4 s

57/100

10%

TBT (Total Blocking Time)

Value1,160 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

origin.no

321 ms

www.origin.no

905 ms

css

38 ms

styles-ed6eb7e81e.css

241 ms

bundle-28fb98b017.js

358 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 95% of them (74 requests) were addressed to the original Origin.no, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Origin.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 481.8 kB (28%)

Content Size

1.7 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Origin.no main page is 1.7 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. 30% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 23.6 kB

  • Original 26.1 kB
  • After minification 18.1 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 7.9 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 23.6 kB or 90% of the original size.

Image Optimization

-24%

Potential reduce by 370.3 kB

  • Original 1.5 MB
  • After minification 1.2 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. Obviously, Origin needs image optimization as it can save up to 370.3 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 87.3 kB

  • Original 138.6 kB
  • After minification 138.6 kB
  • After compression 51.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 87.3 kB or 63% of the original size.

CSS Optimization

-49%

Potential reduce by 667 B

  • Original 1.4 kB
  • After minification 1.2 kB
  • After compression 693 B

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. Origin.no needs all CSS files to be minified and compressed as it can save up to 667 B or 49% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

75

After Optimization

75

  • Images
  • JavaScript
  • CSS

The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Origin. According to our analytics all requests are already optimized.

Network Requests Diagram

origin.no

origin.no

321 ms

www.origin.no

www.origin.no

905 ms

css

css

38 ms

styles-ed6eb7e81e.css

styles-ed6eb7e81e.css

241 ms

bundle-28fb98b017.js

bundle-28fb98b017.js

358 ms

origin.png

origin.png

273 ms

front.png

front.png

1420 ms

10.png

10.png

274 ms

11.png

11.png

274 ms

13.png

13.png

470 ms

14.png

14.png

471 ms

15.png

15.png

558 ms

16.png

16.png

1409 ms

17.png

17.png

1565 ms

18.png

18.png

1564 ms

19.png

19.png

2563 ms

2.png

2.png

793 ms

20.png

20.png

1024 ms

21.png

21.png

1256 ms

22.png

22.png

1491 ms

23.png

23.png

1642 ms

24.png

24.png

1651 ms

25.png

25.png

1727 ms

26.png

26.png

1793 ms

28.png

28.png

2563 ms

29.png

29.png

1875 ms

3.png

3.png

2563 ms

30.png

30.png

1957 ms

31.png

31.png

2026 ms

32.png

32.png

2105 ms

33.png

33.png

2192 ms

34.png

34.png

2262 ms

35.png

35.png

2340 ms

36.png

36.png

2425 ms

37.png

37.png

2562 ms

38.png

38.png

2575 ms

39.png

39.png

2660 ms

4.png

4.png

2797 ms

40.png

40.png

2799 ms

analytics.js

analytics.js

34 ms

42.png

42.png

2536 ms

44.png

44.png

2537 ms

46.png

46.png

2543 ms

47.png

47.png

2626 ms

4GwpJM7qx9X5Obd9KsnKxQ.ttf

4GwpJM7qx9X5Obd9KsnKxQ.ttf

37 ms

collect

collect

12 ms

48.png

48.png

2655 ms

49.png

49.png

2569 ms

5.png

5.png

2569 ms

50.png

50.png

2482 ms

51.png

51.png

2257 ms

52.png

52.png

2109 ms

53.png

53.png

2007 ms

54.png

54.png

1863 ms

55.png

55.png

1854 ms

56.png

56.png

1782 ms

57.png

57.png

1721 ms

58.png

58.png

1805 ms

59.png

59.png

1855 ms

6.png

6.png

1850 ms

60.png

60.png

1777 ms

61.png

61.png

1712 ms

62.png

62.png

1642 ms

63.png

63.png

1643 ms

64.png

64.png

1704 ms

65.png

65.png

1630 ms

66.png

66.png

1546 ms

7.png

7.png

1476 ms

rune.png

rune.png

1650 ms

geir.png

geir.png

1645 ms

Bj%C3%B8rnar.png

Bj%C3%B8rnar.png

1994 ms

trygve.png

trygve.png

1645 ms

torbj%C3%B8rn.png

torbj%C3%B8rn.png

1641 ms

kushil.png

kushil.png

1647 ms

gunnar-skjold.png

gunnar-skjold.png

1879 ms

trond.png

trond.png

1877 ms

ask.png

ask.png

1877 ms

long.png

long.png

1876 ms

Accessibility Review

origin.no accessibility score

70

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

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

SEO Factors

origin.no SEO score

85

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

origin.no

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