Tools & Wizards About Us
fp.no screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

fp.no

Forsvarets Personellservice - Forsvarets Personellservice

Page Load Speed

7.4 sec in total

First Response

875 ms

Resources Loaded

5.5 sec

Page Rendered

971 ms

fp.no screenshot

About Website

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

En fast organisert spareforening og servicekontor for ansatte i Forsvaret. Her finner du alt om medlemskap, forsikringer, lån og mye mer.

Visit fp.no

Key Findings

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

Performance Metrics

fp.no performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.84

4/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

www.fp.no

875 ms

uc.js

22 ms

versioned-asset-18D2406E0630C811EA1032B96F2F6D2D.styles.css

325 ms

custom2101242.css

243 ms

versioned-asset-C8BD963C7917AA56E3BFEF730D0FE6A2.core.js

813 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 95% of them (18 requests) were addressed to the original Fp.no, 5% (1 request) were made to Policy.app.cookieinformation.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Fp.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 82.9 kB (3%)

Content Size

2.8 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fp.no main page is 2.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 37.4 kB

  • Original 45.6 kB
  • After minification 38.5 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 7.1 kB, which is 16% 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 37.4 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 37.9 kB

  • Original 2.4 MB
  • After minification 2.4 MB

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. Fp images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 12 B

  • Original 260.2 kB
  • After minification 260.2 kB
  • After compression 260.2 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.

CSS Optimization

-6%

Potential reduce by 7.6 kB

  • Original 129.9 kB
  • After minification 122.5 kB
  • After compression 122.3 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. Fp.no has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

15

After Optimization

15

  • Images
  • JavaScript
  • CSS

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fp. According to our analytics all requests are already optimized.

Network Requests Diagram

www.fp.no

www.fp.no

875 ms

uc.js

uc.js

22 ms

versioned-asset-18D2406E0630C811EA1032B96F2F6D2D.styles.css

versioned-asset-18D2406E0630C811EA1032B96F2F6D2D.styles.css

325 ms

custom2101242.css

custom2101242.css

243 ms

versioned-asset-C8BD963C7917AA56E3BFEF730D0FE6A2.core.js

versioned-asset-C8BD963C7917AA56E3BFEF730D0FE6A2.core.js

813 ms

forsvaretspersonellservice.png

forsvaretspersonellservice.png

82 ms

fjell-og-innsjo-filter-2000x571px-21x6-72.png

fjell-og-innsjo-filter-2000x571px-21x6-72.png

797 ms

soldat-med-instrument-4x3-72.png

soldat-med-instrument-4x3-72.png

3197 ms

fjell-og-innsjo-i-midnattsol-4x3-72.png

fjell-og-innsjo-i-midnattsol-4x3-72.png

963 ms

hus-paa-brygge-4x3-72.png

hus-paa-brygge-4x3-72.png

885 ms

festningen-4x3-72.png

festningen-4x3-72.png

891 ms

fp-appen1.png

fp-appen1.png

505 ms

norske-enkroninger-16x9-72.png

norske-enkroninger-16x9-72.png

3979 ms

dame-p-laptop-16x9-72.png

dame-p-laptop-16x9-72.png

878 ms

if-lappen-16x9m-logo.png

if-lappen-16x9m-logo.png

960 ms

full-bredde-hvit-fp-logo-287x169px.png

full-bredde-hvit-fp-logo-287x169px.png

965 ms

Lato-Regular.woff

Lato-Regular.woff

965 ms

Lato-Black.woff

Lato-Black.woff

1031 ms

OpenSans-Regular.woff

OpenSans-Regular.woff

1050 ms

Accessibility Review

fp.no accessibility score

95

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.

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

Links do not have a discernible name

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

fp.no SEO score

100

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

Language and Encoding

  • Language Detected

    NO

  • Language Claimed

    NB

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fp.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it does not match the claimed language. Our system also found out that Fp.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

fp.no

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