6.3 sec in total
1.4 sec
4.6 sec
309 ms
Click here to check amazing FRAM Mr content for Norway. Otherwise, check out these important facts you probably never knew about frammr.no
Visit frammr.noWe analyzed Frammr.no page load time and found that the first response time was 1.4 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
frammr.no performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value7.4 s
4/100
25%
Value6.7 s
37/100
10%
Value10 ms
100/100
30%
Value0.011
100/100
15%
Value6.0 s
64/100
10%
1368 ms
945 ms
382 ms
258 ms
395 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 77% of them (44 requests) were addressed to the original Frammr.no, 16% (9 requests) were made to Reiseplanlegger.frammr.no and 4% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Frammr.no.
Page size can be reduced by 1.8 MB (73%)
2.5 MB
675.6 kB
In fact, the total size of Frammr.no main page is 2.5 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. 35% of websites need less resources to load. Javascripts take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 41.2 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 8.7 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 41.2 kB or 77% of the original size.
Potential reduce by 63.0 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, FRAM Mr needs image optimization as it can save up to 63.0 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.5 MB
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 1.5 MB or 80% of the original size.
Potential reduce by 280.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. Frammr.no needs all CSS files to be minified and compressed as it can save up to 280.0 kB or 83% of the original size.
Number of requests can be reduced by 35 (64%)
55
20
The browser has sent 55 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 21 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
frammr.no
1368 ms
default.css
945 ms
module.css
382 ms
module.css
258 ms
skin.css
395 ms
container.css
252 ms
container.css
258 ms
container.css
372 ms
portal.css
380 ms
searchskinobjectpreview.css
381 ms
bootstrap.min.custom18.css
891 ms
tilpassninger.css
489 ms
style.css
511 ms
jquery.js
1747 ms
jquery-migrate.js
597 ms
jquery-ui.js
2251 ms
Telerik.Web.UI.WebResource.axd
819 ms
WebResource.axd
803 ms
Telerik.Web.UI.WebResource.axd
1869 ms
dnn.js
825 ms
dnn.modalpopup.js
960 ms
jquery.hoverintent.min.js
901 ms
dnn.servicesframework.js
948 ms
dnn.jquery.js
1530 ms
respond.js
1067 ms
dnncore.js
1085 ms
searchskinobjectpreview.js
1185 ms
jquery-ui.css
6 ms
jquery.textext.min.js
1591 ms
Styles.css
1194 ms
bootstrap.js
1318 ms
initWidgets.js
1419 ms
Stor_Fram_Logo_Sort.jpg
1280 ms
Stor_Fram_logo_Hvit.jpg
1278 ms
warning.gif
620 ms
facebook_icon1.gif
619 ms
Fram_toppbilde_1040x400_ViSamlar.jpg
513 ms
bacgroundSearchWithHeader.jpg
148 ms
TravelMagicWE.dll
402 ms
backgroundReisekortMedHeader.jpg
130 ms
Trafikkmeldinger_header.jpg
150 ms
Aktuelt_header.gif
127 ms
footerBottomImage.jpg
122 ms
glyphicons-halflings-regular.woff
355 ms
analytics.js
78 ms
DotNetNukeAjaxShared.js
215 ms
ui-bg_flat_75_ffffff_40x100.png
49 ms
collect
31 ms
widgets.js
124 ms
mobile.css
330 ms
modernizr.js
253 ms
jquery.js
425 ms
jquery.mobile.js
575 ms
mobile.scripts.js
306 ms
back-m.png
170 ms
ajax-loader.gif
139 ms
icons-18-white.png
132 ms
frammr.no accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
frammr.no best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
frammr.no SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
NN
NB
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 does not match 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.
frammr.no
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: