Tools & Wizards About Us

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

futurecandy.com

FUTURE CANDY | Die Agentur für erfolgreiche Innovationen

Page Load Speed

5.7 sec in total

First Response

321 ms

Resources Loaded

3.9 sec

Page Rendered

1.5 sec

About Website

Visit futurecandy.com now to see the best up-to-date FUTURE CANDY content for Germany and also check out these interesting facts you probably never knew about futurecandy.com

Wir sind FUTURE CANDY, die Agentur für erfolgreiche Innovationsprojekte! Wir helfen Ihnen Trends zu verstehen, Ideen zu entwickeln und Innovationen umzusetzen, FUTURE CANDY ist eine der führenden Inno...

Visit futurecandy.com

Key Findings

We analyzed Futurecandy.com page load time and found that the first response time was 321 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

futurecandy.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value1,940 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

Network Requests Diagram

futurecandy.com

321 ms

www.futurecandy.com

1005 ms

main.min.css

107 ms

style.min.css

287 ms

styles.css

308 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 81% of them (63 requests) were addressed to the original Futurecandy.com, 4% (3 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Secure.otto5loki.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Futurecandy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (9%)

Content Size

12.1 MB

After Optimization

11.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Futurecandy.com main page is 12.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. 70% of websites need less resources to load. Images take 11.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 74.6 kB

  • Original 90.9 kB
  • After minification 69.7 kB
  • After compression 16.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. This page needs HTML code to be minified as it can gain 21.2 kB, which is 23% 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 74.6 kB or 82% of the original size.

Image Optimization

-9%

Potential reduce by 1.0 MB

  • Original 11.7 MB
  • After minification 10.7 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. FUTURE CANDY images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 35.2 kB

  • Original 277.0 kB
  • After minification 275.5 kB
  • After compression 241.8 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 35.2 kB or 13% of the original size.

CSS Optimization

-26%

Potential reduce by 13.8 kB

  • Original 52.2 kB
  • After minification 52.2 kB
  • After compression 38.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. Futurecandy.com needs all CSS files to be minified and compressed as it can save up to 13.8 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (61%)

Requests Now

71

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FUTURE 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 30 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

futurecandy.com accessibility score

74

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

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

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

Low

No form fields have multiple labels

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

futurecandy.com best practices score

75

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

Browser errors were logged to the console

SEO Factors

futurecandy.com SEO score

84

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Futurecandy.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Futurecandy.com 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 data is detected on the main page of FUTURE CANDY. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: