Tools & Wizards About Us

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

heidelberg.de

Startseite | Heidelberg

Page Load Speed

8.5 sec in total

First Response

316 ms

Resources Loaded

6.1 sec

Page Rendered

2 sec

About Website

Visit heidelberg.de now to see the best up-to-date Heidelberg content for Germany and also check out these interesting facts you probably never knew about heidelberg.de

Die offizielle Website der Stadt Heidelberg und Ihr digitales Rathaus - vereinbaren Sie hier Online-Termine in den Bürgerämtern und erfahren Sie alles zu Verwaltung, Bürgerservice, Politik, Umwelt, Bi...

Visit heidelberg.de

Key Findings

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

Performance Metrics

heidelberg.de performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value1,920 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

heidelberg.de

316 ms

heidelberg.de

422 ms

www.heidelberg.de

523 ms

HD.html

2770 ms

jquery-ui.min.css

305 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 89% of them (65 requests) were addressed to the original Heidelberg.de, 8% (6 requests) were made to Cookieconsent.komm.one and 1% (1 request) were made to Static.conword.io. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Heidelberg.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 500.9 kB (9%)

Content Size

5.3 MB

After Optimization

4.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Heidelberg.de main page is 5.3 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. 80% 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. Images take 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 359.8 kB

  • Original 407.4 kB
  • After minification 304.4 kB
  • After compression 47.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 103.0 kB, which is 25% 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 359.8 kB or 88% of the original size.

Image Optimization

-3%

Potential reduce by 132.7 kB

  • Original 4.6 MB
  • After minification 4.5 MB

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. Heidelberg images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.3 kB

  • Original 159.8 kB
  • After minification 159.8 kB
  • After compression 158.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-6%

Potential reduce by 7.1 kB

  • Original 121.3 kB
  • After minification 121.3 kB
  • After compression 114.2 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. Heidelberg.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 32 (49%)

Requests Now

65

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

heidelberg.de accessibility score

92

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

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

heidelberg.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

Missing source maps for large first-party JavaScript

SEO Factors

heidelberg.de SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Heidelberg.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 Heidelberg.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 Heidelberg. 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: