Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

goettgen.de

GOETTGEN - Die Schmuck Profis

Page Load Speed

6.8 sec in total

First Response

303 ms

Resources Loaded

6 sec

Page Rendered

488 ms

goettgen.de screenshot

About Website

Visit goettgen.de now to see the best up-to-date GOETTGEN content for Germany and also check out these interesting facts you probably never knew about goettgen.de

Der Onlineshop und Store für Schmuck und Uhren mit umfassenden Bereichen über Schmuckwissen und Service.

Visit goettgen.de

Key Findings

We analyzed Goettgen.de page load time and found that the first response time was 303 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

goettgen.de performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

goettgen.de

303 ms

www.goettgen.de

2139 ms

aggregator.css

193 ms

book.css

206 ms

node.css

208 ms

Our browser made a total of 143 requests to load all elements on the main page. We found that 92% of them (132 requests) were addressed to the original Goettgen.de, 1% (2 requests) were made to Facebook.com and 1% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Goettgen.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 519.7 kB (26%)

Content Size

2.0 MB

After Optimization

1.5 MB

In fact, the total size of Goettgen.de main page is 2.0 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. 40% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 111.4 kB

  • Original 133.1 kB
  • After minification 121.3 kB
  • After compression 21.7 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 111.4 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 70.9 kB

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

JavaScript Optimization

-58%

Potential reduce by 54.0 kB

  • Original 93.5 kB
  • After minification 84.9 kB
  • After compression 39.5 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 54.0 kB or 58% of the original size.

CSS Optimization

-85%

Potential reduce by 283.4 kB

  • Original 332.4 kB
  • After minification 213.6 kB
  • After compression 49.0 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. Goettgen.de needs all CSS files to be minified and compressed as it can save up to 283.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (39%)

Requests Now

141

After Optimization

86

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

Accessibility Review

goettgen.de accessibility score

74

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

goettgen.de best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

goettgen.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

Links do not have descriptive text

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

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 Goettgen.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 Goettgen.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 description is not detected on the main page of GOETTGEN. 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: