Tools & Wizards About Us
krug.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% 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

  • 77

    SEO

    Google-friendlier than
    36% of websites

krug.com

Krug Champagne | Only Prestige Champagnes since 1843

Page Load Speed

2.7 sec in total

First Response

529 ms

Resources Loaded

2 sec

Page Rendered

178 ms

krug.com screenshot

About Website

Visit krug.com now to see the best up-to-date Krug content for United States and also check out these interesting facts you probably never knew about krug.com

Discover Krug, the first and still unique Champagne House to create only prestige Champagnes every year since its foundation in 1843.

Visit krug.com

Key Findings

We analyzed Krug.com page load time and found that the first response time was 529 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

krug.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value25.2 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value1,840 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.091

92/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

Network Requests Diagram

krug_sas

529 ms

asap.js

35 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

60 ms

css_G1GBTxRiM8VBpaHsmVvPZbcww0AkgIvoqzRmvyFXA2Q.css

57 ms

css_VuvLEzCdwg-srK1j60-TgoWtmcck7zzZqQ1NigWXqaE.css

61 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 71% of them (22 requests) were addressed to the original Krug.com, 13% (4 requests) were made to C.betrad.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (582 ms) belongs to the original domain Krug.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 829.4 kB (69%)

Content Size

1.2 MB

After Optimization

374.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Krug.com main page is 1.2 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. Javascripts take 665.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 47.2 kB

  • Original 59.0 kB
  • After minification 57.0 kB
  • After compression 11.8 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 47.2 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 2.2 kB

  • Original 154.9 kB
  • After minification 152.7 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. Krug images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 499.7 kB

  • Original 665.0 kB
  • After minification 509.3 kB
  • After compression 165.3 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 499.7 kB or 75% of the original size.

CSS Optimization

-86%

Potential reduce by 280.3 kB

  • Original 324.9 kB
  • After minification 320.2 kB
  • After compression 44.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. Krug.com needs all CSS files to be minified and compressed as it can save up to 280.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (57%)

Requests Now

23

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

krug_sas

krug_sas

529 ms

asap.js

asap.js

35 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

60 ms

css_G1GBTxRiM8VBpaHsmVvPZbcww0AkgIvoqzRmvyFXA2Q.css

css_G1GBTxRiM8VBpaHsmVvPZbcww0AkgIvoqzRmvyFXA2Q.css

57 ms

css_VuvLEzCdwg-srK1j60-TgoWtmcck7zzZqQ1NigWXqaE.css

css_VuvLEzCdwg-srK1j60-TgoWtmcck7zzZqQ1NigWXqaE.css

61 ms

css_lDo32qBsHGIJ_WllU7-R3sDdT6gz8dT2ID-aYpna6Gc.css

css_lDo32qBsHGIJ_WllU7-R3sDdT6gz8dT2ID-aYpna6Gc.css

103 ms

js_BocpO7oV2V9m_et9Sfy-yRJG7oHvwVFyyZ9yKoQrDBM.js

js_BocpO7oV2V9m_et9Sfy-yRJG7oHvwVFyyZ9yKoQrDBM.js

188 ms

js_6YDTYQ9c_unj2AqmAl04z-XzMu-2zEBI8xTmpnmaOvI.js

js_6YDTYQ9c_unj2AqmAl04z-XzMu-2zEBI8xTmpnmaOvI.js

164 ms

js_h7gjVV5QN4m_Zp3gMk-iwTDD_DmUsP4lMZ2SgMk8Wxs.js

js_h7gjVV5QN4m_Zp3gMk-iwTDD_DmUsP4lMZ2SgMk8Wxs.js

204 ms

all.min.js

all.min.js

216 ms

css

css

54 ms

widgets.js

widgets.js

149 ms

gtm.js

gtm.js

235 ms

select-cursor.png

select-cursor.png

139 ms

krug-1-sba62062af2.png

krug-1-sba62062af2.png

139 ms

logo_consignesdetri.png

logo_consignesdetri.png

139 ms

AGaramondPro-Regular.otf

AGaramondPro-Regular.otf

159 ms

AGaramondPro-Bold.otf

AGaramondPro-Bold.otf

490 ms

h1.js

h1.js

180 ms

sas.jpg

sas.jpg

119 ms

hp-slides-logo.png

hp-slides-logo.png

83 ms

Gotham-Medium.otf

Gotham-Medium.otf

115 ms

Gotham-Book.otf

Gotham-Book.otf

92 ms

Gotham-Bold.otf

Gotham-Bold.otf

86 ms

AGaramondPro-Italic.otf

AGaramondPro-Italic.otf

239 ms

AGaramondPro-BoldItalic.otf

AGaramondPro-BoldItalic.otf

582 ms

analytics.js

analytics.js

47 ms

3657.js

3657.js

59 ms

ric-close.png

ric-close.png

17 ms

bg1.png

bg1.png

42 ms

collect

collect

67 ms

Accessibility Review

krug.com accessibility score

66

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Some elements have a [tabindex] value greater than 0

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

krug.com best practices score

67

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

krug.com SEO score

77

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

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Krug.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Krug.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

krug.com

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