Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

blog.inberlin.de

Blog@inBerlin - der Berlin Blog für alle Neu- und Alt-Berliner

Page Load Speed

10.2 sec in total

First Response

3 sec

Resources Loaded

6.4 sec

Page Rendered

837 ms

blog.inberlin.de screenshot

About Website

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

Der Berlin Blog für Geschichte/Kultur und Freizeit in Berlin! Von der Vergangenheit bis in die Gegenwart - von Flohmärkten bis zum Vegan-Restaurant.

Visit blog.inberlin.de

Key Findings

We analyzed Blog.inberlin.de page load time and found that the first response time was 3 sec and then it took 7.2 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

blog.inberlin.de performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value4,150 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.209

59/100

15%

TTI (Time to Interactive)

Value20.4 s

2/100

10%

Network Requests Diagram

blog.inberlin.de

2988 ms

wp-emoji-release.min.js

198 ms

widget.css

191 ms

style.css

197 ms

style.css

193 ms

Our browser made a total of 162 requests to load all elements on the main page. We found that 41% of them (66 requests) were addressed to the original Blog.inberlin.de, 16% (26 requests) were made to Pbs.twimg.com and 12% (20 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Blog.inberlin.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (31%)

Content Size

3.7 MB

After Optimization

2.5 MB

In fact, the total size of Blog.inberlin.de main page is 3.7 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. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 185.8 kB

  • Original 237.4 kB
  • After minification 231.3 kB
  • After compression 51.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 185.8 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 54.9 kB

  • Original 2.1 MB
  • After minification 2.1 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. Blog InBerlin images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 658.7 kB

  • Original 989.1 kB
  • After minification 982.7 kB
  • After compression 330.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 658.7 kB or 67% of the original size.

CSS Optimization

-85%

Potential reduce by 253.2 kB

  • Original 298.2 kB
  • After minification 234.3 kB
  • After compression 45.1 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.inberlin.de needs all CSS files to be minified and compressed as it can save up to 253.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (41%)

Requests Now

153

After Optimization

90

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

Accessibility Review

blog.inberlin.de accessibility score

88

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

blog.inberlin.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

SEO Factors

blog.inberlin.de SEO score

89

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

Links do not have descriptive text

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 Blog.inberlin.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.inberlin.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 InBerlin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: