3.9 sec in total
941 ms
2.7 sec
235 ms
Visit havag.com now to see the best up-to-date HAVAG content for Germany and also check out these interesting facts you probably never knew about havag.com
Die Hallesche Verkehrs-AG gehört dem Mitteldeutschen Verkehrsverbund an und bedient das Gebiet Halle (Saale) und Merseburg.
Visit havag.comWe analyzed Havag.com page load time and found that the first response time was 941 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
havag.com performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value17.1 s
0/100
25%
Value10.0 s
9/100
10%
Value4,190 ms
1/100
30%
Value0.81
5/100
15%
Value17.3 s
4/100
10%
941 ms
328 ms
432 ms
331 ms
332 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that all of those requests were addressed to Havag.com and no external sources were called. The less responsive or slowest element that took the longest time to load (941 ms) belongs to the original domain Havag.com.
Page size can be reduced by 385.0 kB (52%)
739.1 kB
354.1 kB
In fact, the total size of Havag.com main page is 739.1 kB. 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 304.5 kB which makes up the majority of the site volume.
Potential reduce by 37.0 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 37.0 kB or 80% of the original size.
Potential reduce by 61.7 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. Obviously, HAVAG needs image optimization as it can save up to 61.7 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 162.3 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 162.3 kB or 67% of the original size.
Potential reduce by 124.0 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. Havag.com needs all CSS files to be minified and compressed as it can save up to 124.0 kB or 85% of the original size.
Number of requests can be reduced by 31 (67%)
46
15
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HAVAG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
havag.com
941 ms
common.css
328 ms
jquery-ui-1.8.12.custom.css
432 ms
jquery.timeentry.css
331 ms
colorbox.css
332 ms
jquery.js
645 ms
jquery-ui-1.8.12.custom.min.js
545 ms
jquery.timeentry.pack.js
433 ms
font-size.js
434 ms
i18n.de.js
434 ms
jquery.jscrollpane.js
530 ms
jquery.mousewheel.js
529 ms
main.js
534 ms
ui.datepicker-de.js
536 ms
jquery.colorbox.js
629 ms
jquery.ie-select-width.js
630 ms
stations_autocomplete.js
542 ms
reset.css
316 ms
general.css
327 ms
formate.css
514 ms
color.css
415 ms
jquery.jscrollpane.css
418 ms
logo.png
208 ms
home.gif
106 ms
my_havag_mh.png
104 ms
lupe.gif
104 ms
arrow_bottom.gif
106 ms
time.gif
107 ms
calendar.gif
203 ms
f
381 ms
thumb
219 ms
thumb
220 ms
thumb
322 ms
info.gif
274 ms
f
694 ms
f
810 ms
f
326 ms
f
375 ms
f
425 ms
piwik.js
406 ms
piwik.php
387 ms
loading_background.png
104 ms
loading.gif
108 ms
controls.png
109 ms
close.png
204 ms
ui-bg_highlight-soft_100_eeeeee_1x100.png
211 ms
print.css
106 ms
havag.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.
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
ARIA IDs are not unique
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.
havag.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
Missing source maps for large first-party JavaScript
havag.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
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Havag.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Havag.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.
havag.com
Open Graph description is not detected on the main page of HAVAG. 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: