Tools & Wizards About Us

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

schwinge.com

Startseite - Datenschutz und Internetagentur SCHWINGE in Stuttgart

Page Load Speed

5.4 sec in total

First Response

341 ms

Resources Loaded

4.8 sec

Page Rendered

270 ms

About Website

Visit schwinge.com now to see the best up-to-date SCHWINGE content and also check out these interesting facts you probably never knew about schwinge.com

SCHWINGE. realisiert Projekte als Full-Service Internetagentur, IT-Management Dienstleister und Spezialist für Datenschutz im Herzen von Stuttgart.

Visit schwinge.com

Key Findings

We analyzed Schwinge.com page load time and found that the first response time was 341 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

schwinge.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

schwinge.com

341 ms

schwinge.com

431 ms

www.schwinge.com

1600 ms

grid.css

209 ms

base.css

315 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 98% of them (114 requests) were addressed to the original Schwinge.com, 2% (2 requests) were made to Stats.schwinge.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Schwinge.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (47%)

Content Size

2.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Schwinge.com main page is 2.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. 65% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 110.2 kB

  • Original 130.6 kB
  • After minification 128.9 kB
  • After compression 20.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 110.2 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 6.7 kB

  • Original 1.0 MB
  • After minification 1.0 MB

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. SCHWINGE images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 419.9 kB

  • Original 572.6 kB
  • After minification 492.2 kB
  • After compression 152.7 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 419.9 kB or 73% of the original size.

CSS Optimization

-86%

Potential reduce by 624.5 kB

  • Original 730.1 kB
  • After minification 644.5 kB
  • After compression 105.7 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. Schwinge.com needs all CSS files to be minified and compressed as it can save up to 624.5 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 72 (69%)

Requests Now

104

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

schwinge.com accessibility score

84

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[role]s are not contained by their required parent element

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

schwinge.com 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

schwinge.com SEO score

97

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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 Schwinge.com 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 Schwinge.com 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

Open Graph data is detected on the main page of SCHWINGE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: