Tools & Wizards About Us

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

blog.codecentric.de

IT-Expertenwissen von Entwicklern für Entwickler

Page Load Speed

3 sec in total

First Response

218 ms

Resources Loaded

2.4 sec

Page Rendered

405 ms

About Website

Visit blog.codecentric.de now to see the best up-to-date Blog Codecentric content for United States and also check out these interesting facts you probably never knew about blog.codecentric.de

Im codecentric Blog schreiben codecentricer*innen über aktuelle IT-Themen: Agile Methoden, Softwarearchitektur, KI, Testing und vieles mehr.

Visit blog.codecentric.de

Key Findings

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

Performance Metrics

blog.codecentric.de performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value7.0 s

33/100

10%

TBT (Total Blocking Time)

Value3,820 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

blog.codecentric.de

218 ms

blog.codecentric.de

379 ms

blog

769 ms

podloveCdn.js

493 ms

loader.js

20 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Blog.codecentric.de, 91% (41 requests) were made to Codecentric.de and 4% (2 requests) were made to App.usercentrics.eu. The less responsive or slowest element that took the longest time to load (785 ms) relates to the external source Codecentric.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 647.6 kB (41%)

Content Size

1.6 MB

After Optimization

928.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Blog.codecentric.de main page is 1.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. HTML takes 808.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 647.6 kB

  • Original 808.2 kB
  • After minification 807.9 kB
  • After compression 160.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. 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 647.6 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 564.4 kB
  • After minification 564.4 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. Blog Codecentric images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 203.9 kB
  • After minification 203.9 kB
  • After compression 203.9 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.

Requests Breakdown

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

Requests Now

41

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

blog.codecentric.de accessibility score

83

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

blog.codecentric.de best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

blog.codecentric.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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.codecentric.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Blog.codecentric.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 data is detected on the main page of Blog Codecentric. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: