6.4 sec in total
374 ms
5.6 sec
446 ms
Welcome to nfmh.is homepage info - get ready to check NFMH best content for Iceland right away, or after learning these important things about nfmh.is
Nemendafélag Menntaskólans við Hamrahlíð
Visit nfmh.isWe analyzed Nfmh.is page load time and found that the first response time was 374 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
nfmh.is performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value6.1 s
12/100
25%
Value3.0 s
94/100
10%
Value240 ms
85/100
30%
Value0.003
100/100
15%
Value5.6 s
69/100
10%
374 ms
1058 ms
1356 ms
28 ms
454 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 25% of them (24 requests) were addressed to the original Nfmh.is, 19% (18 requests) were made to Scontent.cdninstagram.com and 8% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Snapwidget.com.
Page size can be reduced by 679.5 kB (46%)
1.5 MB
785.3 kB
In fact, the total size of Nfmh.is main page is 1.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. 65% of websites need less resources to load. Javascripts take 658.6 kB which makes up the majority of the site volume.
Potential reduce by 72.5 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 72.5 kB or 68% of the original size.
Potential reduce by 123.9 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, NFMH needs image optimization as it can save up to 123.9 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 431.1 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 431.1 kB or 65% of the original size.
Potential reduce by 51.9 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. Nfmh.is needs all CSS files to be minified and compressed as it can save up to 51.9 kB or 81% of the original size.
Number of requests can be reduced by 46 (53%)
86
40
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NFMH. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
nfmh.is
374 ms
www.nfmh.is
1058 ms
main.less
1356 ms
jquery.min.js
28 ms
modernizr.js
454 ms
jquery.flexslider-min.js
451 ms
jquery.fancybox.js
601 ms
jquery.fancybox-thumbs.js
313 ms
select.js
464 ms
fileupload.js
601 ms
jquery.tabs.js
605 ms
sidebar.js
613 ms
js
78 ms
googlemaps.js
574 ms
addthis_widget.js
11 ms
Europe.js
192 ms
css
23 ms
analytics.js
21 ms
nfmh_logo.png
157 ms
252677bd5e5240c3.jpg
463 ms
668e6b36ecc9042.jpg
465 ms
d4a04c8e6edd36ee.jpg
591 ms
b8d8c379a658a98.png
590 ms
1b88efe690e4b9da.png
867 ms
5798bd7b6dae4fc4.jpg
595 ms
www.nfmh.is
773 ms
BkZwJXYnumPMepfEA344yQ.ttf
29 ms
eFfAHNfFT0YtF77QmRKRj_esZW2xOQ-xsNqO47m55DA.ttf
30 ms
9GQrDsQoLNPSbu4a8XkaZw.ttf
30 ms
BfPy-oLZyJitfovLhnoy1A.ttf
31 ms
Pb-Tqi3xXEdTJ3ZTpmCsBw.ttf
31 ms
icomoon.woff
600 ms
collect
52 ms
230 ms
2793 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
45 ms
bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf
44 ms
300lo.json
48 ms
all.js&version=v2.0
63 ms
widgets.js
121 ms
plusone.js
48 ms
pinit00.png
39 ms
jquery.event.move.js
606 ms
sh.8e5f85691f9aaa082472a194.html
36 ms
cb=gapi.loaded_0
66 ms
cb=gapi.loaded_1
64 ms
fastbutton
125 ms
156 ms
xd_arbiter.php
29 ms
xd_arbiter.php
98 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
187 ms
postmessageRelay
68 ms
combined.css
36 ms
smoothDivScroll.css
26 ms
stack_161235.js
84 ms
jquery.min.js
25 ms
cb=gapi.loaded_0
25 ms
cb=gapi.loaded_1
16 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
52 ms
3193398744-postmessagerelay.js
21 ms
rpc:shindig_random.js
57 ms
12071139_1494176294210736_2088779890_n.jpg
92 ms
small_share_sprite.png
18 ms
12070931_1471837849789871_1136780691_n.jpg
52 ms
12107485_766563696806105_1354117265_n.jpg
148 ms
11931195_470974999736561_387434647_n.jpg
105 ms
11909423_993764180681070_1982294093_n.jpg
85 ms
11939313_430573650467591_290416110_n.jpg
51 ms
11249279_1535279620027752_1051946259_n.jpg
86 ms
11909913_462784127224884_15981297_n.jpg
173 ms
11176352_1398115347179539_1718299150_n.jpg
81 ms
collect
11 ms
collect
83 ms
cb=gapi.loaded_0
28 ms
stackpile.api-bfb5078e74.js
38 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
44 ms
nr-885.min.js
18 ms
a53393d12f
46 ms
jot
94 ms
jquery.event.move.js
145 ms
12142639_1631043140518714_421481045_n.jpg
18 ms
12139688_897434560345592_20024340_n.jpg
27 ms
12070658_164780800532030_248521937_n.jpg
12 ms
11917755_893696744016692_540127743_n.jpg
81 ms
11325387_532312933574723_349646007_n.jpg
18 ms
11242035_701772686617289_1194694201_n.jpg
168 ms
11192580_1627909924111370_938551194_n.jpg
35 ms
10956733_636418023170170_496946804_n.jpg
29 ms
10995136_1629733847249352_1782602223_n.jpg
21 ms
bg.png
9 ms
play_small.png
6 ms
collect
3 ms
ping
74 ms
a53393d12f
24 ms
like.php
108 ms
qeKvIRsJabD.js
31 ms
LVx-xkvaJ0b.png
24 ms
nfmh.is 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
nfmh.is 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
nfmh.is 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
IS
IS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nfmh.is can be misinterpreted by Google and other search engines. Our service has detected that Icelandic is used on the page, and it matches the claimed language. Our system also found out that Nfmh.is 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.
nfmh.is
Open Graph description is not detected on the main page of NFMH. 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: