2.8 sec in total
532 ms
2 sec
218 ms
Click here to check amazing Greenmobile content. Otherwise, check out these important facts you probably never knew about greenmobile.no
SoMe-ads, Google ads, SEO — HØRT
Visit greenmobile.noWe analyzed Greenmobile.no page load time and found that the first response time was 532 ms and then it took 2.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.
greenmobile.no performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value7.1 s
5/100
25%
Value9.0 s
14/100
10%
Value6,350 ms
0/100
30%
Value0
100/100
15%
Value11.5 s
18/100
10%
532 ms
215 ms
214 ms
6 ms
213 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Greenmobile.no, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (920 ms) relates to the external source Atea.no.
Page size can be reduced by 240.4 kB (47%)
509.9 kB
269.6 kB
In fact, the total size of Greenmobile.no main page is 509.9 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 251.1 kB which makes up the majority of the site volume.
Potential reduce by 17.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. This page needs HTML code to be minified as it can gain 5.9 kB, which is 27% 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 17.4 kB or 78% of the original size.
Potential reduce by 15.4 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. Greenmobile images are well optimized though.
Potential reduce by 184.4 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 184.4 kB or 73% of the original size.
Potential reduce by 23.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. Greenmobile.no needs all CSS files to be minified and compressed as it can save up to 23.2 kB or 84% of the original size.
Number of requests can be reduced by 33 (65%)
51
18
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greenmobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
532 ms
screen.css
215 ms
menu.css
214 ms
jquery.min.js
6 ms
site.js
213 ms
WebResource.axd
241 ms
gtm.js
97 ms
LoginEshop.aspx
134 ms
bg_top.jpg
126 ms
logo.gif
133 ms
arrow_right.gif
133 ms
gb.gif
134 ms
no.gif
228 ms
se.gif
258 ms
dk.gif
227 ms
fi.gif
256 ms
lv.gif
256 ms
ee.gif
267 ms
lt.gif
341 ms
nav_bottom.gif
333 ms
nav_top.gif
394 ms
background_section_open.png
396 ms
gray_menuarrow_right.gif
397 ms
gray_menuarrow_down.gif
396 ms
button_dotted.png
442 ms
background_section.png
445 ms
subpage_bottom.gif
473 ms
subpage_top.gif
479 ms
LoopMann.jpg
920 ms
Loop_priser.jpg
817 ms
PC_kjetting.jpg
658 ms
411136108f9c3223159f5ad74ee8acce.png
554 ms
Loop_Utstyr.jpg
793 ms
logo_facebook.png
588 ms
logo_twitter.png
663 ms
logo_linkedin.png
699 ms
icon_printer.gif
769 ms
bg_footer.jpg
713 ms
conversion_async.js
23 ms
analytics.js
23 ms
fbds.js
18 ms
hotjar-19826.js
152 ms
eshop_top.gif
795 ms
eshop_bg.gif
788 ms
collect
16 ms
161 ms
132 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
91 ms
ga-audiences
67 ms
visit-data
211 ms
print.css
107 ms
22 ms
greenmobile.no accessibility score
greenmobile.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
greenmobile.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 doesn't use legible font sizes
Tap targets are not sized appropriately
NO
NO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greenmobile.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it matches the claimed language. Our system also found out that Greenmobile.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.
greenmobile.no
Open Graph description is not detected on the main page of Greenmobile. 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: