Tools & Wizards About Us
lindenbraeu-berlin.de screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lindenbraeu-berlin.de

Bier Genuss im Herzen von Berlin

Page Load Speed

3 sec in total

First Response

288 ms

Resources Loaded

2.5 sec

Page Rendered

236 ms

lindenbraeu-berlin.de screenshot

About Website

Welcome to lindenbraeu-berlin.de homepage info - get ready to check Lindenbraeu Berlin best content right away, or after learning these important things about lindenbraeu-berlin.de

Besuchen Sie unsere drei Lokale in Berlin-Mitte. Das Lindenbräu im Sony Center am Potsdamer Platz. Das Hopfingerbräu am Brandenburger Tor. Das Hopfingerbräu im Hauptbahnhof.

Visit lindenbraeu-berlin.de

Key Findings

We analyzed Lindenbraeu-berlin.de page load time and found that the first response time was 288 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

lindenbraeu-berlin.de performance score

0

Network Requests Diagram

lindenbraeu-berlin.de

288 ms

linden-hopfinger-braeu.de

285 ms

www.bier-genuss.berlin

737 ms

style_lb.css

430 ms

modernizr-2.7.1.min.js

192 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 Lindenbraeu-berlin.de, 84% (16 requests) were made to Bier-genuss.berlin and 5% (1 request) were made to Linden-hopfinger-braeu.de. The less responsive or slowest element that took the longest time to load (789 ms) relates to the external source Bier-genuss.berlin.

Page Optimization Overview & Recommendations

Page size can be reduced by 478.8 kB (35%)

Content Size

1.4 MB

After Optimization

896.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lindenbraeu-berlin.de main page is 1.4 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. 35% of websites need less resources to load. Images take 776.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 5.8 kB

  • Original 7.8 kB
  • After minification 7.0 kB
  • After compression 2.0 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 840 B, which is 11% 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 5.8 kB or 74% of the original size.

Image Optimization

-5%

Potential reduce by 38.1 kB

  • Original 776.3 kB
  • After minification 738.2 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. Lindenbraeu Berlin images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 332.0 kB

  • Original 475.2 kB
  • After minification 474.7 kB
  • After compression 143.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 332.0 kB or 70% of the original size.

CSS Optimization

-89%

Potential reduce by 102.9 kB

  • Original 115.8 kB
  • After minification 94.4 kB
  • After compression 12.9 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. Lindenbraeu-berlin.de needs all CSS files to be minified and compressed as it can save up to 102.9 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (31%)

Requests Now

16

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lindenbraeu-berlin.de

lindenbraeu-berlin.de

288 ms

linden-hopfinger-braeu.de

linden-hopfinger-braeu.de

285 ms

www.bier-genuss.berlin

www.bier-genuss.berlin

737 ms

style_lb.css

style_lb.css

430 ms

modernizr-2.7.1.min.js

modernizr-2.7.1.min.js

192 ms

plugins.min.js

plugins.min.js

789 ms

helper.min.js

helper.min.js

192 ms

modules.min.js

modules.min.js

303 ms

main.min.js

main.min.js

202 ms

analytics.js

analytics.js

11 ms

paper.png

paper.png

192 ms

logo.svg

logo.svg

108 ms

logo.svg

logo.svg

98 ms

bg_landing.jpg

bg_landing.jpg

380 ms

FrutigerLTStd-Roman.woff

FrutigerLTStd-Roman.woff

105 ms

ClareBTRom.woff

ClareBTRom.woff

185 ms

intro.jpg

intro.jpg

192 ms

intro.jpg

intro.jpg

407 ms

intro.jpg

intro.jpg

380 ms

SEO Factors

lindenbraeu-berlin.de SEO score

0

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 Lindenbraeu-berlin.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 Lindenbraeu-berlin.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

lindenbraeu-berlin.de

Open Graph data is detected on the main page of Lindenbraeu Berlin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: