5.7 sec in total
321 ms
3.9 sec
1.5 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 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.
futurecandy.com performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value6.6 s
8/100
25%
Value7.0 s
32/100
10%
Value1,940 ms
8/100
30%
Value0.019
100/100
15%
Value21.1 s
1/100
10%
321 ms
1005 ms
107 ms
287 ms
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 size can be reduced by 1.1 MB (9%)
12.1 MB
11.0 MB
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.
Potential reduce by 74.6 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.
Potential reduce by 1.0 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.
Potential reduce by 35.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. 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.
Potential reduce by 13.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 needs all CSS files to be minified and compressed as it can save up to 13.8 kB or 26% of the original size.
Number of requests can be reduced by 43 (61%)
71
28
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.
futurecandy.com
321 ms
www.futurecandy.com
1005 ms
main.min.css
107 ms
style.min.css
287 ms
styles.css
308 ms
wpa.css
310 ms
cookie-law-info-public.css
308 ms
cookie-law-info-gdpr.css
311 ms
jquery.min.js
413 ms
jquery-migrate.min.js
389 ms
cookie-law-info-public.js
513 ms
157767.js
45 ms
app.min.js
695 ms
track.js
30 ms
mediaelementplayer-legacy.min.css
424 ms
wp-mediaelement.min.css
424 ms
yikes-inc-easy-mailchimp-extender-public.min.css
492 ms
cookie-law-info-table.css
687 ms
hooks.min.js
688 ms
i18n.min.js
689 ms
index.js
693 ms
index.js
724 ms
wpa.js
724 ms
api.js
47 ms
wp-polyfill.min.js
809 ms
index.js
691 ms
mediaelement-and-player.min.js
902 ms
mediaelement-migrate.min.js
813 ms
wp-mediaelement.min.js
814 ms
vimeo.min.js
812 ms
yikes-mc-ajax-forms.min.js
811 ms
form-submission-helpers.min.js
871 ms
65ba9fdf41816db7b48cce4d6.js
226 ms
bg.png
682 ms
cropped-logo_big.png
369 ms
Webinar-5.png
762 ms
box_shadow.png
370 ms
FC_Gadget_Slider_2-1-scaled-2.jpg
546 ms
Beitragsbild-Indien.png
1180 ms
PXL_20240310_234335095-scaled.jpg
869 ms
travel.png
591 ms
events_teaser.png
681 ms
Die-FUTURE-CANDY-Speaker-halten-multimediale-Keynotes-zu-den-Top-Themen-der-Innovationsbranche.-Sowohl-klassisch-vor-Ort-als-auch-digital-via-Livestream-oder-im-virtuellen-Raum.-Sprich-uns-an-wir-5.png
726 ms
tech-flat_teaser.png
754 ms
Die-FUTURE-CANDY-Speaker-halten-multimediale-Keynotes-zu-den-Top-Themen-der-Innovationsbranche.-Sowohl-klassisch-vor-Ort-als-auch-digital-via-Livestream-oder-im-virtuellen-Raum.-Sprich-uns-an-wir-4.png
762 ms
Die-FUTURE-CANDY-Speaker-halten-multimediale-Keynotes-zu-den-Top-Themen-der-Innovationsbranche.-Sowohl-klassisch-vor-Ort-als-auch-digital-via-Livestream-oder-im-virtuellen-Raum.-Sprich-uns-an-wir.png
808 ms
a410f5fe-97bf-42d4-8eca-dacfe89b2ad4-e1702900534730.jpg
1064 ms
IMG_0908-scaled.jpeg
974 ms
Bild4-1-scaled-e1698659265830.jpg
1073 ms
Header-Magazin_3.png
1222 ms
Case-Header.png
1083 ms
MicrosoftTeams-image-2-5-scaled-e1682520345357.jpg
1095 ms
newsletter.jpg
1176 ms
send.png
1043 ms
FUTURE_CANDY_TEAM-15-1-e1712067869574.jpg
1052 ms
LinkedIn.svg
1064 ms
GT-America-Standard-Regular.woff
1144 ms
GT-America-Standard-Medium.woff
1152 ms
GT-America-Standard-Light.woff
1122 ms
GT-America-Standard-Thin.ttf
1179 ms
GT-America-Standard-Bold.woff
1180 ms
instagram.svg
1169 ms
embed.js
20 ms
XING.svg
1125 ms
facebook.svg
1132 ms
spotify.svg
1131 ms
youtube.svg
1132 ms
logo-cookieyes.svg
1143 ms
127 ms
js
62 ms
gtm.js
64 ms
gtm.js
66 ms
157767.js
6 ms
fbevents.js
14 ms
track.js
6 ms
api.js
142 ms
insight.min.js
23 ms
insight_tag_errors.gif
34 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
Includes front-end JavaScript libraries with known security vulnerabilities
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: