3.5 sec in total
412 ms
2.9 sec
215 ms
Visit fmri.at now to see the best up-to-date FMRI content and also check out these interesting facts you probably never knew about fmri.at
Brain research group at the MR Centre of Excellence, Medical University of Vienna using functional magnetic resonance imaging (fMRI) & TMS brain stimulation
Visit fmri.atWe analyzed Fmri.at page load time and found that the first response time was 412 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
fmri.at performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value13.0 s
0/100
25%
Value8.8 s
16/100
10%
Value240 ms
85/100
30%
Value0.621
10/100
15%
Value11.1 s
20/100
10%
412 ms
1539 ms
191 ms
27 ms
297 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 60% of them (21 requests) were addressed to the original Fmri.at, 11% (4 requests) were made to Tmsfmri.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Fmri.at.
Page size can be reduced by 527.8 kB (36%)
1.5 MB
929.0 kB
In fact, the total size of Fmri.at main page is 1.5 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. 35% of websites need less resources to load. Images take 749.0 kB which makes up the majority of the site volume.
Potential reduce by 33.7 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 33.7 kB or 74% of the original size.
Potential reduce by 17.2 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. FMRI images are well optimized though.
Potential reduce by 324.8 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 324.8 kB or 67% of the original size.
Potential reduce by 152.2 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. Fmri.at needs all CSS files to be minified and compressed as it can save up to 152.2 kB or 87% of the original size.
Number of requests can be reduced by 14 (45%)
31
17
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FMRI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
fmri.at
412 ms
www.fmri.at
1539 ms
style.css
191 ms
jquery.min.js
27 ms
jquery.aw-showcase.js
297 ms
style.min.css
394 ms
classic-themes.min.css
202 ms
css
22 ms
style.css
295 ms
jquery.min.js
400 ms
jquery-migrate.min.js
290 ms
fac9b2244ede589d98478de6fdc176ed.css
414 ms
css
34 ms
navigation.js
388 ms
b645babe967fac6dea8611a2f8b3e16d.js
694 ms
wp-emoji-release.min.js
110 ms
analytics.js
18 ms
TMSfMRIm1_neuroimage-01.png
623 ms
1-s2.0-S1053811920300720-gr6.jpg
132 ms
top_bg.png
100 ms
logo_meduni.png
101 ms
fMRIat_350px.png
100 ms
mainnav_bg.png
101 ms
mainnav_active_bg.png
114 ms
bulb-1.png
200 ms
HBM2015_AllanHummer_pRFEyetrackerCorrection_final-300x204.jpg
202 ms
21558644_10155469112230751_368117396772843621_n-e1506421071355-300x247.jpg
202 ms
hummer_retinotop_neuroimage-011.png
622 ms
sad09_cerebcort.png
525 ms
aha_cream-01.png
623 ms
font
41 ms
collect
43 ms
font
25 ms
collect
37 ms
js
66 ms
fmri.at 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
Image elements do not have [alt] attributes
fmri.at best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
fmri.at SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fmri.at 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 Fmri.at 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.
fmri.at
Open Graph data is detected on the main page of FMRI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: