9.9 sec in total
332 ms
8.6 sec
1 sec
Visit hamburg1.de now to see the best up-to-date Hamburg 1 content for Germany and also check out these interesting facts you probably never knew about hamburg1.de
Hamburg 1 ist der TV Sender für die Metropolregion Hamburg. Mit einer technischen Reichweite von 1,9 Mio. Haushalten sendet Hamburg 1 bis über die Stadtgrenzen hinaus ins naheliegende Umland. Auch auß...
Visit hamburg1.deWe analyzed Hamburg1.de page load time and found that the first response time was 332 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
hamburg1.de performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value8.5 s
1/100
25%
Value5.5 s
54/100
10%
Value500 ms
58/100
30%
Value0.919
3/100
15%
Value6.8 s
55/100
10%
332 ms
1342 ms
21 ms
40 ms
457 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 19% of them (29 requests) were addressed to the original Hamburg1.de, 25% (38 requests) were made to Images.telvi.de and 17% (25 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (6.1 sec) relates to the external source Images.telvi.de.
Page size can be reduced by 1.0 MB (16%)
6.6 MB
5.6 MB
In fact, the total size of Hamburg1.de main page is 6.6 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 5.3 MB which makes up the majority of the site volume.
Potential reduce by 102.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 16.6 kB, which is 14% 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 102.6 kB or 86% of the original size.
Potential reduce by 68.5 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. Hamburg 1 images are well optimized though.
Potential reduce by 654.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 654.3 kB or 67% of the original size.
Potential reduce by 210.5 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. Hamburg1.de needs all CSS files to be minified and compressed as it can save up to 210.5 kB or 89% of the original size.
Number of requests can be reduced by 46 (32%)
144
98
The browser has sent 144 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hamburg 1. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
hamburg1.de
332 ms
www.hamburg1.de
1342 ms
swfobject.js
21 ms
js
40 ms
instreamapi-2.1.2.min.js
457 ms
foundation.css
453 ms
icomoon.css
250 ms
slick.css
252 ms
style.css
380 ms
modernizr.js
334 ms
jquery.js
764 ms
app.js
389 ms
video.js
446 ms
Chart.min.js
638 ms
numeral.min.js
517 ms
css
23 ms
foundation.js
346 ms
foundation.topbar.js
345 ms
foundation.clearing.js
348 ms
foundation.accordion.js
423 ms
foundation.reveal.js
456 ms
slick.min.js
459 ms
logo_xxhamburg1.png
1039 ms
logo_hamburg1w.png
178 ms
0738c7954b5384c4e9594720.jpg
1292 ms
1ab36dd105e450082aa746ec.jpg
1121 ms
9583972a089b5216e076a012.jpg
3606 ms
4dd9c4c54a99eb75e7f0eead.jpg
1286 ms
d57b0d21280950ec2518690c.jpg
1976 ms
5b4ec187e3123766b2bd66ad.jpg
1715 ms
9f7bb3834d8a3253feb335ef.jpg
2132 ms
703e942798f9ddc9c7022c2c.jpg
2244 ms
00beedbd4d69052cda7033cc.jpg
2356 ms
ceaa4de42d2b8f70ec5980a4.jpg
2523 ms
b33d9ccea1a1d394a4d40098.jpg
2717 ms
232bf159d3a40fd4c773b60e.jpg
3008 ms
f94319e5770333a389be8405.jpg
3298 ms
b598a636d7e551ddf1013028.jpg
3196 ms
10ca1636c120b78600fc8679.jpg
4141 ms
fs_joey-regular-webfont.woff
391 ms
fs_joey-bold-webfont.woff
301 ms
icomoon.woff
149 ms
fs_joey-medium-webfont.woff
394 ms
fs_joey-bold_italic-webfont.woff
393 ms
common.js
28 ms
map.js
28 ms
crossteaser.php
357 ms
oton.jpg
351 ms
c9b3451fe2bf0ffc281d6652.jpg
3544 ms
0040a8a28e32af94ee5cc912.jpg
3915 ms
5de0fa971b009d9284c3774c.jpg
4212 ms
fc79b39a8430db025fc8a8de.jpg
4245 ms
0d3985605242f6779b631157.jpg
4408 ms
0848aa8297950778bc93a6e3e21198c5.jpg
4527 ms
8b2a0b2b778e788ae749d497.jpg
4457 ms
6df1d0818d49f6be7a1f7bea.jpg
4643 ms
7de283e82494006de36c2bb8.jpg
4925 ms
54ecf76ec2414978c65d115d.jpg
5007 ms
fffcfa9e0268f3cbff6ee513.jpg
4780 ms
6703f67bf0aebda48df416fe.jpg
5189 ms
07c3b5a03ffae7009afbf17d.jpg
5467 ms
359d7f9fdd191a09946edc70.jpg
5190 ms
5d0ccfdc0ceccf0d4de887c4.jpg
5219 ms
e6b6d65b25c3359ed107f70d.jpg
5254 ms
0275557994e80d33969b82e3.jpg
5815 ms
33dfa3ea59c5b13352348c7f.jpg
5851 ms
d82cc93aef95b1cb6c068f9c.jpg
5533 ms
03d65447f053b544b093421e2bc9fdf1.jpg
6103 ms
7b1550603046f416d0e3681ad3c43a6b.jpg
5921 ms
StaticMapService.GetMapImage
244 ms
widgets.js
53 ms
util.js
39 ms
onion.js
38 ms
ViewportInfoService.GetViewportInfo
60 ms
stats.js
21 ms
controls.js
55 ms
transparent.png
48 ms
css
23 ms
google4.png
61 ms
marker.js
24 ms
mapcnt6.png
59 ms
sv5.png
58 ms
openhand_8_8.cur
59 ms
2124_28.jpg
340 ms
vt
234 ms
vt
234 ms
analytics.js
235 ms
piwik.js
526 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
67 ms
ajax-loader.gif
191 ms
vt
57 ms
vt
56 ms
vt
55 ms
vt
54 ms
vt
55 ms
vt
99 ms
vt
91 ms
vt
95 ms
vt
92 ms
vt
93 ms
vt
96 ms
tmapctrl.png
47 ms
fs_joey-bold_italic-webfont.woff
360 ms
fs_joey-bold-webfont.woff
341 ms
cb_scout5.png
87 ms
tmapctrl4.png
70 ms
imgs8.png
74 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
83 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
169 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
170 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
169 ms
slick.woff
278 ms
collect
44 ms
syndication
275 ms
544493332639252481
336 ms
collect
212 ms
AuthenticationService.Authenticate
330 ms
piwik.php
317 ms
eff4823ca2a5ca6be003561f.jpg
5193 ms
1f643.png
144 ms
26ab.png
140 ms
26aa.png
140 ms
1f49a.png
133 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
7 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
27 ms
z5g1s8dccak7h66cqsnu_normal.jpeg
199 ms
MF0A4Vsf_normal.jpg
223 ms
pPIMQSdG_normal.jpg
268 ms
zzQJ_fkZ_normal.jpg
298 ms
ScX5mllH_normal.jpg
308 ms
FTgHry5C_normal.jpg
324 ms
251ef92f4a12ff5965d6d465e04c1b12_normal.jpeg
427 ms
Fjx1XERa_normal.jpg
327 ms
NTDY624i_normal.png
330 ms
gwPnOaCX_normal.jpg
325 ms
zQzgyzl8_normal.jpg
335 ms
c4TiPfJb_normal.jpg
349 ms
Ilt4smXx_normal.jpeg
352 ms
CcDu-oJW0AA-ZbM.jpg:small
379 ms
CcC_BRWWoAEZsiL.jpg:small
387 ms
Cba5S6EWcAEd6dG.jpg:small
361 ms
Ca1txvaWIAAB7bo.jpg:small
376 ms
Ca15LDlWIAANWEL.jpg:small
380 ms
CaPHslzXEAEjxyo.jpg:small
394 ms
CaGUkPFWQAABljk.jpg:small
404 ms
CZzWedPXEAAvwbg.jpg:small
407 ms
CZq5w3tXEAA9mHT.jpg:small
421 ms
CZjv4K1WYAAHBRs.jpg:small
417 ms
084af634b4d1a396cf354084.jpg
4838 ms
jot
26 ms
QuotaService.RecordEvent
41 ms
hamburg1.de accessibility score
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
Links do not have a discernible name
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
hamburg1.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Missing source maps for large first-party JavaScript
hamburg1.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
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 Hamburg1.de 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 Hamburg1.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.
hamburg1.de
Open Graph description is not detected on the main page of Hamburg 1. 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: