Tools & Wizards About Us
eysser.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

eysser.com

Eyßer Schöne Gärten | Garten- & Landschaftsbau Dresden

Page Load Speed

4.5 sec in total

First Response

415 ms

Resources Loaded

3.9 sec

Page Rendered

197 ms

eysser.com screenshot

About Website

Visit eysser.com now to see the best up-to-date Eysser content and also check out these interesting facts you probably never knew about eysser.com

Garten- und Lanschaftsbau in Dresden: Eyßer Schöne Gärten. Wir sind Ihr Partner rund um die Neu- und Umgestaltung Ihres Gartens oder Grundstückes.

Visit eysser.com

Key Findings

We analyzed Eysser.com page load time and found that the first response time was 415 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

eysser.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value4.8 s

66/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.488

17/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

eysser.com

415 ms

www.eysser.com

327 ms

styles.css

165 ms

mobileLink.js

323 ms

colorbox.css

322 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 93% of them (26 requests) were addressed to the original Eysser.com, 7% (2 requests) were made to Tracker.euroweb.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Eysser.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 121.0 kB (23%)

Content Size

537.2 kB

After Optimization

416.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eysser.com main page is 537.2 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. Only 10% of websites need less resources to load. Images take 383.5 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 6.4 kB

  • Original 8.8 kB
  • After minification 7.2 kB
  • After compression 2.3 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.6 kB, which is 18% 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 6.4 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 12.2 kB

  • Original 383.5 kB
  • After minification 371.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. Eysser images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 90.6 kB

  • Original 130.0 kB
  • After minification 114.0 kB
  • After compression 39.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 90.6 kB or 70% of the original size.

CSS Optimization

-79%

Potential reduce by 11.8 kB

  • Original 14.9 kB
  • After minification 11.6 kB
  • After compression 3.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. Eysser.com needs all CSS files to be minified and compressed as it can save up to 11.8 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (23%)

Requests Now

26

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eysser.com

eysser.com

415 ms

www.eysser.com

www.eysser.com

327 ms

styles.css

styles.css

165 ms

mobileLink.js

mobileLink.js

323 ms

colorbox.css

colorbox.css

322 ms

jquery.js

jquery.js

801 ms

core.js

core.js

327 ms

colorbox.js

colorbox.js

486 ms

accordion.js

accordion.js

326 ms

tracker.js

tracker.js

308 ms

bg-body.jpg

bg-body.jpg

821 ms

bg-containerBottom.jpg

bg-containerBottom.jpg

419 ms

branding.png

branding.png

640 ms

garden01.jpg

garden01.jpg

2135 ms

bg-nav.jpg

bg-nav.jpg

192 ms

bg-contentsidebar.png

bg-contentsidebar.png

1531 ms

qrcode2-mit-rand.png

qrcode2-mit-rand.png

640 ms

bg-telephone.png

bg-telephone.png

638 ms

bg-businesshours.jpg

bg-businesshours.jpg

799 ms

bg-footer.jpg

bg-footer.jpg

800 ms

counter.js

counter.js

167 ms

bg-btn-desktop.png

bg-btn-desktop.png

773 ms

controls.png

controls.png

985 ms

border.png

border.png

986 ms

loading.gif

loading.gif

989 ms

futcm-webfont.woff

futcm-webfont.woff

1005 ms

futcl-webfont.woff

futcl-webfont.woff

1341 ms

print.css

print.css

159 ms

Accessibility Review

eysser.com accessibility score

90

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

Links do not have a discernible name

Best Practices

eysser.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

eysser.com SEO score

92

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

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 Eysser.com 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 Eysser.com 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

eysser.com

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