Tools & Wizards About Us

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

gruyere.com

Le Gruyère AOP - Un savoir-faire artisanal, une tradition depuis 1115

Page Load Speed

5.9 sec in total

First Response

331 ms

Resources Loaded

5.4 sec

Page Rendered

124 ms

About Website

Welcome to gruyere.com homepage info - get ready to check Gruyere best content for Switzerland right away, or after learning these important things about gruyere.com

Bienvenue sur le site du Gruyère AOP. Découvrez les étapes de fabrication de ce fromage traditionnel suisse et testez des recettes authentiques pour le déguster!

Visit gruyere.com

Key Findings

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

Performance Metrics

gruyere.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value16.4 s

0/100

10%

TBT (Total Blocking Time)

Value790 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value25.6 s

0/100

10%

Network Requests Diagram

gruyere.com

331 ms

gruyere.com

444 ms

accueil

1485 ms

news-basic.css

208 ms

merged-411ef8b2612ba460bfb369d2dadfefef-84000df9693bf385fd91185b41e769a4.css

436 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 88% of them (68 requests) were addressed to the original Gruyere.com, 9% (7 requests) were made to Use.typekit.net and 1% (1 request) were made to Platform-api.sharethis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Gruyere.com.

Page Optimization Overview & Recommendations

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

Content Size

4.5 MB

After Optimization

4.3 MB

  • HTML
  • Images
  • CSS

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

HTML Optimization

-87%

Potential reduce by 99.8 kB

  • Original 114.2 kB
  • After minification 87.2 kB
  • After compression 14.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. This page needs HTML code to be minified as it can gain 27.0 kB, which is 24% 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 99.8 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 63.1 kB

  • Original 4.4 MB
  • After minification 4.3 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. Gruyere images are well optimized though.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 B

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.

Requests Breakdown

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

Requests Now

62

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

gruyere.com accessibility score

76

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

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

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

gruyere.com SEO score

86

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 uses legible font sizes

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

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

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