Tools & Wizards About Us
spichtinger.net screenshot

Report Summary

  • 97

    Performance

    Renders faster than
    94% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

spichtinger.net

Mag. Daniel Spichtinger, M.A - selbständiger PR Berater, spezialisiert auf offene Wissenschaft und Wissenschaftspolitik in der Europäischen Union / in...

Page Load Speed

372 ms in total

First Response

30 ms

Resources Loaded

202 ms

Page Rendered

140 ms

spichtinger.net screenshot

About Website

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.net

Key Findings

We analyzed Spichtinger.net page load time and found that the first response time was 30 ms and then it took 342 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

spichtinger.net performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

93/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.7 s

100/100

10%

Network Requests Diagram

spichtinger.net

30 ms

mc_global.195798.css

29 ms

theme.css

105 ms

turbify_ss_extensions_1675321208.js

32 ms

turbify_ss_extensions_1675321208.js

31 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 13% of them (2 requests) were addressed to the original Spichtinger.net, 53% (8 requests) were made to Turbifycdn.com and 33% (5 requests) were made to S.turbifycdn.com. The less responsive or slowest element that took the longest time to load (105 ms) relates to the external source S.turbifycdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 18.3 kB (11%)

Content Size

164.6 kB

After Optimization

146.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Spichtinger.net main page is 164.6 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. 15% of websites need less resources to load. Javascripts take 86.7 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 15.4 kB

  • Original 21.1 kB
  • After minification 21.1 kB
  • After compression 5.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 15.4 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 1.6 kB

  • Original 51.3 kB
  • After minification 49.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. Spichtinger images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 380 B

  • Original 86.7 kB
  • After minification 86.7 kB
  • After compression 86.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-17%

Potential reduce by 943 B

  • Original 5.5 kB
  • After minification 5.5 kB
  • After compression 4.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. Spichtinger.net needs all CSS files to be minified and compressed as it can save up to 943 B or 17% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

14

After Optimization

14

  • Images
  • JavaScript
  • CSS

The browser has sent 14 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.

Network Requests Diagram

spichtinger.net

spichtinger.net

30 ms

mc_global.195798.css

mc_global.195798.css

29 ms

theme.css

theme.css

105 ms

turbify_ss_extensions_1675321208.js

turbify_ss_extensions_1675321208.js

32 ms

turbify_ss_extensions_1675321208.js

turbify_ss_extensions_1675321208.js

31 ms

html.jpg

html.jpg

18 ms

DS-EFA-small.253114413_std.jpg

DS-EFA-small.253114413_std.jpg

6 ms

spacer.gif

spacer.gif

3 ms

doc.jpg

doc.jpg

14 ms

hd.jpg

hd.jpg

17 ms

hcontent.jpg

hcontent.jpg

16 ms

bd.jpg

bd.jpg

17 ms

ft.jpg

ft.jpg

16 ms

analytics-social.gif

analytics-social.gif

16 ms

fcontent.jpg

fcontent.jpg

17 ms

Accessibility Review

spichtinger.net accessibility score

88

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

spichtinger.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

spichtinger.net SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: