Tools & Wizards About Us

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

spitzner.de

Spitzner Duschschäume, Saunaaufgüsse, Badezusätze und Wellnessprodukte im Spitzner Onlineshop.

Page Load Speed

12.6 sec in total

First Response

325 ms

Resources Loaded

11.1 sec

Page Rendered

1.2 sec

About Website

Visit spitzner.de now to see the best up-to-date Spitzner content for Germany and also check out these interesting facts you probably never knew about spitzner.de

Pflegeprodukte für jeden Geschmack. Jetzt im Spitzner Shop bestellen! Kostenlose Hotline · Nachhaltige Pflege · Hohe Ergiebigkeit · Dermatologisch getestet

Visit spitzner.de

Key Findings

We analyzed Spitzner.de page load time and found that the first response time was 325 ms and then it took 12.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

spitzner.de performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.9 s

0/100

25%

SI (Speed Index)

Value32.9 s

0/100

10%

TBT (Total Blocking Time)

Value2,390 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.141

78/100

15%

TTI (Time to Interactive)

Value71.9 s

0/100

10%

Network Requests Diagram

spitzner.de

325 ms

www.spitzner.de

1024 ms

loader.js

22 ms

calendar.min.css

216 ms

owl.carousel.min.css

326 ms

Our browser made a total of 348 requests to load all elements on the main page. We found that 94% of them (328 requests) were addressed to the original Spitzner.de, 1% (5 requests) were made to Fonts.gstatic.com and 1% (3 requests) were made to App.usercentrics.eu. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Spitzner.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.9 MB (22%)

Content Size

22.0 MB

After Optimization

17.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Spitzner.de main page is 22.0 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. Only a small number of websites need less resources to load. Images take 17.0 MB which makes up the majority of the site volume.

HTML Optimization

-94%

Potential reduce by 941.6 kB

  • Original 999.2 kB
  • After minification 742.5 kB
  • After compression 57.6 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 256.6 kB, which is 26% 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 941.6 kB or 94% of the original size.

Image Optimization

-5%

Potential reduce by 834.4 kB

  • Original 17.0 MB
  • After minification 16.2 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. Spitzner images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 2.1 MB

  • Original 2.8 MB
  • After minification 2.0 MB
  • After compression 697.4 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 2.1 MB or 75% of the original size.

CSS Optimization

-84%

Potential reduce by 1.0 MB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 191.4 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. Spitzner.de needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 194 (58%)

Requests Now

334

After Optimization

140

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

spitzner.de accessibility score

69

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 do not have all required [aria-*] attributes

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

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

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

Links do not have a discernible name

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

High

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

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

spitzner.de best practices score

83

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

Page has valid source maps

SEO Factors

spitzner.de SEO score

92

Search Engine Optimization Advices

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

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 Spitzner.de 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 Spitzner.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

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