6.9 sec in total
400 ms
6 sec
582 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 400 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
sars.no performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value6.5 s
8/100
25%
Value29.7 s
0/100
10%
Value37,610 ms
0/100
30%
Value0.091
92/100
15%
Value50.8 s
0/100
10%
400 ms
929 ms
122 ms
238 ms
356 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Sars.no, 55% (47 requests) were made to Uib.no and 13% (11 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Uib.no.
Page size can be reduced by 191.2 kB (6%)
3.2 MB
3.0 MB
In fact, the total size of Sars.no main page is 3.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 46.4 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 46.4 kB or 80% of the original size.
Potential reduce by 47.1 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 34.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 34.1 kB or 33% of the original size.
Potential reduce by 63.6 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 63.6 kB or 28% of the original size.
Number of requests can be reduced by 58 (74%)
78
20
The browser has sent 78 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 36 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
sars.no
400 ms
sarscentre
929 ms
system.base.css
122 ms
system.menus.css
238 ms
system.messages.css
356 ms
system.theme.css
390 ms
date.css
422 ms
datepicker.1.7.css
520 ms
field.css
487 ms
node.css
453 ms
picture_wysiwyg.css
554 ms
user.css
586 ms
views.css
618 ms
colorbox_style.css
654 ms
ctools.css
685 ms
panels.css
720 ms
locale.css
751 ms
field_collection.theme.css
783 ms
style.css
1396 ms
print.css
852 ms
jquery.min.js
1002 ms
jquery-extend-3.4.0.js
917 ms
jquery-html-prefilter-3.5.0-backport.js
949 ms
jquery.once.js
981 ms
drupal.js
1011 ms
form.js
1044 ms
jquery.colorbox-min.js
1078 ms
colorbox.js
1100 ms
colorbox_style.js
1133 ms
colorbox_inline.js
1163 ms
googleanalytics.js
1180 ms
mobile_menu.js
1207 ms
sortable.js
1245 ms
uib_search.js
1268 ms
w3.js
1300 ms
field_group.js
1332 ms
yfr2tzw.js
35 ms
widgets.js
126 ms
picturefill.min.js
1739 ms
picture.min.js
1739 ms
gtm.js
359 ms
analytics.js
761 ms
logo.svg
729 ms
linkedin.jpg
987 ms
nematostella_spawning-ii-landscape2sm_0.jpg
727 ms
skjermbilde_2022-05-11_kl._14.27.59.png
1144 ms
athira-sm.jpg
1373 ms
6d2a3173_copy4.png
1349 ms
1.2_0.png
1289 ms
6d2a0075_copy.jpg
912 ms
d
514 ms
d
525 ms
d
526 ms
d
517 ms
widget_iframe.7dae38096d06923d683a2a807172322a.html
287 ms
linkedin.jpg
1046 ms
bg_tab.png
599 ms
d
117 ms
d
118 ms
fbevents.js
228 ms
scevent.min.js
297 ms
js
275 ms
settings
355 ms
linkid.js
59 ms
132351337292922
226 ms
p.gif
215 ms
collect
59 ms
collect
166 ms
collect
70 ms
collect
58 ms
collect
139 ms
horizon_timeline.a7991bb824d62c8d5038ddd875db8389.js
106 ms
embeds
102 ms
collect
125 ms
ga-audiences
64 ms
ga-audiences
54 ms
ga-audiences
39 ms
sars_centre
642 ms
polyfills-57d3feabe8bfd4ee389c.js
25 ms
runtime-eb61dff4a84b8f906e6b.js
53 ms
modules.c7def0268c66f6a548ed.js
102 ms
main-e9db78f5e7b3d83edd5e.js
94 ms
_app-446fb4a338b215deec8c.js
95 ms
%5BscreenName%5D-c8b4c96951cf24f547b4.js
102 ms
_buildManifest.js
107 ms
_ssgManifest.js
108 ms
sars.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
Links do not have a discernible name
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
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: