4.1 sec in total
333 ms
3.3 sec
391 ms
Welcome to sars.no homepage info - get ready to check Sars best content right away, or after learning these important things about sars.no
The Michael Sars Centre at the University of Bergen, is an international community of scientists using advanced technologies to study the unique molecular and cellular biology of marine organisms in a...
Visit sars.noWe analyzed Sars.no page load time and found that the first response time was 333 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
sars.no performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value8.8 s
1/100
25%
Value8.5 s
17/100
10%
Value1,000 ms
27/100
30%
Value0.104
89/100
15%
Value15.9 s
6/100
10%
333 ms
120 ms
110 ms
218 ms
326 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Sars.no, 54% (38 requests) were made to Uib.no and 25% (18 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Uib.no.
Page size can be reduced by 146.4 kB (7%)
2.1 MB
2.0 MB
In fact, the total size of Sars.no main page is 2.1 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. 70% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 48.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 48.0 kB or 81% of the original size.
Potential reduce by 27.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. Sars images are well optimized though.
Potential reduce by 26.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 26.9 kB or 23% of the original size.
Potential reduce by 43.7 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. Sars.no needs all CSS files to be minified and compressed as it can save up to 43.7 kB or 21% of the original size.
Number of requests can be reduced by 46 (73%)
63
17
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sars. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
sars.no
333 ms
michaelsarscentre
120 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
110 ms
css_LzzNjvyQpSxyIbQ8CjQDdsJQqRnd8fNiXTcMlXTqIVE.css
218 ms
css_hFjMpgojz5tLIvTCOXkG5jneFLTaWNX_hakVb3yaMeE.css
326 ms
css_3OmOXy6QprOkr48nRgtrypyE0V5QWVpjdpRaJc2Wx-o.css
903 ms
jquery.min.js
541 ms
jquery-extend-3.4.0.js
390 ms
jquery-html-prefilter-3.5.0-backport.js
462 ms
jquery.once.js
491 ms
drupal.js
525 ms
jquery_browser.js
558 ms
form-single-submit.js
591 ms
form.js
625 ms
entityreference.js
657 ms
jquery.colorbox-min.js
691 ms
purify.min.js
726 ms
colorbox.js
757 ms
colorbox_style.js
792 ms
colorbox_inline.js
823 ms
googleanalytics.js
857 ms
mobile_menu.js
889 ms
sortable.js
941 ms
uib_search.js
958 ms
w3.js
989 ms
field_group.js
1026 ms
yfr2tzw.js
137 ms
widgets.js
24 ms
picturefill.min.js
1108 ms
picture.min.js
1108 ms
gtm.js
69 ms
analytics.js
20 ms
linkid.js
5 ms
collect
14 ms
logo.svg
287 ms
banner_website.png
650 ms
notochord_picture.jpg
317 ms
4i3a4637_tiny.png
648 ms
4i3a4615_web.jpg
353 ms
4i3a5096_final.jpg
286 ms
growth_juveniles_adults_rectangle_small.png
386 ms
img_0708_0.jpeg
421 ms
d
145 ms
d
191 ms
d
168 ms
d
168 ms
d
191 ms
d
192 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
27 ms
banner_website.png
665 ms
bg_tab.png
269 ms
settings
97 ms
p.gif
22 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
3 ms
MSarsCentre
141 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
4 ms
runtime-b1c52fd0a13ead5fcf6b.js
21 ms
modules-96ebc7ac3ad66d681a3d.js
26 ms
main-babd9234dc048fb47339.js
24 ms
_app-a9c9f1a99e4414675fb1.js
26 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
25 ms
_buildManifest.js
24 ms
_ssgManifest.js
25 ms
8526.0c32a8f0cfc5749221a3.js
12 ms
1755.07a49c40b12af4f75780.js
12 ms
8283.f3e5048cca7cef5eed7f.js
4 ms
3077.44bfeb00af01bc4020f6.js
8 ms
1362.42d432e02f7980bca032.js
7 ms
4956.c4e51ef593974b9db0bb.js
22 ms
5893.d500bd2a89ded806aa73.js
8 ms
css_VVIwC6Oh2S6Yoj-dlw07AnQN33wARXuRRIf8pwRiu2U.css
110 ms
sars.no accessibility score
sars.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
Page has valid source maps
sars.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 uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sars.no can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Sars.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.
sars.no
Open Graph description is not detected on the main page of Sars. 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: