Tools & Wizards About Us
blog.codecentric.de screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

blog.codecentric.de

IT-Expertenwissen von Entwicklern für Entwickler

Page Load Speed

2.3 sec in total

First Response

313 ms

Resources Loaded

1.7 sec

Page Rendered

201 ms

blog.codecentric.de screenshot

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 313 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

blog.codecentric.de performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

blog.codecentric.de

313 ms

blog.codecentric.de

376 ms

b02b715b7281faed53698d2047584885-compressor-part.css

483 ms

6f6f493f64ca648636eb947075339c4f-compressor-part.js

245 ms

c6e7b473930944d65a8c96fbf1305f8f-compressor-part.js

249 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 77% of them (24 requests) were addressed to the original Blog.codecentric.de, 6% (2 requests) were made to Ssl.google-analytics.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (574 ms) belongs to the original domain Blog.codecentric.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 326.3 kB (64%)

Content Size

510.7 kB

After Optimization

184.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.codecentric.de main page is 510.7 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. Javascripts take 210.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 23.8 kB

  • Original 30.2 kB
  • After minification 29.5 kB
  • After compression 6.4 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 23.8 kB or 79% of the original size.

Image Optimization

-9%

Potential reduce by 6.2 kB

  • Original 66.6 kB
  • After minification 60.3 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

-60%

Potential reduce by 127.3 kB

  • Original 210.5 kB
  • After minification 210.5 kB
  • After compression 83.2 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 127.3 kB or 60% of the original size.

CSS Optimization

-83%

Potential reduce by 168.9 kB

  • Original 203.4 kB
  • After minification 202.6 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. Blog.codecentric.de needs all CSS files to be minified and compressed as it can save up to 168.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (30%)

Requests Now

27

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 27 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 9 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

blog.codecentric.de

blog.codecentric.de

313 ms

blog.codecentric.de

blog.codecentric.de

376 ms

b02b715b7281faed53698d2047584885-compressor-part.css

b02b715b7281faed53698d2047584885-compressor-part.css

483 ms

6f6f493f64ca648636eb947075339c4f-compressor-part.js

6f6f493f64ca648636eb947075339c4f-compressor-part.js

245 ms

c6e7b473930944d65a8c96fbf1305f8f-compressor-part.js

c6e7b473930944d65a8c96fbf1305f8f-compressor-part.js

249 ms

jquery.min.js

jquery.min.js

90 ms

8c38ba51b074257c0dca6c118109945f-compressor-part.js

8c38ba51b074257c0dca6c118109945f-compressor-part.js

574 ms

devicepx-jetpack.js

devicepx-jetpack.js

127 ms

d67aaa0fbf26bd9c18a2c13656e41f56-compressor-part.js

d67aaa0fbf26bd9c18a2c13656e41f56-compressor-part.js

249 ms

e-201609.js

e-201609.js

20 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

145 ms

ga.js

ga.js

143 ms

24b01165392f040800e3539b35ba0e6c

24b01165392f040800e3539b35ba0e6c

277 ms

header_bg.jpg

header_bg.jpg

265 ms

suche_lupe.png

suche_lupe.png

135 ms

codecentric-logo.png

codecentric-logo.png

135 ms

codecentric-logo-mobil-active.png

codecentric-logo-mobil-active.png

157 ms

codecentric-logo.png

codecentric-logo.png

158 ms

olcay_hasanoglu-50x50.jpg

olcay_hasanoglu-50x50.jpg

265 ms

ee706eea-6842-4241-8400-640ca2df80b9.6572d028-6884-4eb6-88dd-0950c5afa357.1.1.image_1-50x50.jpg

ee706eea-6842-4241-8400-640ca2df80b9.6572d028-6884-4eb6-88dd-0950c5afa357.1.1.image_1-50x50.jpg

271 ms

jonas_hecht1-50x50.jpg

jonas_hecht1-50x50.jpg

269 ms

felix_braun-50x50.jpg

felix_braun-50x50.jpg

269 ms

tobias_flohre-50x50.jpg

tobias_flohre-50x50.jpg

270 ms

joerg_spiegelhoff-50x50.png

joerg_spiegelhoff-50x50.png

268 ms

tobias_schaber_-50x50.jpg

tobias_schaber_-50x50.jpg

359 ms

facebook.gif

facebook.gif

350 ms

twitter.gif

twitter.gif

350 ms

2DE131_1C_0.woff

2DE131_1C_0.woff

475 ms

2DE131_11_0.woff

2DE131_11_0.woff

318 ms

__utm.gif

__utm.gif

92 ms

g.gif

g.gif

24 ms

Accessibility Review

blog.codecentric.de accessibility score

87

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.

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

83

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

Page has valid source maps

SEO Factors

blog.codecentric.de SEO score

86

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

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

blog.codecentric.de

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: