Tools & Wizards About Us
nifab.no screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    83% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

nifab.no

NIFAB - Norsk informasjon for allmenn bruk

Page Load Speed

2.4 sec in total

First Response

567 ms

Resources Loaded

1.7 sec

Page Rendered

124 ms

nifab.no screenshot

About Website

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

Norsk informasjon for allmenn bruk

Visit nifab.no

Key Findings

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

Performance Metrics

nifab.no performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value4.9 s

77/100

10%

Network Requests Diagram

nifab.no

567 ms

core.css

475 ms

frontpage.css

289 ms

jquery-1.3.2.min.js

505 ms

jquery.cookies.2.0.1.min.js

318 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 90% of them (53 requests) were addressed to the original Nifab.no, 5% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to Survey.webstatus.v2.userneeds.dk. The less responsive or slowest element that took the longest time to load (665 ms) belongs to the original domain Nifab.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 169.9 kB (53%)

Content Size

322.2 kB

After Optimization

152.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 16.3 kB

  • Original 20.9 kB
  • After minification 15.7 kB
  • After compression 4.5 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 5.2 kB, which is 25% 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 16.3 kB or 78% of the original size.

Image Optimization

-27%

Potential reduce by 35.3 kB

  • Original 129.2 kB
  • After minification 93.9 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. Obviously, NIFAB needs image optimization as it can save up to 35.3 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-55%

Potential reduce by 49.6 kB

  • Original 90.5 kB
  • After minification 86.2 kB
  • After compression 40.9 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 49.6 kB or 55% of the original size.

CSS Optimization

-84%

Potential reduce by 68.6 kB

  • Original 81.7 kB
  • After minification 69.0 kB
  • After compression 13.0 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. Nifab.no needs all CSS files to be minified and compressed as it can save up to 68.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (63%)

Requests Now

57

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nifab.no

nifab.no

567 ms

core.css

core.css

475 ms

frontpage.css

frontpage.css

289 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

505 ms

jquery.cookies.2.0.1.min.js

jquery.cookies.2.0.1.min.js

318 ms

jquery.scrolloffset.1.0.js

jquery.scrolloffset.1.0.js

216 ms

jquery.urlcheck.1.0.js

jquery.urlcheck.1.0.js

296 ms

collection.js

collection.js

323 ms

wb.js

wb.js

384 ms

textboxSwitcher.js

textboxSwitcher.js

396 ms

global.css

global.css

102 ms

sitebar.css

sitebar.css

97 ms

sitebar_christmas.css

sitebar_christmas.css

106 ms

banner.css

banner.css

97 ms

topmenu.css

topmenu.css

110 ms

layout.css

layout.css

132 ms

imagegallery.css

imagegallery.css

190 ms

medialist.css

medialist.css

192 ms

wsi.ashx

wsi.ashx

376 ms

HONConduct584151_s1.gif

HONConduct584151_s1.gif

208 ms

sitebar-bg.gif

sitebar-bg.gif

117 ms

eng-GB.gif

eng-GB.gif

115 ms

body-bg.gif

body-bg.gif

117 ms

profile-elements2.gif

profile-elements2.gif

117 ms

left2.gif

left2.gif

115 ms

right2.gif

right2.gif

123 ms

nifab_RGB.png

nifab_RGB.png

192 ms

topmenu.png

topmenu.png

287 ms

ml.gif

ml.gif

204 ms

mr.gif

mr.gif

204 ms

tc.gif

tc.gif

211 ms

tl.gif

tl.gif

215 ms

tr.gif

tr.gif

285 ms

button-left.png

button-left.png

306 ms

button-back.png

button-back.png

312 ms

button-right.png

button-right.png

315 ms

bc.gif

bc.gif

321 ms

bl.gif

bl.gif

381 ms

br.gif

br.gif

384 ms

left.gif

left.gif

406 ms

puslespill_foto_colourbox_com_fp_news_small.jpg

puslespill_foto_colourbox_com_fp_news_small.jpg

413 ms

collage_frauke_fp_news_small.jpg

collage_frauke_fp_news_small.jpg

419 ms

hvem_er_de_alternative_behandlerne_illustrasjonsfoto_colourbox_com_fp_news_small.jpg

hvem_er_de_alternative_behandlerne_illustrasjonsfoto_colourbox_com_fp_news_small.jpg

534 ms

kunstterapi_fp_news_small.jpg

kunstterapi_fp_news_small.jpg

476 ms

2x1_grey.gif

2x1_grey.gif

479 ms

rightw.gif

rightw.gif

506 ms

nafkam-logo-negativt.png

nafkam-logo-negativt.png

514 ms

fb-footer.gif

fb-footer.gif

524 ms

twitter-footer.gif

twitter-footer.gif

570 ms

rss-footer.gif

rss-footer.gif

574 ms

googleplus.png

googleplus.png

607 ms

linkedin.png

linkedin.png

616 ms

youtube.png

youtube.png

628 ms

NorskLogoSekAvsenderNeg_svart.png

NorskLogoSekAvsenderNeg_svart.png

642 ms

helsedirektoratet.gif

helsedirektoratet.gif

665 ms

ga.js

ga.js

8 ms

__utm.gif

__utm.gif

26 ms

__utm.gif

__utm.gif

29 ms

collect

collect

61 ms

Accessibility Review

nifab.no accessibility score

91

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

Buttons do not have an accessible name

Best Practices

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

nifab.no SEO score

97

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

nifab.no

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