Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 47

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

mygshock.de

G-SHOCK | Die Brand | CASIO

Page Load Speed

10 sec in total

First Response

304 ms

Resources Loaded

9.3 sec

Page Rendered

398 ms

mygshock.de screenshot

About Website

Click here to check amazing Myg SHOCK content. Otherwise, check out these important facts you probably never knew about mygshock.de

Widerstandsfähige Materialien, innovative Funktionen und unverwechselbar im Design: Entdecke die G-SHOCK Uhren. ⌚ Finde umfassende Informationen rund um die Brand.

Visit mygshock.de

Key Findings

We analyzed Mygshock.de page load time and found that the first response time was 304 ms and then it took 9.7 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

mygshock.de performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.207

60/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

mygshock.de

304 ms

www.mygshock.de

1072 ms

ga.js

12 ms

responsive-slider.css

197 ms

mediaelements-genericons.css

200 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 54% of them (34 requests) were addressed to the original Mygshock.de, 16% (10 requests) were made to Static.xx.fbcdn.net and 11% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (6.2 sec) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 301.0 kB (31%)

Content Size

960.8 kB

After Optimization

659.8 kB

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

HTML Optimization

-79%

Potential reduce by 54.2 kB

  • Original 68.5 kB
  • After minification 66.8 kB
  • After compression 14.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. 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 54.2 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 15.4 kB

  • Original 556.9 kB
  • After minification 541.4 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. Myg SHOCK images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 121.3 kB

  • Original 192.8 kB
  • After minification 180.7 kB
  • After compression 71.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 121.3 kB or 63% of the original size.

CSS Optimization

-77%

Potential reduce by 110.0 kB

  • Original 142.6 kB
  • After minification 116.4 kB
  • After compression 32.6 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. Mygshock.de needs all CSS files to be minified and compressed as it can save up to 110.0 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (53%)

Requests Now

53

After Optimization

25

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

Accessibility Review

mygshock.de accessibility score

47

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

mygshock.de 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

High

Page has valid source maps

SEO Factors

mygshock.de SEO score

71

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

High

Document doesn't have a valid hreflang

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 doesn't use 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 Mygshock.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 Mygshock.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 Myg SHOCK. 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: