Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

disnorge.no

Slekt og Data | Norges største organisasjon for slektsforskere

Page Load Speed

1.1 sec in total

First Response

273 ms

Resources Loaded

696 ms

Page Rendered

86 ms

disnorge.no screenshot

About Website

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

Slekt og Data er Norges største organisasjon for slektsforskere. Som medlem får du kunnskap, hjelp og inspirasjon til å finne dine røtter. Les mer>

Visit disnorge.no

Key Findings

We analyzed Disnorge.no page load time and found that the first response time was 273 ms and then it took 782 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

disnorge.no performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

disnorge.no

273 ms

www.disnorge.no

417 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that all of those requests were addressed to Disnorge.no and no external sources were called. The less responsive or slowest element that took the longest time to load (417 ms) belongs to the original domain Disnorge.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 33 B (19%)

Content Size

175 B

After Optimization

142 B

In fact, the total size of Disnorge.no main page is 175 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 175 B which makes up the majority of the site volume.

HTML Optimization

-19%

Potential reduce by 33 B

  • Original 175 B
  • After minification 173 B
  • After compression 142 B

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 33 B or 19% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

disnorge.no accessibility score

76

Accessibility Issues

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

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

disnorge.no best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

disnorge.no SEO score

85

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

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

    NO

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Disnorge.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Disnorge.no main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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