Tools & Wizards About Us
rpfn.no screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

rpfn.no

Retinitis Pigmentosa Foreningen i Norge - Offisielt nettsted

Page Load Speed

4.7 sec in total

First Response

288 ms

Resources Loaded

3.7 sec

Page Rendered

643 ms

rpfn.no screenshot

About Website

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

Vi ønsker å spre informasjon om øyesykdommen Retinitis Pigmentosa. Medlemsskap i foreningen er åpen for alle med interesse for denne sykdommen.

Visit rpfn.no

Key Findings

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

Performance Metrics

rpfn.no performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value8.1 s

20/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

rpfn.no

288 ms

rpfn.no

2639 ms

gtm.js

57 ms

style.min.css

549 ms

styles.css

278 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 98% of them (42 requests) were addressed to the original Rpfn.no, 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Rpfn.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 504.0 kB (49%)

Content Size

1.0 MB

After Optimization

534.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 79.1 kB

  • Original 100.8 kB
  • After minification 99.1 kB
  • After compression 21.7 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 79.1 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 5.2 kB

  • Original 405.1 kB
  • After minification 399.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. Rpfn images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 134.5 kB

  • Original 198.4 kB
  • After minification 189.6 kB
  • After compression 63.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 134.5 kB or 68% of the original size.

CSS Optimization

-85%

Potential reduce by 285.1 kB

  • Original 334.3 kB
  • After minification 309.3 kB
  • After compression 49.2 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. Rpfn.no needs all CSS files to be minified and compressed as it can save up to 285.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (82%)

Requests Now

39

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rpfn.no

rpfn.no

288 ms

rpfn.no

rpfn.no

2639 ms

gtm.js

gtm.js

57 ms

style.min.css

style.min.css

549 ms

styles.css

styles.css

278 ms

ivory-search.min.css

ivory-search.min.css

278 ms

style.css

style.css

279 ms

style.css

style.css

280 ms

front.min.css

front.min.css

368 ms

main.css

main.css

642 ms

style.css

style.css

243 ms

jquery.min.js

jquery.min.js

424 ms

jquery-migrate.min.js

jquery-migrate.min.js

336 ms

wp-hide-post-public.js

wp-hide-post-public.js

336 ms

front.min.js

front.min.js

407 ms

variables-skeleton.min.css

variables-skeleton.min.css

118 ms

variables-full.min.css

variables-full.min.css

118 ms

common-skeleton.min.css

common-skeleton.min.css

119 ms

common-full.min.css

common-full.min.css

192 ms

widget-events-list-skeleton.min.css

widget-events-list-skeleton.min.css

313 ms

widget-events-list-full.min.css

widget-events-list-full.min.css

312 ms

index.js

index.js

313 ms

index.js

index.js

312 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

314 ms

scripts-navigation-accessibility.js

scripts-navigation-accessibility.js

316 ms

scripts-navigation-mobile.js

scripts-navigation-mobile.js

328 ms

jquery.fitvids.js

jquery.fitvids.js

329 ms

scripts-global.js

scripts-global.js

329 ms

ivory-search.min.js

ivory-search.min.js

447 ms

tribe-common.min.js

tribe-common.min.js

449 ms

query-string.min.js

query-string.min.js

451 ms

underscore-before.js

underscore-before.js

450 ms

underscore.min.js

underscore.min.js

449 ms

underscore-after.js

underscore-after.js

449 ms

manager.min.js

manager.min.js

451 ms

breakpoints.min.js

breakpoints.min.js

478 ms

rp-logo-3.png

rp-logo-3.png

285 ms

forskning-1920x720.jpg

forskning-1920x720.jpg

351 ms

forskning-806x453.jpg

forskning-806x453.jpg

550 ms

RP-nytt_2023-3_Thumb.jpg

RP-nytt_2023-3_Thumb.jpg

494 ms

retina-int.gif

retina-int.gif

201 ms

Genericons-Neue.woff

Genericons-Neue.woff

219 ms

retina-int.gif

retina-int.gif

133 ms

Accessibility Review

rpfn.no accessibility score

100

Accessibility Issues

Best Practices

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

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

    NB

  • Encoding

    UTF-8

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

rpfn.no

Open Graph data is detected on the main page of Rpfn. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: