Tools & Wizards About Us
konzertvergleich.de screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

konzertvergleich.de

Die Stadt gehört UNS. - PRINZ

Page Load Speed

3.1 sec in total

First Response

354 ms

Resources Loaded

2.6 sec

Page Rendered

136 ms

konzertvergleich.de screenshot

About Website

Welcome to konzertvergleich.de homepage info - get ready to check Konzertvergleich best content for Germany right away, or after learning these important things about konzertvergleich.de

PRINZ kennt die besten Restaurants, Cafés, Bars und informiert über die angesagtesten Konzerte, Partys und Events der Städte.

Visit konzertvergleich.de

Key Findings

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

Performance Metrics

konzertvergleich.de performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value650 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0.517

15/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

konzertvergleich.de

354 ms

prinz.de

496 ms

application.5a5517896db3.css

395 ms

application.2e005eff3491.js

504 ms

iam.js

519 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Konzertvergleich.de, 68% (13 requests) were made to Prinz.de and 11% (2 requests) were made to De.ioam.de. The less responsive or slowest element that took the longest time to load (781 ms) relates to the external source Prinz.de.

Page Optimization Overview & Recommendations

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

Content Size

693.8 kB

After Optimization

192.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Konzertvergleich.de main page is 693.8 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. 25% of websites need less resources to load. CSS take 458.1 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 11.3 kB

  • Original 16.1 kB
  • After minification 12.6 kB
  • After compression 4.8 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 3.5 kB, which is 22% 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 11.3 kB or 70% of the original size.

Image Optimization

-20%

Potential reduce by 30.9 kB

  • Original 153.6 kB
  • After minification 122.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, Konzertvergleich needs image optimization as it can save up to 30.9 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 35.1 kB

  • Original 66.1 kB
  • After minification 57.2 kB
  • After compression 31.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 35.1 kB or 53% of the original size.

CSS Optimization

-92%

Potential reduce by 423.5 kB

  • Original 458.1 kB
  • After minification 270.4 kB
  • After compression 34.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. Konzertvergleich.de needs all CSS files to be minified and compressed as it can save up to 423.5 kB or 92% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (40%)

Requests Now

10

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

konzertvergleich.de

konzertvergleich.de

354 ms

prinz.de

prinz.de

496 ms

application.5a5517896db3.css

application.5a5517896db3.css

395 ms

application.2e005eff3491.js

application.2e005eff3491.js

504 ms

iam.js

iam.js

519 ms

qs.ioam.de

qs.ioam.de

281 ms

tx.io

tx.io

283 ms

tx.io

tx.io

95 ms

icons-s0f4d381ee5.d7cef07bd8c5.png

icons-s0f4d381ee5.d7cef07bd8c5.png

781 ms

prinz-logo.c2cad0bde847.png

prinz-logo.c2cad0bde847.png

130 ms

germany-map.a308c8b18ec7.png

germany-map.a308c8b18ec7.png

379 ms

portal-location.e18377566bc5.png

portal-location.e18377566bc5.png

258 ms

titillium-thin.2c63c74e89b2.woff

titillium-thin.2c63c74e89b2.woff

365 ms

titillium-light.361d8b27d8e1.woff

titillium-light.361d8b27d8e1.woff

377 ms

titillium-regular.bae37e36a65d.woff

titillium-regular.bae37e36a65d.woff

394 ms

titillium-bold.ee404828a6db.woff

titillium-bold.ee404828a6db.woff

490 ms

titillium-semibold.f7619ff980d7.woff

titillium-semibold.f7619ff980d7.woff

613 ms

titillium-black.7281db472320.woff

titillium-black.7281db472320.woff

493 ms

nr-892.min.js

nr-892.min.js

16 ms

Accessibility Review

konzertvergleich.de accessibility score

58

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

konzertvergleich.de best practices score

75

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

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

konzertvergleich.de SEO score

85

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

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

konzertvergleich.de

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