Tools & Wizards About Us
candy.de screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

candy.de

Geräteverkauf, Service und Ersatzteile Candy | Candy

Page Load Speed

3.8 sec in total

First Response

169 ms

Resources Loaded

2.9 sec

Page Rendered

723 ms

candy.de screenshot

About Website

Click here to check amazing Candy content for Germany. Otherwise, check out these important facts you probably never knew about candy.de

Offizieller Candy-Standort. Verkauf von Waschmaschinen, Kühlschränken und vielen anderen Geräten. Kundendienst und Verkauf von Zubehör und Ersatzteilen.

Visit candy.de

Key Findings

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

Performance Metrics

candy.de performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value690 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

candy.de

169 ms

candy.de

287 ms

www.candy.de

323 ms

428 ms

style.css

341 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 10% of them (3 requests) were addressed to the original Candy.de, 31% (9 requests) were made to Candy-home.com and 31% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (716 ms) relates to the external source Candy-home.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 956.9 kB (75%)

Content Size

1.3 MB

After Optimization

317.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Candy.de main page is 1.3 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. 40% of websites need less resources to load. HTML takes 688.0 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 612.8 kB

  • Original 688.0 kB
  • After minification 687.5 kB
  • After compression 75.2 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 612.8 kB or 89% of the original size.

JavaScript Optimization

-0%

Potential reduce by 103 B

  • Original 207.3 kB
  • After minification 207.3 kB
  • After compression 207.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. This website has mostly compressed JavaScripts.

CSS Optimization

-91%

Potential reduce by 344.0 kB

  • Original 378.8 kB
  • After minification 378.0 kB
  • After compression 34.8 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. Candy.de needs all CSS files to be minified and compressed as it can save up to 344.0 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (75%)

Requests Now

12

After Optimization

3

  • AJAX
  • JavaScript
  • CSS

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

Network Requests Diagram

candy.de

candy.de

169 ms

candy.de

candy.de

287 ms

www.candy.de

www.candy.de

323 ms

428 ms

style.css

style.css

341 ms

style-gr.css

style-gr.css

340 ms

custom-styles.css

custom-styles.css

592 ms

webpack-runtime-c1bf2cd59063bbb347cf.js

webpack-runtime-c1bf2cd59063bbb347cf.js

418 ms

framework-417bf7382a8b74085ed2.js

framework-417bf7382a8b74085ed2.js

716 ms

app-7bb645254e1db2c0d041.js

app-7bb645254e1db2c0d041.js

716 ms

gtm.js

gtm.js

105 ms

css2

css2

34 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4W61C4G-EiApg6U.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4W61C4G-EiApg6U.ttf

84 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4bC1C4G-EiApg6U.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4bC1C4G-EiApg6U.ttf

127 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC0C4G-EiApg6U.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC0C4G-EiApg6U.ttf

168 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC1C4G-EiApg6U.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC1C4G-EiApg6U.ttf

183 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4QK1C4G-EiApg6U.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4QK1C4G-EiApg6U.ttf

184 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4e6yC4G-EiApg6U.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4e6yC4G-EiApg6U.ttf

183 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4deyC4G-EiApg6U.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4deyC4G-EiApg6U.ttf

186 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4bCyC4G-EiApg6U.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4bCyC4G-EiApg6U.ttf

182 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4ZmyC4G-EiApg6U.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4ZmyC4G-EiApg6U.ttf

234 ms

candyIcons.ttf

candyIcons.ttf

283 ms

candyIcons-96057565c301c80ff9b98e5d807e9209.ttf

candyIcons-96057565c301c80ff9b98e5d807e9209.ttf

402 ms

otSDKStub.js

otSDKStub.js

37 ms

2ce19c6d-f3f1-4333-a8d6-8c0c8403f6a0.json

2ce19c6d-f3f1-4333-a8d6-8c0c8403f6a0.json

54 ms

location

location

58 ms

otBannerSdk.js

otBannerSdk.js

48 ms

candyIcons.woff

candyIcons.woff

297 ms

candyIcons.svg

candyIcons.svg

292 ms

Accessibility Review

candy.de accessibility score

96

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

Links do not have a discernible name

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

candy.de SEO score

98

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

candy.de

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