4.4 sec in total
445 ms
3.7 sec
266 ms
Visit fug.no now to see the best up-to-date FUG content for Norway and also check out these interesting facts you probably never knew about fug.no
FUG (foreldreutvalget for grunnopplæringen) veileder foreldre og skoleansatte i spørsmål om skolehverdagen. Se mer.
Visit fug.noWe analyzed Fug.no page load time and found that the first response time was 445 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
fug.no performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value6.0 s
13/100
25%
Value7.5 s
27/100
10%
Value1,750 ms
10/100
30%
Value0.159
73/100
15%
Value9.7 s
28/100
10%
445 ms
994 ms
213 ms
220 ms
223 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 33% of them (20 requests) were addressed to the original Fug.no, 33% (20 requests) were made to Img2.custompublish.com and 13% (8 requests) were made to Speech.leseweb.dk. The less responsive or slowest element that took the longest time to load (994 ms) belongs to the original domain Fug.no.
Page size can be reduced by 565.6 kB (62%)
906.1 kB
340.6 kB
In fact, the total size of Fug.no main page is 906.1 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. 65% of websites need less resources to load. Javascripts take 417.2 kB which makes up the majority of the site volume.
Potential reduce by 27.0 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 27.0 kB or 77% of the original size.
Potential reduce by 33.8 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, FUG needs image optimization as it can save up to 33.8 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 266.9 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 266.9 kB or 64% of the original size.
Potential reduce by 237.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. Fug.no needs all CSS files to be minified and compressed as it can save up to 237.8 kB or 84% of the original size.
Number of requests can be reduced by 29 (52%)
56
27
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FUG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
fug.no
445 ms
www.fug.no
994 ms
jquery.mmenu.all.css
213 ms
21358.css
220 ms
21353.css
223 ms
jd7phlpq3ycsirvhya7n.js
600 ms
customization.js
224 ms
jquery.js
335 ms
lightbox.css
223 ms
jquery.lightbox.js
427 ms
jquery.fitVids.js
429 ms
slides.min.jquery.js
430 ms
cycle.min.js
433 ms
jquery.mmenu.min.js
435 ms
feedback.js.php
556 ms
feedback.css.php
106 ms
logo.png
508 ms
en.gif
183 ms
se.gif
221 ms
no.gif
222 ms
tagline.png
496 ms
btn_search_submit-white.png
496 ms
0_3456049.jpg
496 ms
0_3450938.jpg
497 ms
0_1940365.jpg
498 ms
ga.js
72 ms
opacity20.png
165 ms
headerBg.jpg
498 ms
headerBanner.png
355 ms
redBg.png
355 ms
tab.png
354 ms
tinyArrow.png
497 ms
bullet.png
497 ms
nettstedskart.png
498 ms
rss.png
497 ms
facebook[1].png
497 ms
social_twitter_box_blue.png
538 ms
curvey.png
537 ms
footerBg.jpg
547 ms
question53-24.png
319 ms
__utm.gif
12 ms
ypVkdkLhLB8
49 ms
_l0Ht4VsoEg
52 ms
hmWRCKsn6WE
71 ms
www-embed-player-vflfNyN_r.css
33 ms
www-embed-player.js
65 ms
base.js
97 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
73 ms
ad_status.js
47 ms
FUG+40+%C3%A5r+1976-2016,+banner.jpg
443 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
28 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
38 ms
footerLogo.png
438 ms
toolbar_1.gif
239 ms
toolbar_ikonramme_1.gif
244 ms
play_1.gif
244 ms
stop_1.gif
290 ms
question_1.gif
247 ms
settings_closed_1.gif
247 ms
settingsbar_1.gif
475 ms
fug.no accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
fug.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
Page has valid source maps
fug.no SEO score
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
NO
NO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fug.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 Fug.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.
fug.no
Open Graph description is not detected on the main page of FUG. 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: