Tools & Wizards About Us
hvor.no screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

hvor.no

Kart, veibeskrivelse og kjørerute - map/maps | 1881

Page Load Speed

5.9 sec in total

First Response

223 ms

Resources Loaded

5.5 sec

Page Rendered

158 ms

hvor.no screenshot

About Website

Welcome to hvor.no homepage info - get ready to check Hvor best content right away, or after learning these important things about hvor.no

Bruk vår gratis karttjeneste for veibeskrivelse, kjørerute, flyfoto, skråfoto m.m. Detaljrike kart finner du på 1881.no.

Visit hvor.no

Key Findings

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

Performance Metrics

hvor.no performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value4,330 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

hvor.no

223 ms

219 ms

435 ms

kart.1881.no

502 ms

css

50 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Hvor.no, 59% (35 requests) were made to Tiles1881.webatlas.no and 12% (7 requests) were made to Kart.1881.no. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Tiles1881.webatlas.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 170.6 kB (23%)

Content Size

733.0 kB

After Optimization

562.3 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-74%

Potential reduce by 138.2 kB

  • Original 187.6 kB
  • After minification 180.0 kB
  • After compression 49.3 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. 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 138.2 kB or 74% of the original size.

Image Optimization

-6%

Potential reduce by 31.2 kB

  • Original 492.5 kB
  • After minification 461.3 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. Hvor images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 1.1 kB

  • Original 52.8 kB
  • After minification 52.8 kB
  • After compression 51.7 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 5 (10%)

Requests Now

48

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hvor.no

hvor.no

223 ms

219 ms

435 ms

kart.1881.no

kart.1881.no

502 ms

css

css

50 ms

loader.js

loader.js

42 ms

8e1a3768-f5e4-4362-8b50-4742380e4358

8e1a3768-f5e4-4362-8b50-4742380e4358

156 ms

css

css

109 ms

js

js

624 ms

gtm.js

gtm.js

120 ms

aperture.js

aperture.js

43 ms

logo-1881-alt.svg

logo-1881-alt.svg

180 ms

bidseyeview-indicator.png

bidseyeview-indicator.png

283 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

82 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

131 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

150 ms

kleanads-2406281031.js

kleanads-2406281031.js

158 ms

jsdata

jsdata

152 ms

jsdata

jsdata

104 ms

1881-11.woff

1881-11.woff

584 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

77 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

76 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

75 ms

8.png

8.png

408 ms

7.png

7.png

380 ms

8.png

8.png

818 ms

8.png

8.png

522 ms

9.png

9.png

523 ms

7.png

7.png

438 ms

7.png

7.png

563 ms

9.png

9.png

532 ms

9.png

9.png

823 ms

6.png

6.png

626 ms

8.png

8.png

627 ms

8.png

8.png

838 ms

10.png

10.png

827 ms

6.png

6.png

720 ms

6.png

6.png

815 ms

7.png

7.png

909 ms

7.png

7.png

999 ms

9.png

9.png

924 ms

9.png

9.png

3322 ms

10.png

10.png

1476 ms

10.png

10.png

1093 ms

6.png

6.png

1025 ms

6.png

6.png

1093 ms

10.png

10.png

1128 ms

10.png

10.png

1278 ms

8.png

8.png

1187 ms

8.png

8.png

1328 ms

7.png

7.png

1281 ms

7.png

7.png

1372 ms

9.png

9.png

1375 ms

9.png

9.png

1727 ms

6.png

6.png

1466 ms

6.png

6.png

1469 ms

10.png

10.png

1561 ms

10.png

10.png

1700 ms

css

css

108 ms

Accessibility Review

hvor.no accessibility score

82

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.

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

Low

No form fields have multiple labels

High

Form elements do not have associated labels

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

hvor.no SEO score

92

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

Language and Encoding

  • Language Detected

    NO

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

hvor.no

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