Tools & Wizards About Us
ssoar.info screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

ssoar.info

Page Load Speed

2.6 sec in total

First Response

238 ms

Resources Loaded

2.2 sec

Page Rendered

120 ms

ssoar.info screenshot

About Website

Welcome to ssoar.info homepage info - get ready to check Ssoar best content for Germany right away, or after learning these important things about ssoar.info

GESIS Leibniz Institut für Sozialwissenschaften

Visit ssoar.info

Key Findings

We analyzed Ssoar.info page load time and found that the first response time was 238 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

ssoar.info performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.047

99/100

15%

TTI (Time to Interactive)

Value9.0 s

34/100

10%

Network Requests Diagram

ssoar.info

238 ms

www.ssoar.info

576 ms

layout_3col_standard.css

110 ms

content_dbclear.css

207 ms

Hyphenator.js

210 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 75% of them (21 requests) were addressed to the original Ssoar.info, 11% (3 requests) were made to S7.addthis.com and 4% (1 request) were made to Web.gesis.org. The less responsive or slowest element that took the longest time to load (576 ms) belongs to the original domain Ssoar.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 313.6 kB (64%)

Content Size

488.8 kB

After Optimization

175.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ssoar.info main page is 488.8 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. 25% of websites need less resources to load. Javascripts take 357.5 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 35.6 kB

  • Original 52.7 kB
  • After minification 51.5 kB
  • After compression 17.1 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 35.6 kB or 67% of the original size.

Image Optimization

-8%

Potential reduce by 1.8 kB

  • Original 23.6 kB
  • After minification 21.9 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. Ssoar images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 230.3 kB

  • Original 357.5 kB
  • After minification 356.6 kB
  • After compression 127.2 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 230.3 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 45.9 kB

  • Original 54.9 kB
  • After minification 36.3 kB
  • After compression 9.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. Ssoar.info needs all CSS files to be minified and compressed as it can save up to 45.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (50%)

Requests Now

24

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ssoar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ssoar.info

ssoar.info

238 ms

www.ssoar.info

www.ssoar.info

576 ms

layout_3col_standard.css

layout_3col_standard.css

110 ms

content_dbclear.css

content_dbclear.css

207 ms

Hyphenator.js

Hyphenator.js

210 ms

javascript_a708894199.js

javascript_a708894199.js

213 ms

addthis_widget.js

addthis_widget.js

16 ms

slim_base.css

slim_base.css

109 ms

nav_ssoarbuttons.css

nav_ssoarbuttons.css

200 ms

nav_vlist.css

nav_vlist.css

399 ms

basemod.css

basemod.css

201 ms

content.css

content.css

216 ms

typo3-RTE.css

typo3-RTE.css

408 ms

lg-share-en.gif

lg-share-en.gif

9 ms

219f814921.png

219f814921.png

107 ms

content_client.gif

content_client.gif

109 ms

zlogo_monitor_2007_100.jpg

zlogo_monitor_2007_100.jpg

107 ms

RTEmagicC_feed-icon-14x14_de7fab.png.png

RTEmagicC_feed-icon-14x14_de7fab.png.png

105 ms

logo_gesis.png

logo_gesis.png

109 ms

logo_dfg.png

logo_dfg.png

112 ms

logo_oa.png

logo_oa.png

205 ms

t.js

t.js

498 ms

vvcnt.php

vvcnt.php

365 ms

cnt_js.php

cnt_js.php

267 ms

header.png

header.png

112 ms

content_client.gif

content_client.gif

112 ms

300lo.json

300lo.json

35 ms

sh.7c7179124ea24ac6ba46caac.html

sh.7c7179124ea24ac6ba46caac.html

26 ms

Accessibility Review

ssoar.info accessibility score

89

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.

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

ssoar.info best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

ssoar.info SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ssoar.info can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Ssoar.info 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

ssoar.info

Open Graph description is not detected on the main page of Ssoar. 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: