Tools & Wizards About Us
swag.de screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

swag.de

Automotive Aftermarket Spare Parts for passenger Cars | SWAG

Page Load Speed

3.4 sec in total

First Response

317 ms

Resources Loaded

2.5 sec

Page Rendered

591 ms

swag.de screenshot

About Website

Welcome to swag.de homepage info - get ready to check SWAG best content for Russia right away, or after learning these important things about swag.de

Als einer der weltweiten Marktführer für PKW- und NKW-Ersatzteile setzt febi bilstein immer wieder neue Maßstäbe im freien Ersatzteilmarkt.

Visit swag.de

Key Findings

We analyzed Swag.de page load time and found that the first response time was 317 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.

Performance Metrics

swag.de performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

swag.de

317 ms

www.swag.de

607 ms

191c1a5209.css

107 ms

youtubevideo.css

213 ms

app.css

557 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 88% of them (22 requests) were addressed to the original Swag.de, 12% (3 requests) were made to Consent.cookiebot.com. The less responsive or slowest element that took the longest time to load (940 ms) belongs to the original domain Swag.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 63.8 kB (4%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Swag.de 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. 30% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 39.2 kB

  • Original 48.9 kB
  • After minification 40.6 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 8.3 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 39.2 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 6.5 kB

  • Original 1.4 MB
  • After minification 1.4 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. SWAG images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 18.1 kB

  • Original 49.0 kB
  • After minification 49.0 kB
  • After compression 30.9 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 18.1 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (23%)

Requests Now

22

After Optimization

17

  • Images
  • JavaScript
  • CSS

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SWAG. 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 as a result speed up the page load time.

Network Requests Diagram

swag.de

swag.de

317 ms

www.swag.de

www.swag.de

607 ms

191c1a5209.css

191c1a5209.css

107 ms

youtubevideo.css

youtubevideo.css

213 ms

app.css

app.css

557 ms

8992772695.js

8992772695.js

317 ms

uc.js

uc.js

19 ms

cd.js

cd.js

229 ms

app.js

app.js

753 ms

aac7c7eb32.js

aac7c7eb32.js

315 ms

logo-swag.svg

logo-swag.svg

107 ms

billstein-badge.svg

billstein-badge.svg

108 ms

partsfinder-logo-weiss.svg

partsfinder-logo-weiss.svg

110 ms

csm_SWAG_Home_Vital_Lines_becb89b8c0.png

csm_SWAG_Home_Vital_Lines_becb89b8c0.png

729 ms

csm_slider-flaggen_615766f9ef.jpg

csm_slider-flaggen_615766f9ef.jpg

314 ms

csm_youtube_376a9c201047e978a1344d6573965e8d_ed356f067c.jpg

csm_youtube_376a9c201047e978a1344d6573965e8d_ed356f067c.jpg

524 ms

csm_SWAG_Home_partsfinder_326b3dbb5c.png

csm_SWAG_Home_partsfinder_326b3dbb5c.png

940 ms

SWAG_Home_partsfinder_Logo.png

SWAG_Home_partsfinder_Logo.png

217 ms

SWAG_Home_Newsletter.png

SWAG_Home_Newsletter.png

243 ms

SWAG_Home_Messe.jpg

SWAG_Home_Messe.jpg

526 ms

cdreport.js

cdreport.js

214 ms

footer_bg_large.jpg

footer_bg_large.jpg

267 ms

billstein-badge-footer.svg

billstein-badge-footer.svg

338 ms

icomoon.ttf

icomoon.ttf

376 ms

SWAG_Home_Newsletter_Background.jpg

SWAG_Home_Newsletter_Background.jpg

311 ms

Accessibility Review

swag.de accessibility score

91

Accessibility Issues

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

Buttons do not have an accessible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

swag.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

swag.de SEO score

82

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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Swag.de 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 Swag.de 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

swag.de

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