Tools & Wizards About Us
nbm.no screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

nbm.no

Norsk Bedriftsmegling: Kjøp og salg av små og store bedrifter

Page Load Speed

2.2 sec in total

First Response

558 ms

Resources Loaded

1.5 sec

Page Rendered

136 ms

nbm.no screenshot

About Website

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

Vi i Norsk Bedriftsmegling AS har til enhver tid et bredt utvalg av virksomheter og bedrifter for salg, samt en stor portefølje av potensielle kjøpere.

Visit nbm.no

Key Findings

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

Performance Metrics

nbm.no performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value23.2 s

0/100

10%

TBT (Total Blocking Time)

Value19,340 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.608

10/100

15%

TTI (Time to Interactive)

Value29.0 s

0/100

10%

Network Requests Diagram

nbm.no

558 ms

style.css

118 ms

head.load.min.js

227 ms

toolbox.js

245 ms

css

25 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 65% of them (15 requests) were addressed to the original Nbm.no, 17% (4 requests) were made to Fonts.gstatic.com and 9% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (558 ms) belongs to the original domain Nbm.no.

Page Optimization Overview & Recommendations

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

Content Size

337.7 kB

After Optimization

139.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nbm.no main page is 337.7 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. 40% of websites need less resources to load. Javascripts take 234.0 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 7.5 kB

  • Original 10.9 kB
  • After minification 10.1 kB
  • After compression 3.4 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 7.5 kB or 68% of the original size.

Image Optimization

-8%

Potential reduce by 4.0 kB

  • Original 49.8 kB
  • After minification 45.8 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. Nbm images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 152.7 kB

  • Original 234.0 kB
  • After minification 215.3 kB
  • After compression 81.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 152.7 kB or 65% of the original size.

CSS Optimization

-79%

Potential reduce by 33.9 kB

  • Original 42.9 kB
  • After minification 42.2 kB
  • After compression 9.1 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. Nbm.no needs all CSS files to be minified and compressed as it can save up to 33.9 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (39%)

Requests Now

18

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nbm.no

nbm.no

558 ms

style.css

style.css

118 ms

head.load.min.js

head.load.min.js

227 ms

toolbox.js

toolbox.js

245 ms

css

css

25 ms

css

css

37 ms

scriptaculous.bundle.min.pack.js

scriptaculous.bundle.min.pack.js

345 ms

common.js

common.js

241 ms

analytics.js

analytics.js

19 ms

gradient_overlay.png

gradient_overlay.png

115 ms

background_pattern.gif

background_pattern.gif

222 ms

loading.gif

loading.gif

226 ms

478399.gif

478399.gif

228 ms

search.png

search.png

228 ms

721327&width=612&height=341&zwidth=612&zheight=408&x=306&y=171.jpg

721327&width=612&height=341&zwidth=612&zheight=408&x=306&y=171.jpg

552 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

60 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

59 ms

printer.png

printer.png

371 ms

share.png

share.png

371 ms

collect

collect

20 ms

4A-myfZX6oDr9CtSTkTGig.ttf

4A-myfZX6oDr9CtSTkTGig.ttf

16 ms

rapsGf8n-DpRu9kcmAAciA.ttf

rapsGf8n-DpRu9kcmAAciA.ttf

17 ms

print.css

print.css

115 ms

Accessibility Review

nbm.no accessibility score

95

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

High

Some elements have a [tabindex] value greater than 0

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

nbm.no best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

nbm.no SEO score

98

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

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

nbm.no

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