7 sec in total
200 ms
3.6 sec
3.2 sec
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.comWe analyzed Futurecandy.com page load time and found that the first response time was 200 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
futurecandy.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value12.5 s
0/100
25%
Value9.2 s
13/100
10%
Value470 ms
61/100
30%
Value0.001
100/100
15%
Value14.9 s
8/100
10%
200 ms
762 ms
102 ms
201 ms
301 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 68% of them (50 requests) were addressed to the original Futurecandy.com, 7% (5 requests) were made to Google.com and 4% (3 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Futurecandy.com.
Page size can be reduced by 939.1 kB (10%)
9.4 MB
8.5 MB
In fact, the total size of Futurecandy.com main page is 9.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 9.1 MB which makes up the majority of the site volume.
Potential reduce by 65.5 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 19.8 kB, which is 25% 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 65.5 kB or 83% of the original size.
Potential reduce by 866.0 kB
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.
Potential reduce by 5.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. This website has mostly compressed JavaScripts.
Potential reduce by 1.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. Futurecandy.com has all CSS files already compressed.
Number of requests can be reduced by 37 (56%)
66
29
The browser has sent 66 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 26 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
futurecandy.com
200 ms
www.futurecandy.com
762 ms
main.min.css
102 ms
style.min.css
201 ms
styles.css
301 ms
cookie-law-info-public.css
288 ms
cookie-law-info-gdpr.css
293 ms
jquery.min.js
402 ms
jquery-migrate.min.js
303 ms
cookie-law-info-public.js
316 ms
157767.js
60 ms
api.js
31 ms
app.min.js
581 ms
track.js
16 ms
yikes-inc-easy-mailchimp-extender-public.min.css
389 ms
cookie-law-info-table.css
521 ms
index.js
521 ms
index.js
522 ms
yikes-mc-ajax-forms.min.js
524 ms
form-submission-helpers.min.js
524 ms
65ba9fdf41816db7b48cce4d6.js
141 ms
bg.png
378 ms
cropped-logo_big.png
214 ms
futurecandy.jpg
577 ms
travel.png
485 ms
keynote.png
291 ms
events_teaser.png
239 ms
tech-flat_teaser.png
287 ms
reports.png
327 ms
inspiration-workshops_teaser.png
387 ms
consulting_teaser.png
425 ms
box_shadow.png
433 ms
Swisscom.jpg
860 ms
Unbenannt-e1643716243146.png
1294 ms
New-Project-1.png
1009 ms
Spatial-Oculus-Quest-screenshot-e1624375379110.png
1125 ms
goodyear-scaled-e1624352271906.jpg
1057 ms
WeChat-Image_20210812160514-scaled-e1628777237536.jpg
1004 ms
IFA-SHIFT-2020.jpg
1063 ms
newsletter.jpg
1125 ms
send.png
1112 ms
Team-scaled.jpg
1635 ms
LinkedIn.svg
1162 ms
instagram.svg
1207 ms
XING.svg
1222 ms
facebook.svg
1225 ms
spotify.svg
1260 ms
youtube.svg
1306 ms
logo-cookieyes.svg
1323 ms
GT-America-Standard-Regular.woff
1270 ms
GT-America-Standard-Medium.woff
1387 ms
GT-America-Standard-Light.woff
1461 ms
GT-America-Standard-Thin.ttf
1461 ms
GT-America-Standard-Bold.woff
1461 ms
embed.js
53 ms
158 ms
gtm.js
108 ms
157767.js
9 ms
fbevents.js
50 ms
api.js
26 ms
recaptcha__en.js
115 ms
track.js
14 ms
735275410390423
103 ms
analytics.js
183 ms
conversion_async.js
183 ms
loader.js
54 ms
js
59 ms
call-tracking_7.js
123 ms
collect
44 ms
52 ms
collect
21 ms
wcm
18 ms
ga-audiences
18 ms
21 ms
futurecandy.com 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
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
Buttons do not have an accessible name
No form fields have multiple labels
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
futurecandy.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
futurecandy.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
DE
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.
futurecandy.com
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: