7.7 sec in total
428 ms
6.5 sec
754 ms
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.deWe analyzed Spitzner.de page load time and found that the first response time was 428 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
spitzner.de performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value9.8 s
0/100
25%
Value23.2 s
0/100
10%
Value15,630 ms
0/100
30%
Value0.002
100/100
15%
Value43.8 s
0/100
10%
428 ms
420 ms
814 ms
57 ms
70 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 86% of them (69 requests) were addressed to the original Spitzner.de, 5% (4 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Spitzner.de.
Page size can be reduced by 3.1 MB (34%)
9.0 MB
5.9 MB
In fact, the total size of Spitzner.de main page is 9.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. 55% of websites need less resources to load. Images take 7.2 MB which makes up the majority of the site volume.
Potential reduce by 157.9 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 64.7 kB, which is 38% 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 157.9 kB or 92% of the original size.
Potential reduce by 1.6 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. Obviously, Spitzner needs image optimization as it can save up to 1.6 MB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 693.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 693.4 kB or 77% of the original size.
Potential reduce by 613.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. Spitzner.de needs all CSS files to be minified and compressed as it can save up to 613.6 kB or 88% of the original size.
Number of requests can be reduced by 36 (51%)
71
35
The browser has sent 71 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 33 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
spitzner.de
428 ms
www.spitzner.de
420 ms
www.spitzner.de
814 ms
css
57 ms
css
70 ms
d61d08f8f96ec2ca24026c49b141379e.css
394 ms
217de4e58e9436b6009752bd1bbd3116.css
726 ms
prototype.js
765 ms
ccard.js
552 ms
validation.js
539 ms
builder.js
567 ms
effects.js
567 ms
dragdrop.js
637 ms
controls.js
658 ms
slider.js
663 ms
js.js
674 ms
form.js
761 ms
menu.js
781 ms
translate.js
782 ms
cookies.js
782 ms
jquery-1.11.2.min.js
824 ms
jquery-noconflict.js
837 ms
jquery.fancybox.js
842 ms
ajaxaddto.js
852 ms
owl.carousel.min.js
855 ms
product.js
865 ms
configurable.js
927 ms
calendar.js
1040 ms
calendar-setup.js
947 ms
jquery-migrate-1.0.0.js
953 ms
bootstrap.min.js
963 ms
jquery.swblog.js
978 ms
megamenu.js
1017 ms
bundle.js
1047 ms
sw_quickview.js
1059 ms
twitterfetcher.js
1059 ms
jquery.granada.js
1079 ms
waypoints.min.js
1116 ms
analytics.js
53 ms
logo.png
155 ms
ajax-loader.gif
154 ms
jan16_sport_zuhause_slider_links.png
971 ms
jan16_produkttipp.png
1062 ms
Kachel_rechts_DuschschaumEnergy.jpg
345 ms
jan16_be_a_unicorn.png
448 ms
duschschaum_lavendel_960x3058.png
540 ms
duschen_duschschaum_pure_man_2.png
640 ms
duschen_duschschaum_acaiyuzu_1_1.png
492 ms
duschen_duschschaum_creme_1.png
735 ms
duschen_duschschaum_inspiration_1.png
886 ms
sauna_saunaaufguss_saunamed_1.png
1118 ms
sauna_saunaaufguss_ingwer_limette_1.png
1219 ms
sauna_saunaaufguss_citrus_mint_1.png
1225 ms
saunaaufguss-zitronengras-basilikum-190ml_1.png
1461 ms
sauna_saunaaufguss_eukalyptus_1.png
1270 ms
geschenkset_creme_1.png
1266 ms
geschenkset_acai-yuzu_1_1.png
1220 ms
geschenkset_pureman_1.png
1412 ms
wohlfuehlset-creme_2015_1_1.png
1334 ms
wohlfuehlset-acaiyuzu_2015_2_1.png
1334 ms
duschen_duschschaum_energy_2.png
1468 ms
duschen_duschschaum_passion_1.png
1386 ms
sauna_saunaaufguss_alpenkrauter_1.png
1641 ms
sauna_saunaaufguss_latschenkiefer_1.png
1628 ms
sauna_saunaaufguss_eisminze_1.png
1674 ms
top-newsletter.png
1509 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
142 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
138 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
142 ms
granada-font.woff
1554 ms
PuwvqkdbcqU-fCZ9Ed-b7S3USBnSvpkopQaUR-2r7iU.ttf
127 ms
collect
99 ms
collect
159 ms
testimonial-1_2.jpg
1900 ms
ga-audiences
129 ms
jan16_maenner.jpg
3359 ms
icon-facebook.png
1412 ms
icon-youtube.png
1475 ms
X75E9C271BEF2D8E39118F8C13EDCCE72.js
773 ms
dfe98268dfeeb2c12982ee7c040cf471.css
108 ms
spitzner.de accessibility score
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
[role]s do not have all required [aria-*] attributes
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
spitzner.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
spitzner.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
DE
DE
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.
spitzner.de
Open Graph data is detected on the main page of Spitzner. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: