7.4 sec in total
1.1 sec
6.2 sec
164 ms
Welcome to ndla.no homepage info - get ready to check NDLA best content for Norway right away, or after learning these important things about ndla.no
Kvalitetssikrede og fritt tilgjengelige nettbaserte læremidler for videregående opplæring
Visit ndla.noWe analyzed Ndla.no page load time and found that the first response time was 1.1 sec and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ndla.no performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value3.5 s
64/100
25%
Value6.7 s
36/100
10%
Value660 ms
45/100
30%
Value0.141
78/100
15%
Value11.9 s
17/100
10%
1059 ms
3403 ms
3427 ms
3491 ms
659 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Ndla.no, 33% (16 requests) were made to Cdn-a.ndlap3.seria.net and 13% (6 requests) were made to Cdn-b.ndlap3.seria.net. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Auth.ndla.no.
Page size can be reduced by 675.6 kB (54%)
1.2 MB
569.8 kB
In fact, the total size of Ndla.no main page is 1.2 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. 40% of websites need less resources to load. Javascripts take 637.8 kB which makes up the majority of the site volume.
Potential reduce by 40.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 40.0 kB or 72% of the original size.
Potential reduce by 23.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. NDLA images are well optimized though.
Potential reduce by 463.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 463.1 kB or 73% of the original size.
Potential reduce by 149.5 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. Ndla.no needs all CSS files to be minified and compressed as it can save up to 149.5 kB or 80% of the original size.
Number of requests can be reduced by 9 (20%)
44
35
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NDLA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
ndla.no
1059 ms
extuserproperties.js.php
3403 ms
extauth.js
3427 ms
roamauth.js.php
3491 ms
ndla_fag_tabs.css
659 ms
css_e362f25ad165f7e82291bedf5a7e4440.css
894 ms
css
65 ms
js_6e68e965f2d6ed73f3797e492af20650.jsmin.js
1262 ms
js_e3eb320c3012604353fa0d858caf2717.jsmin.js
659 ms
spring.js
657 ms
analytics.js
38 ms
logo.png
140 ms
eu_128.png
110 ms
dk_128.png
125 ms
samskrive_128.png
203 ms
naturbruk_profilbilde_0.jpg
303 ms
sx0c5ff8.jpg
314 ms
slideshow_pause.png
241 ms
ndlafilm_128.png
138 ms
fyr_128.png
209 ms
deling_128.png
207 ms
youtube_128.png
213 ms
aktualitet_128.png
214 ms
follow_128.png
247 ms
sy3265ca_1.jpg
357 ms
mahongliyulizhongtian.png
896 ms
syad8202.jpg
234 ms
slideshow_play.png
234 ms
all.js
34 ms
header_bg.jpg
337 ms
topbar_bg.png
332 ms
throbber.gif
338 ms
footer_bg.jpg
482 ms
channel60.js
1020 ms
;;;
749 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
64 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
97 ms
fontawesome-webfont.woff
641 ms
collect
33 ms
237 ms
xd_arbiter.php
46 ms
xd_arbiter.php
79 ms
blank.gif
203 ms
MathJax.js
457 ms
gtm.js
49 ms
close-cross.png
246 ms
collect
25 ms
xd_arbiter.php
19 ms
ndla.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ndla.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
Missing source maps for large first-party JavaScript
ndla.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
Tap targets are not sized appropriately
NO
NB
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ndla.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it does not match the claimed language. Our system also found out that Ndla.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.
ndla.no
Open Graph data is detected on the main page of NDLA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: