Tools & Wizards About Us
candy.ae screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% 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

  • 92

    SEO

    Google-friendlier than
    74% of websites

candy.ae

Official website: Home appliances | Candy

Page Load Speed

3.3 sec in total

First Response

154 ms

Resources Loaded

3 sec

Page Rendered

230 ms

candy.ae screenshot

About Website

Visit candy.ae now to see the best up-to-date Candy content and also check out these interesting facts you probably never knew about candy.ae

Candy official website: Sale of washing machines, refrigerators and many other appliances. Assistance service and sale of accessories and spare parts.

Visit candy.ae

Key Findings

We analyzed Candy.ae page load time and found that the first response time was 154 ms and then it took 3.2 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.ae performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

candy.ae

154 ms

candy.ae

283 ms

www.candy.ae

337 ms

468 ms

style.css

403 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 849.7 kB (80%)

Content Size

1.1 MB

After Optimization

210.5 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Candy.ae main page is 1.1 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. HTML takes 572.6 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 505.3 kB

  • Original 572.6 kB
  • After minification 572.2 kB
  • After compression 67.3 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 505.3 kB or 88% of the original size.

JavaScript Optimization

-0%

Potential reduce by 327 B

  • Original 108.7 kB
  • After minification 108.7 kB
  • After compression 108.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. 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.ae 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 6 (75%)

Requests Now

8

After Optimization

2

  • JavaScript
  • CSS

The browser has sent 8 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 4 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.ae

candy.ae

154 ms

candy.ae

candy.ae

283 ms

www.candy.ae

www.candy.ae

337 ms

468 ms

style.css

style.css

403 ms

style-gr.css

style-gr.css

344 ms

custom-styles.css

custom-styles.css

609 ms

webpack-runtime-1c0a00c54bfb981bdc56.js

webpack-runtime-1c0a00c54bfb981bdc56.js

486 ms

framework-417bf7382a8b74085ed2.js

framework-417bf7382a8b74085ed2.js

630 ms

app-8140cc14eacb4a3db0e4.js

app-8140cc14eacb4a3db0e4.js

631 ms

gtm.js

gtm.js

135 ms

css2

css2

41 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4W61C4E.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4W61C4E.ttf

17 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4bC1C4E.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4bC1C4E.ttf

23 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC0C4E.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC0C4E.ttf

46 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC1C4E.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4TC1C4E.ttf

51 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4QK1C4E.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4QK1C4E.ttf

52 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4e6yC4E.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4e6yC4E.ttf

52 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4deyC4E.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4deyC4E.ttf

53 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4bCyC4E.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4bCyC4E.ttf

53 ms

QGYyz_MVcBeNP4NjuGObqx1XmO1I4ZmyC4E.ttf

QGYyz_MVcBeNP4NjuGObqx1XmO1I4ZmyC4E.ttf

53 ms

candyIcons.ttf

candyIcons.ttf

295 ms

candyIcons-96057565c301c80ff9b98e5d807e9209.ttf

candyIcons-96057565c301c80ff9b98e5d807e9209.ttf

458 ms

candyIcons.woff

candyIcons.woff

292 ms

candyIcons.svg

candyIcons.svg

317 ms

Accessibility Review

candy.ae 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.ae 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.ae SEO score

92

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

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

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: