Tools & Wizards About Us
pusteblume-rostock.de screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

pusteblume-rostock.de

Pusteblume - Ihr Restaurant am Stadtrand von Rostock

Page Load Speed

3.2 sec in total

First Response

387 ms

Resources Loaded

2.4 sec

Page Rendered

341 ms

pusteblume-rostock.de screenshot

About Website

Welcome to pusteblume-rostock.de homepage info - get ready to check Pusteblume Rostock best content right away, or after learning these important things about pusteblume-rostock.de

Pusteblume Rostock. Restaurant am westlichen Stadtrand von Rostock. Wir bieten Retaurantbetrieb, Catering und Event Service.

Visit pusteblume-rostock.de

Key Findings

We analyzed Pusteblume-rostock.de page load time and found that the first response time was 387 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 50% of websites can load faster.

Performance Metrics

pusteblume-rostock.de performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

69/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

84/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.479

18/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

pusteblume-rostock.de

387 ms

jquery-latest.min.js

7 ms

jquery.slides.min.js

364 ms

boilerplate.css

590 ms

stv.css

687 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 82% of them (14 requests) were addressed to the original Pusteblume-rostock.de, 12% (2 requests) were made to Google-analytics.com and 6% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Pusteblume-rostock.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 66.8 kB (4%)

Content Size

1.6 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pusteblume-rostock.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. 25% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 7.3 kB

  • Original 10.2 kB
  • After minification 8.9 kB
  • After compression 2.9 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 1.3 kB, which is 13% 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 7.3 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 11.8 kB

  • Original 1.5 MB
  • After minification 1.5 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. Pusteblume Rostock images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

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

CSS Optimization

-85%

Potential reduce by 15.6 kB

  • Original 18.4 kB
  • After minification 9.7 kB
  • After compression 2.8 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. Pusteblume-rostock.de needs all CSS files to be minified and compressed as it can save up to 15.6 kB or 85% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

16

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pusteblume Rostock. According to our analytics all requests are already optimized.

Network Requests Diagram

pusteblume-rostock.de

pusteblume-rostock.de

387 ms

jquery-latest.min.js

jquery-latest.min.js

7 ms

jquery.slides.min.js

jquery.slides.min.js

364 ms

boilerplate.css

boilerplate.css

590 ms

stv.css

stv.css

687 ms

logo.jpg

logo.jpg

469 ms

IMG_3882.png

IMG_3882.png

850 ms

Fotolia_51662619_S.jpg

Fotolia_51662619_S.jpg

905 ms

Fotolia_53205431_S.jpg

Fotolia_53205431_S.jpg

1026 ms

Fotolia_52898630_S.jpg

Fotolia_52898630_S.jpg

1277 ms

Fotolia_7996540_S.jpg

Fotolia_7996540_S.jpg

1407 ms

Fotolia_39708077_S.jpg

Fotolia_39708077_S.jpg

1674 ms

logo_klein.png

logo_klein.png

1089 ms

blume.png

blume.png

1241 ms

analytics.js

analytics.js

72 ms

pagination.png

pagination.png

846 ms

collect

collect

23 ms

Accessibility Review

pusteblume-rostock.de accessibility score

66

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.

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

pusteblume-rostock.de best practices score

67

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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

pusteblume-rostock.de SEO score

83

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

High

Tap targets are not sized appropriately

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 Pusteblume-rostock.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 Pusteblume-rostock.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

pusteblume-rostock.de

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