Tools & Wizards About Us
degree.no screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

degree.no

Vi utvikler ehandelsløsninger for B2B-markedet

Page Load Speed

4 sec in total

First Response

501 ms

Resources Loaded

3.3 sec

Page Rendered

248 ms

degree.no screenshot

About Website

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

Våre erfarne utviklere, designere og prosjektledere bidrar til at B2B bedrifter lykkes med salg i e-handel og optimaliserer kundereisene.

Visit degree.no

Key Findings

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

degree.no performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value23.3 s

0/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

Network Requests Diagram

degree.no

501 ms

www.degree.no

1133 ms

bootstrap.min.css

1051 ms

font-awesome.min.css

889 ms

degree.css

702 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 79% of them (26 requests) were addressed to the original Degree.no, 6% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Degree.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 270.8 kB (59%)

Content Size

461.0 kB

After Optimization

190.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Degree.no main page is 461.0 kB. 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. Javascripts take 190.7 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 14.6 kB

  • Original 18.8 kB
  • After minification 13.9 kB
  • After compression 4.2 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 4.9 kB, which is 26% 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 14.6 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 92.0 kB
  • After minification 92.0 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. Degree images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 124.7 kB

  • Original 190.7 kB
  • After minification 190.3 kB
  • After compression 66.0 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 124.7 kB or 65% of the original size.

CSS Optimization

-82%

Potential reduce by 131.5 kB

  • Original 159.5 kB
  • After minification 156.5 kB
  • After compression 27.9 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. Degree.no needs all CSS files to be minified and compressed as it can save up to 131.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (25%)

Requests Now

24

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

degree.no

degree.no

501 ms

www.degree.no

www.degree.no

1133 ms

bootstrap.min.css

bootstrap.min.css

1051 ms

font-awesome.min.css

font-awesome.min.css

889 ms

degree.css

degree.css

702 ms

jquery.js

jquery.js

1099 ms

bootstrap.min.js

bootstrap.min.js

919 ms

herbyCookie.min.js

herbyCookie.min.js

348 ms

degree.js

degree.js

538 ms

herbycookie.min.js

herbycookie.min.js

359 ms

fbevents.js

fbevents.js

141 ms

logo_degree_header.svg

logo_degree_header.svg

174 ms

forside_promo.svg

forside_promo.svg

522 ms

forside_blink.svg

forside_blink.svg

177 ms

profile_xtramile.svg

profile_xtramile.svg

179 ms

promo_telenor.svg

promo_telenor.svg

346 ms

promo_berg-hansen.svg

promo_berg-hansen.svg

352 ms

kontakt.svg

kontakt.svg

357 ms

logo_degree_footer.svg

logo_degree_footer.svg

355 ms

gtm.js

gtm.js

71 ms

bakgrunn.jpg

bakgrunn.jpg

546 ms

bakgrunn_trekant.svg

bakgrunn_trekant.svg

680 ms

logo_filemail.svg

logo_filemail.svg

523 ms

ffabe1_0_0.woff

ffabe1_0_0.woff

671 ms

ff1_2_0.woff

ff1_2_0.woff

663 ms

ff1_0_0.woff

ff1_0_0.woff

671 ms

ff1_1_0.woff

ff1_1_0.woff

671 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

677 ms

analytics.js

analytics.js

30 ms

collect

collect

11 ms

collect

collect

96 ms

115 ms

ga-audiences

ga-audiences

34 ms

Accessibility Review

degree.no accessibility score

73

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-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

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

Links do not have a discernible name

Best Practices

degree.no best practices score

83

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

Page has valid source maps

SEO Factors

degree.no SEO score

90

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

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

    NO

  • Language Claimed

    NO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Degree.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 Degree.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

degree.no

Open Graph data is detected on the main page of Degree. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: