4.8 sec in total
324 ms
4.3 sec
262 ms
Welcome to hanhart.com homepage info - get ready to check Hanhart best content for United Kingdom right away, or after learning these important things about hanhart.com
Hanhart Chronographen und Stoppuhren
Visit hanhart.comWe analyzed Hanhart.com page load time and found that the first response time was 324 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
hanhart.com performance score
name
value
score
weighting
Value5.8 s
5/100
10%
Value14.2 s
0/100
25%
Value9.9 s
10/100
10%
Value840 ms
34/100
30%
Value0
100/100
15%
Value12.8 s
13/100
10%
324 ms
1554 ms
289 ms
291 ms
489 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 93% of them (54 requests) were addressed to the original Hanhart.com, 5% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Hanhart.com.
Page size can be reduced by 811.0 kB (39%)
2.1 MB
1.3 MB
In fact, the total size of Hanhart.com main page is 2.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. 45% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 103.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 13.7 kB, which is 11% 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 103.3 kB or 83% of the original size.
Potential reduce by 40.1 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. Hanhart images are well optimized though.
Potential reduce by 484.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 484.5 kB or 75% of the original size.
Potential reduce by 183.1 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. Hanhart.com needs all CSS files to be minified and compressed as it can save up to 183.1 kB or 83% of the original size.
Number of requests can be reduced by 31 (56%)
55
24
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hanhart. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and as a result speed up the page load time.
hanhart.com
324 ms
www.hanhart.com
1554 ms
advanced-navigation.css
289 ms
font-awesome.min.css
291 ms
prototype.js
489 ms
jquery-1.10.2.min.js
510 ms
validation.js
297 ms
builder.min.js
290 ms
effects.min.js
384 ms
dragdrop.min.js
386 ms
controls.min.js
387 ms
slider.js
394 ms
js.js
482 ms
form.js
486 ms
translate.min.js
485 ms
cookies.min.js
532 ms
et_currencymanager_round.js
579 ms
menu.js
582 ms
effects.js
580 ms
advanced-navigation.js
585 ms
adaptive_images.js
588 ms
modernizr.custom.min.js
590 ms
selectivizr.min.js
674 ms
matchMedia.min.js
676 ms
matchMedia.addListener.min.js
678 ms
enquire.min.js
679 ms
app_230315.min.js
682 ms
imagesloaded.pkgd.min.js
687 ms
minicart.min.js
768 ms
jquery.flexslider-min.js
773 ms
slideshow_v2_7.min.js
776 ms
isotope.pkgd.min.js
777 ms
packery-mode.pkgd.min.js
784 ms
ccard.min.js
790 ms
styles_1_12.css
968 ms
instant_checkout.js
785 ms
analytics.js
53 ms
hanhart_Logo_chrono.png
129 ms
hanhart_luenette.png
129 ms
IMG-20160307-WA0000-600x400.jpg
194 ms
201601201601Hanhart_Dakar_2016_04s321-600x400.jpg
310 ms
201512artur1-600x279.jpg
201 ms
20151111887972_10154189076805760_6750919059516453217_n-600x400.jpg
298 ms
201511Munichtime-2015-152_klein-600x399.jpg
411 ms
201510hanhart-3-wide-600x400.jpg
407 ms
Pilots-600x300.jpg
389 ms
phoca_thumb_l_1XRH78021-600x338.jpg
401 ms
uhrmacher_panitz-600x415.png
990 ms
201504survivor_pilot-600x434.jpg
415 ms
loading.gif
486 ms
cvv.gif
498 ms
dinregular-webfont.woff
469 ms
dinmedium-webfont.woff
477 ms
dinblack-webfont.woff
510 ms
collect
55 ms
hanhart_symbols.woff
513 ms
collect
58 ms
collect
27 ms
hanhart.com 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
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.
hanhart.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
hanhart.com 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
Tap targets are not sized appropriately
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hanhart.com 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 Hanhart.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.
hanhart.com
Open Graph description is not detected on the main page of Hanhart. 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: