Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

frammr.no

FRAM

Page Load Speed

2.4 sec in total

First Response

410 ms

Resources Loaded

1.8 sec

Page Rendered

222 ms

frammr.no screenshot

About Website

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

Kollektivtilbodet i Møre og Romsdal

Visit frammr.no

Key Findings

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

Performance Metrics

frammr.no performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

frammr.no

410 ms

default-typography.css

104 ms

default-skip-to-links.css

202 ms

default-tabfocus-styles.css

307 ms

jquery-1.12.4.min.js

581 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 71% of them (29 requests) were addressed to the original Frammr.no, 5% (2 requests) were made to Reise.frammr.no and 5% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (705 ms) belongs to the original domain Frammr.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.8 kB (25%)

Content Size

136.5 kB

After Optimization

101.7 kB

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

HTML Optimization

-70%

Potential reduce by 29.2 kB

  • Original 41.6 kB
  • After minification 37.3 kB
  • After compression 12.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 29.2 kB or 70% of the original size.

JavaScript Optimization

-6%

Potential reduce by 4.6 kB

  • Original 81.2 kB
  • After minification 81.1 kB
  • After compression 76.6 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

-7%

Potential reduce by 954 B

  • Original 13.7 kB
  • After minification 13.7 kB
  • After compression 12.8 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. Frammr.no has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (77%)

Requests Now

39

After Optimization

9

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

Accessibility Review

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

High

Links do not have a discernible name

Best Practices

frammr.no best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

frammr.no SEO score

91

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

    NN

  • Language Claimed

    NN

  • Encoding

    UTF-8

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

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