5.5 sec in total
859 ms
4.5 sec
202 ms
Click here to check amazing Hacon content for Germany. Otherwise, check out these important facts you probably never knew about hacon.de
Wir entwickeln digitale, effiziente und vernetzte Lösungen für die Mobilität von morgen - von der Reiseinformation über MaaS zu Operator Business Products.
Visit hacon.deWe analyzed Hacon.de page load time and found that the first response time was 859 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
hacon.de performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value26.9 s
0/100
25%
Value18.1 s
0/100
10%
Value80 ms
99/100
30%
Value0.278
44/100
15%
Value19.8 s
2/100
10%
859 ms
224 ms
259 ms
292 ms
325 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 89% of them (59 requests) were addressed to the original Hacon.de, 6% (4 requests) were made to Piwik.hacon.de and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Hacon.de.
Page size can be reduced by 180.1 kB (14%)
1.2 MB
1.1 MB
In fact, the total size of Hacon.de main page is 1.2 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. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 36.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 9.0 kB, which is 20% 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 36.3 kB or 82% of the original size.
Potential reduce by 61.3 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. Hacon images are well optimized though.
Potential reduce by 82.5 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 82.5 kB or 58% of the original size.
Number of requests can be reduced by 35 (65%)
54
19
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hacon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
hacon.de
859 ms
base-cachekey8032.css
224 ms
resourceContentWellPortlets.stylesContentWellPortlets-cachekey1274.css
259 ms
hacon_base-cachekey4285.css
292 ms
hacon_navigation-cachekey0995.css
325 ms
hacon_topic_navigation-cachekey9258.css
358 ms
hacon_content-cachekey9314.css
393 ms
hacon_summary_content-cachekey7311.css
462 ms
hacon_reference_content-cachekey9688.css
463 ms
hacon_weblog_content-cachekey1678.css
500 ms
hacon_picturecredits_content-cachekey5629.css
564 ms
hacon_portlets-cachekey4262.css
563 ms
hacon_boxes-cachekey8754.css
606 ms
hacon_footer_navigation-cachekey1831.css
716 ms
hacon_authoring-cachekey8158.css
680 ms
ploneCustom-cachekey9221.css
716 ms
jquery-cachekey4466.js
898 ms
resourceprototype-cachekey2517.js
1048 ms
resourcecollective.fancyzoomview.javascriptfancyzoom-cachekey4722.js
942 ms
bodyBG.png
401 ms
hacon-logo.png
314 ms
spriteLanguage.png
248 ms
input_background.gif
323 ms
btn_search.png
279 ms
bg_mainnav_008787.png
279 ms
bg_mainnav_round.png
391 ms
bg_mainnav_active.png
448 ms
arrLeft.png
476 ms
4a0fec68480ae612022fafd66cdfa1c5
550 ms
9c76cc58f693ed6924a5c97489a776e5
639 ms
4829f917d58e4bd3719368cfcc8d14b6
643 ms
b14e80cbea9d8b375c154bf1a67068b1
633 ms
arrRight.png
629 ms
picHomeHafas.png
943 ms
picHomeTps.png
852 ms
picHomeConsulting.png
1117 ms
image_preview
1063 ms
image_preview
941 ms
fbshare.png
860 ms
5be71cf6d8982ffa729d8d39fd0110ce
1003 ms
fd68d6bb788d8048d47b48d70b8d82cd
1033 ms
50a77deaa5d09e6058684fceeb251a7c
1116 ms
75cf53ad2a4324fe50de24c74b7665a1
1085 ms
hacon_breadcrumbs.png
1222 ms
spinner.gif
1262 ms
bg_mainnav_008787.png
215 ms
seperateLineHome.png
1251 ms
arrowBlueSize01.png
1251 ms
arrFooter.png
1310 ms
bg_sitemap_round.png
1312 ms
ga.js
12 ms
piwik.js
692 ms
closebox.png
1341 ms
__utm.gif
10 ms
Slide_MIT.png-en
1187 ms
Slides_Wearables_2015_e.png
1743 ms
Apps_e.png
1244 ms
info_slider4.png
1615 ms
piwik.js
583 ms
Facebook_grau_web.png
577 ms
Twitter_grau_web.png
551 ms
XING_grau_web.png
686 ms
LinkedIn_grau_web.png
652 ms
piwik.php
96 ms
piwik.php
169 ms
hacon_print-cachekey5831.css
153 ms
hacon.de accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
hacon.de 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
hacon.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hacon.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Hacon.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.
hacon.de
Open Graph description is not detected on the main page of Hacon. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: