Report Summary

  • 9

    Performance

    Renders faster than
    31% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    34% of websites

  • 93

    SEO

    Google-friendlier than
    88% of websites

hamburg.de

hamburg.de - Offizielles Stadtportal für die Hansestadt Hamburg

Page Load Speed

7.7 sec in total

First Response

276 ms

Resources Loaded

6.7 sec

Page Rendered

777 ms

hamburg.de screenshot

About Website

Click here to check amazing Hamburg content for Germany. Otherwise, check out these important facts you probably never knew about hamburg.de

Alle Informationen über Hamburg übersichtlich und schnell gefunden. Hamburg von A bis Z für Hamburger, Touristen und Unternehmen.

Visit hamburg.de

Key Findings

We analyzed Hamburg.de page load time and found that the first response time was 276 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

hamburg.de performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value31.9 s

0/100

10%

TBT (Total Blocking Time)

Value38,720 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.206

60/100

15%

TTI (Time to Interactive)

Value59.6 s

0/100

10%

Network Requests Diagram

hamburg.de

276 ms

www.hamburg.de

1025 ms

iam.js

406 ms

cssapi.css

264 ms

de.css

549 ms

Our browser made a total of 263 requests to load all elements on the main page. We found that 43% of them (112 requests) were addressed to the original Hamburg.de, 5% (14 requests) were made to Cdn1.smartadserver.com and 4% (10 requests) were made to Ww251.smartadserver.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Hamburg.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (60%)

Content Size

3.0 MB

After Optimization

1.2 MB

In fact, the total size of Hamburg.de main page is 3.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 217.2 kB

  • Original 277.3 kB
  • After minification 263.2 kB
  • After compression 60.1 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 217.2 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 30.8 kB

  • Original 621.0 kB
  • After minification 590.2 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 images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 1.5 MB

  • Original 2.0 MB
  • After minification 1.9 MB
  • After compression 522.0 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 1.5 MB or 74% of the original size.

CSS Optimization

-80%

Potential reduce by 100.6 kB

  • Original 125.6 kB
  • After minification 101.6 kB
  • After compression 25.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. Hamburg.de needs all CSS files to be minified and compressed as it can save up to 100.6 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 137 (56%)

Requests Now

245

After Optimization

108

The browser has sent 245 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hamburg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

hamburg.de accessibility score

76

Accessibility Issues

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

High

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

hamburg.de best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

hamburg.de SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hamburg.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 Hamburg.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Hamburg. 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: