9.1 sec in total
364 ms
8.4 sec
309 ms
Visit grei.no now to see the best up-to-date Grei content and also check out these interesting facts you probably never knew about grei.no
Visit grei.noWe analyzed Grei.no page load time and found that the first response time was 364 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
grei.no performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value8.9 s
1/100
25%
Value6.9 s
33/100
10%
Value270 ms
82/100
30%
Value0.199
62/100
15%
Value10.2 s
25/100
10%
364 ms
4721 ms
15 ms
351 ms
235 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 86% of them (66 requests) were addressed to the original Grei.no, 5% (4 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Grei.no.
Page size can be reduced by 1.3 MB (59%)
2.3 MB
942.2 kB
In fact, the total size of Grei.no main page is 2.3 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. 45% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 321 B
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 321 B or 47% of the original size.
Potential reduce by 8.6 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. Grei images are well optimized though.
Potential reduce by 791.5 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 791.5 kB or 73% of the original size.
Potential reduce by 546.4 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. Grei.no needs all CSS files to be minified and compressed as it can save up to 546.4 kB or 88% of the original size.
Number of requests can be reduced by 55 (73%)
75
20
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grei. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
grei.no
364 ms
main.do
4721 ms
analytics.js
15 ms
ddsmoothmenu.css
351 ms
main_styles.css
235 ms
tipsy.css
235 ms
nivo-slider.css
354 ms
styles.css
705 ms
bootstrap-colorpicker.min.css
462 ms
zabuto_calendar.css
463 ms
video-js.css
815 ms
bootstrapValidator.min.css
469 ms
global-style.css
2417 ms
layerslider.css
693 ms
skin.css
587 ms
css
25 ms
collect
12 ms
css
14 ms
jquery.js
1177 ms
jquery-ui-1.9.2.custom.min.css
812 ms
jquery-ui-1.9.2.custom.min.js
2227 ms
jquery.backstretch.min.js
819 ms
jquery.ui.datepicker-no.js
928 ms
jquery.ui.datepicker-fr.js
935 ms
overlibmws.js
1158 ms
TabWindowVisibilityManager.min.js
1051 ms
jquery.cycle.all.js
1352 ms
bootstrap.min.js
237 ms
modernizr.custom.js
118 ms
jquery.mousewheel-3.0.6.pack.js
119 ms
jquery.cookie.js
116 ms
jquery.easing.js
232 ms
bootstrap-hover-dropdown.min.js
234 ms
masonry.js
702 ms
jquery.ui.totop.min.js
346 ms
jquery.mixitup.js
466 ms
jquery.mixitup.init.js
351 ms
jquery.fancybox.pack.js
575 ms
jquery.easypiechart.js
468 ms
waypoints.min.js
526 ms
jquery.sticky.js
581 ms
jquery.wp.custom.js
585 ms
jquery.wp.switcher.js
600 ms
greensock.js
875 ms
zabuto_calendar.js
918 ms
bootstrap-colorpicker.min.js
696 ms
video.js
1439 ms
bootstrapValidator.min.js
1212 ms
layerslider.transitions.js
929 ms
layerslider.kreaturamedia.jquery.js
1164 ms
css
22 ms
css
23 ms
bootstrap.min.css
1207 ms
jquery.fancybox.css
548 ms
font-awesome.css
677 ms
animate.css
1008 ms
easypiechart.css
794 ms
timeline.css
795 ms
all.js
275 ms
Grei_Org_Logo.png
129 ms
blank.gif
123 ms
GUARD_main_i462966_1458305189324.png
1150 ms
GUARD_main_i462966_1458288174885.jpg
238 ms
GUARD_main_i460166_1454755519032.jpg
577 ms
GUARD_sub_main_i462966_1458305189324.png
1199 ms
GUARD_sub_main_i462966_1458288174885.jpg
337 ms
GUARD_sub_main_i460166_1454755519032.jpg
718 ms
fontawesome-webfont.woff
673 ms
dommerhjornet_grei.gif
451 ms
skin.css
477 ms
131 ms
xd_arbiter.php
220 ms
xd_arbiter.php
427 ms
eventsOverviewJson.do
359 ms
ping
56 ms
skin.png
120 ms
blank.gif
120 ms
grei.no accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
grei.no best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
grei.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
NO
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grei.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 Grei.no main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
grei.no
Open Graph description is not detected on the main page of Grei. 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: