5.5 sec in total
372 ms
5 sec
159 ms
Visit legemiddelverket.no now to see the best up-to-date Legemiddelverket content for Norway and also check out these interesting facts you probably never knew about legemiddelverket.no
Statens legemiddelverk skal sikre at alle legemidler som blir brukt i Norge har god kvalitet, er trygge å bruke og har ønsket virkning.
Visit legemiddelverket.noWe analyzed Legemiddelverket.no page load time and found that the first response time was 372 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
legemiddelverket.no performance score
name
value
score
weighting
Value8.9 s
0/100
10%
Value11.6 s
0/100
25%
Value9.6 s
11/100
10%
Value430 ms
64/100
30%
Value0.301
39/100
15%
Value22.0 s
1/100
10%
372 ms
2947 ms
246 ms
254 ms
253 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 96% of them (54 requests) were addressed to the original Legemiddelverket.no, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Legemiddelverket.no.
Page size can be reduced by 1.8 MB (70%)
2.6 MB
775.4 kB
In fact, the total size of Legemiddelverket.no main page is 2.6 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 1.7 MB which makes up the majority of the site volume.
Potential reduce by 92.9 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 92.9 kB or 39% of the original size.
Potential reduce by 23.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, Legemiddelverket needs image optimization as it can save up to 23.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.3 MB
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 1.3 MB or 77% of the original size.
Potential reduce by 401.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. Legemiddelverket.no needs all CSS files to be minified and compressed as it can save up to 401.5 kB or 88% of the original size.
Number of requests can be reduced by 40 (74%)
54
14
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Legemiddelverket. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
legemiddelverket.no
372 ms
default.aspx
2947 ms
SitesterSurvey_1890.js
246 ms
controls.css
254 ms
Menu.css
253 ms
page-layouts-21.css
256 ms
search.css
256 ms
corev4.css
507 ms
ribbonmarkupstyles.v1.3.css
371 ms
style.v1.6.css
377 ms
nivo-slider.css
396 ms
jquery-1.7.1.min.js
396 ms
jquery.placeholder.min.js
493 ms
jquery-1.4.2.min.js
499 ms
selectivizr.js
500 ms
main.v1.1.js
500 ms
modernizr.h5bp.custom.v1.1.js
611 ms
WebResource.axd
130 ms
RibbonVisibility_collapsed.js
134 ms
ScriptResource.axd
137 ms
blank.js
135 ms
jquery.nivo.slider.pack.js
140 ms
init.js
220 ms
spgridview.js
208 ms
ScriptResource.axd
212 ms
ScriptResource.axd
213 ms
bg-circles.png
135 ms
bg-circles-right.png
133 ms
bg-gradient.png
132 ms
fgimg.png
132 ms
gosearch15.png
128 ms
Legemiddelsamstemming-forsidebanner2.jpg
135 ms
bjerkerakler_forsidebanner.jpg
374 ms
eldre2_forsidebanner.jpg
378 ms
P-piller2_725x196pix.jpg
379 ms
legemiddelovervaking_235x62px.jpg
267 ms
rss.gif
266 ms
bgximg.png
224 ms
logo.png
339 ms
button-search.png
339 ms
loading.gif
334 ms
linkbullet9-right.png
440 ms
linkbullet9-white-right.png
443 ms
icon-facebook.png
444 ms
icon-twitter.png
447 ms
ga.js
30 ms
core.js
563 ms
sp.core.js
422 ms
ScriptResx.ashx
534 ms
cui.js
802 ms
__utm.gif
14 ms
sp.ui.dialog.js
129 ms
mediaplayer.js
128 ms
search.js
131 ms
sp.runtime.js
135 ms
sp.js
527 ms
legemiddelverket.no accessibility score
legemiddelverket.no 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
Missing source maps for large first-party JavaScript
legemiddelverket.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Legemiddelverket.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 English language. Our system also found out that Legemiddelverket.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.
legemiddelverket.no
Open Graph data is detected on the main page of Legemiddelverket. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: