Access christofle.com. Silver Flatware & Tableware since 1830

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

christofle.com

339 ms

us.christofle.com

806 ms

1064 ms

css

40 ms

css

62 ms

Our browser made a total of 142 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Christofle.com, 63% (89 requests) were made to Us.christofle.com and 6% (9 requests) were made to Match.adsrvr.org. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Us.christofle.com.

Content Size

4.0 MB

After Optimization

2.3 MB

In fact, the total size of Christofle.com main page is 4.0 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. 75% 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. Javascripts take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 121.3 kB

Original 145.4 kB
After minification 119.9 kB
After compression 24.1 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 25.6 kB, which is 18% 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 121.3 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 7.5 kB

Original 1.7 MB
After minification 1.7 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. Christofle images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 1.3 MB

Original 1.8 MB
After minification 1.6 MB
After compression 484.6 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 1.3 MB or 73% of the original size.

CSS Optimization

-84%

Potential reduce by 288.2 kB

Original 343.5 kB
After minification 275.3 kB
After compression 55.4 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. Christofle.com needs all CSS files to be minified and compressed as it can save up to 288.2 kB or 84% of the original size.

Requests Now

122

After Optimization

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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

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

christofle.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Silver Flatware & Tableware since 1830

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

christofle.com

us.christofle.com

css

css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

christofle.com

us.christofle.com

css

css

style.css

overrides.css

akare.css

jquery-ui-1.10.4.custom.css

jquery-ui-1.10.3.custom.css

jquery.fancybox.css

font-awesome.min.css

bs_leftnavi.css

style.css

jquery.treeview.css

customercredit.css

instantsearch.css

vpager.css

settings.css

dynamic.css

static.css

prototype.js

ccard.js

validation.js

builder.js

effects.js

dragdrop.js

controls.js

slider.js

js.js

form.js

menu.js

translate.js

cookies.js

instantsearch.js

viewinstantsearch.js

jquery-1.7.1-min.js

noconflict.js

jquery.treeview.pack.js

category_tree.js

dd290e845d36d7b70215d9548d2be6a2.js

up_loader.1.1.0.js

bubble.js

jquery-1.11.0.min.js

jquery-migrate-1.2.1.min.js