Tools & Wizards About Us
dig3.no screenshot

Report Summary

  • 81

    Performance

    Renders faster than
    86% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

dig3.no

Velkommen til Dig3 - Lillehammer kommune

Page Load Speed

4 sec in total

First Response

453 ms

Resources Loaded

3.5 sec

Page Rendered

103 ms

dig3.no screenshot

About Website

Visit dig3.no now to see the best up-to-date Dig3 content for Norway and also check out these interesting facts you probably never knew about dig3.no

Forside

Visit dig3.no

Key Findings

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

dig3.no performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

79/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.052

98/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

dig3.no

453 ms

www.dig3.no

591 ms

forside.457556.no.html

127 ms

23660.1850.css

114 ms

jquery.js

338 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 62% of them (18 requests) were addressed to the original Dig3.no, 28% (8 requests) were made to Custompublish.com and 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Custompublish.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 90.5 kB (16%)

Content Size

550.4 kB

After Optimization

459.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dig3.no main page is 550.4 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. 15% of websites need less resources to load. Images take 429.8 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 9.9 kB

  • Original 13.1 kB
  • After minification 11.2 kB
  • After compression 3.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 1.9 kB, which is 14% 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 9.9 kB or 75% of the original size.

Image Optimization

-10%

Potential reduce by 44.7 kB

  • Original 429.8 kB
  • After minification 385.1 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. Dig3 images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 33.2 kB

  • Original 94.9 kB
  • After minification 94.9 kB
  • After compression 61.6 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 33.2 kB or 35% of the original size.

CSS Optimization

-21%

Potential reduce by 2.7 kB

  • Original 12.6 kB
  • After minification 12.6 kB
  • After compression 9.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. Dig3.no needs all CSS files to be minified and compressed as it can save up to 2.7 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (58%)

Requests Now

26

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dig3.no

dig3.no

453 ms

www.dig3.no

www.dig3.no

591 ms

forside.457556.no.html

forside.457556.no.html

127 ms

23660.1850.css

23660.1850.css

114 ms

jquery.js

jquery.js

338 ms

jquery.cycle.lite.1.0.min.js

jquery.cycle.lite.1.0.min.js

328 ms

lightbox.css

lightbox.css

329 ms

jquery.lightbox.js

jquery.lightbox.js

330 ms

shop4.css

shop4.css

329 ms

cpcommon.css

cpcommon.css

353 ms

cpcommon.js.php

cpcommon.js.php

441 ms

kommuneextra.css

kommuneextra.css

438 ms

kommuneextra.js

kommuneextra.js

438 ms

shop4jq.js

shop4jq.js

439 ms

shop_cr.js

shop_cr.js

467 ms

cookieinfo.js

cookieinfo.js

469 ms

cookieinfo.css

cookieinfo.css

546 ms

feedback.js.php

feedback.js.php

559 ms

analytics.js

analytics.js

16 ms

collect

collect

11 ms

js

js

60 ms

dig3introtop.jpg

dig3introtop.jpg

884 ms

menybilde.png

menybilde.png

656 ms

larer.png

larer.png

890 ms

foresatt.png

foresatt.png

785 ms

gausdal.jpg

gausdal.jpg

786 ms

elev.png

elev.png

1011 ms

lillehammer.jpg

lillehammer.jpg

570 ms

oyer.jpg

oyer.jpg

582 ms

Accessibility Review

dig3.no accessibility score

76

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

dig3.no best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

dig3.no SEO score

69

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

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 Dig3.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 Dig3.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

dig3.no

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