2.3 sec in total
306 ms
1 sec
917 ms
Visit spichtinger.net now to see the best up-to-date Spichtinger content and also check out these interesting facts you probably never knew about spichtinger.net
"Horizon, open science and all that"Daniel Spichtinger has been working on EU funded research projects since 2004. He has been involved "hands on" in proposal writing as well as dissemination of resea...
Visit spichtinger.netWe analyzed Spichtinger.net page load time and found that the first response time was 306 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
spichtinger.net performance score
name
value
score
weighting
Value2.2 s
78/100
10%
Value2.7 s
85/100
25%
Value2.9 s
95/100
10%
Value990 ms
28/100
30%
Value0
100/100
15%
Value3.4 s
93/100
10%
306 ms
184 ms
221 ms
280 ms
219 ms
Our browser made a total of 19 requests to load all elements on the main page. We found that 11% of them (2 requests) were addressed to the original Spichtinger.net, 84% (16 requests) were made to S.yimg.com and 5% (1 request) were made to Yui-s.yahooapis.com. The less responsive or slowest element that took the longest time to load (395 ms) relates to the external source S.yimg.com.
Page size can be reduced by 19.3 kB (14%)
136.4 kB
117.0 kB
In fact, the total size of Spichtinger.net main page is 136.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Javascripts take 55.7 kB which makes up the majority of the site volume.
Potential reduce by 16.3 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 16.3 kB or 73% of the original size.
Potential reduce by 1.6 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. Spichtinger images are well optimized though.
Potential reduce by 433 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 1.0 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. Spichtinger.net needs all CSS files to be minified and compressed as it can save up to 1.0 kB or 15% of the original size.
We found no issues to fix!
17
17
The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Spichtinger. According to our analytics all requests are already optimized.
spichtinger.net
306 ms
mc_global.195798.css
184 ms
theme.css
221 ms
mc_yss_extensions.195289.css
280 ms
utilities.js
219 ms
container_2.1.0.js
317 ms
mc_yss_extensions.195289.js
395 ms
DS-EFA-small.253114413_std.jpg
315 ms
html.jpg
279 ms
doc.jpg
271 ms
hd.jpg
270 ms
hcontent.jpg
270 ms
spacer.gif
256 ms
bd.jpg
256 ms
ft.jpg
255 ms
analytics-social.gif
276 ms
fcontent.jpg
275 ms
player-min.js
16 ms
zoom_sm_1.0.gif
16 ms
spichtinger.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
spichtinger.net 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
Browser errors were logged to the console
spichtinger.net SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spichtinger.net 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 Spichtinger.net 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.
spichtinger.net
Open Graph description is not detected on the main page of Spichtinger. 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: