Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

eskenazi.ch

Eskenazi : fabricant d’outils coupants de qualité Swiss Made

Page Load Speed

8.8 sec in total

First Response

287 ms

Resources Loaded

8.1 sec

Page Rendered

506 ms

eskenazi.ch screenshot

About Website

Visit eskenazi.ch now to see the best up-to-date Eskenazi content and also check out these interesting facts you probably never knew about eskenazi.ch

Depuis 1916, Eskenazi SA, entreprise familiale, fabrique des outils de coupe de qualité Swiss Made satisfaisants aux plus hautes exigences.

Visit eskenazi.ch

Key Findings

We analyzed Eskenazi.ch page load time and found that the first response time was 287 ms and then it took 8.6 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

eskenazi.ch performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value19.4 s

0/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value4,210 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

eskenazi.ch

287 ms

www.eskenazi.ch

735 ms

en

414 ms

api.js

45 ms

css

41 ms

Our browser made a total of 215 requests to load all elements on the main page. We found that 91% of them (196 requests) were addressed to the original Eskenazi.ch, 4% (8 requests) were made to Fonts.gstatic.com and 1% (3 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Eskenazi.ch.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (3%)

Content Size

52.3 MB

After Optimization

50.7 MB

In fact, the total size of Eskenazi.ch main page is 52.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 51.7 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 142.6 kB

  • Original 156.3 kB
  • After minification 113.5 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 42.8 kB, which is 27% 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 142.6 kB or 91% of the original size.

Image Optimization

-3%

Potential reduce by 1.5 MB

  • Original 51.7 MB
  • After minification 50.2 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. Eskenazi images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.5 kB

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

CSS Optimization

-0%

Potential reduce by 263 B

  • Original 58.9 kB
  • After minification 58.9 kB
  • After compression 58.7 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. Eskenazi.ch has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (11%)

Requests Now

140

After Optimization

125

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

Accessibility Review

eskenazi.ch accessibility score

72

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

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

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

eskenazi.ch 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

SEO Factors

eskenazi.ch SEO score

79

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eskenazi.ch can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Eskenazi.ch 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 Eskenazi. 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: