Tools & Wizards About Us
hugel.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

hugel.com

Famille Hugel, Famille Hugel, since 1639 in Riquewihr

Page Load Speed

3.1 sec in total

First Response

222 ms

Resources Loaded

2.4 sec

Page Rendered

553 ms

hugel.com screenshot

About Website

Click here to check amazing Hugel content for France. Otherwise, check out these important facts you probably never knew about hugel.com

Famille Hugel, Famille Hugel, since 1639 in Riquewihr. ...

Visit hugel.com

Key Findings

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

Performance Metrics

hugel.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

28/100

10%

LCP (Largest Contentful Paint)

Value20.5 s

0/100

25%

SI (Speed Index)

Value12.1 s

4/100

10%

TBT (Total Blocking Time)

Value3,410 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value20.1 s

2/100

10%

Network Requests Diagram

hugel.com

222 ms

598DGMB3C4

454 ms

bootstrap.min.css

170 ms

material.min.css

341 ms

ripples.min.css

255 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Hugel.com, 54% (34 requests) were made to M.hugel.com and 19% (12 requests) were made to Cdn.vin.co. The less responsive or slowest element that took the longest time to load (956 ms) relates to the external source Cdn.vin.co.

Page Optimization Overview & Recommendations

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

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 31.0 kB

  • Original 38.4 kB
  • After minification 34.7 kB
  • After compression 7.4 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 31.0 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 29.5 kB

  • Original 1.0 MB
  • After minification 998.2 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. Hugel images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 4.1 kB

  • Original 320.0 kB
  • After minification 320.0 kB
  • After compression 315.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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 2.1 kB

  • Original 128.7 kB
  • After minification 128.7 kB
  • After compression 126.5 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. Hugel.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 33 (62%)

Requests Now

53

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hugel.com

hugel.com

222 ms

598DGMB3C4

598DGMB3C4

454 ms

bootstrap.min.css

bootstrap.min.css

170 ms

material.min.css

material.min.css

341 ms

ripples.min.css

ripples.min.css

255 ms

font-awesome.min.css

font-awesome.min.css

251 ms

ionicons.min.css

ionicons.min.css

256 ms

owl.carousel.min.css

owl.carousel.min.css

255 ms

leaflet.css

leaflet.css

260 ms

Control.Geocoder.css

Control.Geocoder.css

336 ms

style.css

style.css

337 ms

personnalisation.php

personnalisation.php

348 ms

hugel_riquewihrduschoenenbourg_1987_1024.jpg

hugel_riquewihrduschoenenbourg_1987_1024.jpg

956 ms

hugel_img_7035_jpg_13717_1024.jpg

hugel_img_7035_jpg_13717_1024.jpg

955 ms

_logo_famille_hugel_b_12844_640.png

_logo_famille_hugel_b_12844_640.png

791 ms

blank.png

blank.png

335 ms

leaflet.js

leaflet.js

452 ms

Control.Geocoder.min.js

Control.Geocoder.min.js

450 ms

require.min.js

require.min.js

451 ms

cookieinfo.min.js

cookieinfo.min.js

451 ms

JeUS1F_aRm0

JeUS1F_aRm0

161 ms

_hugel_gentil_13750_640.jpg

_hugel_gentil_13750_640.jpg

595 ms

_hugel_classic_13748_640.jpg

_hugel_classic_13748_640.jpg

595 ms

_hugel_gewurtz_estate_2012_etiquette02jpg_14306_640.jpg

_hugel_gewurtz_estate_2012_etiquette02jpg_14306_640.jpg

592 ms

hugel_hugel_tradition_png_12310_640.png

hugel_hugel_tradition_png_12310_640.png

664 ms

hugel_hugel_jubilee_png_12337_640.png

hugel_hugel_jubilee_png_12337_640.png

665 ms

_image_14488_640.jpg

_image_14488_640.jpg

593 ms

_hugel_schoelhammer_13749_640.jpg

_hugel_schoelhammer_13749_640.jpg

664 ms

hugel_gewurztraminervendangetardive_1945_640.jpg

hugel_gewurztraminervendangetardive_1945_640.jpg

664 ms

hugel_rieslingselectiondegrainsnobles_1948_640.jpg

hugel_rieslingselectiondegrainsnobles_1948_640.jpg

662 ms

AjaxLoader.gif

AjaxLoader.gif

113 ms

ionicons.ttf

ionicons.ttf

525 ms

matomo.js

matomo.js

729 ms

config.js

config.js

89 ms

Questrial-Regular.ttf

Questrial-Regular.ttf

478 ms

Questrial-Bold.ttf

Questrial-Bold.ttf

124 ms

www-player.css

www-player.css

6 ms

www-embed-player.js

www-embed-player.js

42 ms

base.js

base.js

85 ms

scripts.js

scripts.js

354 ms

ad_status.js

ad_status.js

286 ms

XRk6eFbYaDme_I9SSIFgFZ9I1nSvAmlSIHv6h58Lfu0.js

XRk6eFbYaDme_I9SSIFgFZ9I1nSvAmlSIHv6h58Lfu0.js

200 ms

embed.js

embed.js

106 ms

jquery.min.js

jquery.min.js

197 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

142 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

143 ms

id

id

34 ms

Create

Create

43 ms

custom-infowindow.min.js

custom-infowindow.min.js

135 ms

modernizr.min.js

modernizr.min.js

136 ms

device.min.js

device.min.js

138 ms

bootstrap.min.js

bootstrap.min.js

137 ms

material.min.js

material.min.js

136 ms

ripples.min.js

ripples.min.js

136 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

235 ms

midnight.min.js

midnight.min.js

235 ms

owl.carousel.min.js

owl.carousel.min.js

237 ms

parallax.min.js

parallax.min.js

236 ms

jquery.columnizer.min.js

jquery.columnizer.min.js

236 ms

matomo.php

matomo.php

122 ms

GenerateIT

GenerateIT

53 ms

qoe

qoe

22 ms

log_event

log_event

1 ms

Accessibility Review

hugel.com accessibility score

92

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

<frame> or <iframe> elements do not have a title

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

hugel.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

hugel.com SEO score

86

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hugel.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 Hugel.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

hugel.com

Open Graph data is detected on the main page of Hugel. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: