Tools & Wizards About Us
chedeville.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

chedeville.com

Chedeville - Crafting The Finest Clarinet Mouthpieces Worldwide

Page Load Speed

23 sec in total

First Response

151 ms

Resources Loaded

21.9 sec

Page Rendered

910 ms

chedeville.com screenshot

About Website

Click here to check amazing Chedeville content. Otherwise, check out these important facts you probably never knew about chedeville.com

Making the best Clarinet mouthpieces with new world technology and old-world craftsmanship, consistently for Classical musicians.

Visit chedeville.com

Key Findings

We analyzed Chedeville.com page load time and found that the first response time was 151 ms and then it took 22.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

chedeville.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value1,750 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

chedeville.com

151 ms

mediaelementplayer-legacy.min.css

167 ms

wp-mediaelement.min.css

249 ms

views-frontend.css

305 ms

settings.css

306 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 74% of them (48 requests) were addressed to the original Chedeville.com, 9% (6 requests) were made to B1494196.smushcdn.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Stats1.wpmudev.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 203.6 kB (29%)

Content Size

690.4 kB

After Optimization

486.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Chedeville.com main page is 690.4 kB. 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 416.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 203.3 kB

  • Original 242.2 kB
  • After minification 233.5 kB
  • After compression 38.9 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 203.3 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 88 B

  • Original 416.5 kB
  • After minification 416.4 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. Chedeville images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 183 B

  • Original 31.7 kB
  • After minification 31.7 kB
  • After compression 31.5 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.

Requests Breakdown

Number of requests can be reduced by 46 (79%)

Requests Now

58

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

chedeville.com

chedeville.com

151 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

167 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

249 ms

views-frontend.css

views-frontend.css

305 ms

settings.css

settings.css

306 ms

fontello.css

fontello.css

276 ms

css

css

48 ms

css

css

59 ms

css

css

65 ms

gateway.css

gateway.css

274 ms

sv-wc-payment-gateway-payment-form.min.css

sv-wc-payment-gateway-payment-form.min.css

310 ms

wc-cybersource.min.css

wc-cybersource.min.css

409 ms

flatsome.css

flatsome.css

474 ms

flatsome-shop.css

flatsome-shop.css

496 ms

toolset-common-es-frontend.js

toolset-common-es-frontend.js

373 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

464 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

481 ms

wp-polyfill.min.js

wp-polyfill.min.js

598 ms

hooks.min.js

hooks.min.js

552 ms

w.js

w.js

34 ms

jquery.min.js

jquery.min.js

773 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

625 ms

add-to-cart.min.js

add-to-cart.min.js

639 ms

js.cookie.min.js

js.cookie.min.js

641 ms

woocommerce.min.js

woocommerce.min.js

704 ms

sourcebuster.min.js

sourcebuster.min.js

986 ms

order-attribution.min.js

order-attribution.min.js

984 ms

button.js

button.js

995 ms

flatsome-live-search.js

flatsome-live-search.js

995 ms

hoverIntent.min.js

hoverIntent.min.js

994 ms

flatsome.js

flatsome.js

994 ms

flatsome-cookie-notice.js

flatsome-cookie-notice.js

995 ms

jquery.payment.min.js

jquery.payment.min.js

993 ms

sv-wc-payment-gateway-payment-form.js

sv-wc-payment-gateway-payment-form.js

1166 ms

wc-cybersource.min.js

wc-cybersource.min.js

1188 ms

smush-lazy-load-native.min.js

smush-lazy-load-native.min.js

1069 ms

woocommerce.js

woocommerce.js

1122 ms

cart-fragments.min.js

cart-fragments.min.js

1064 ms

packery.pkgd.min.js

packery.pkgd.min.js

1185 ms

aweber-wpn-script.js

aweber-wpn-script.js

1272 ms

g.gif

g.gif

18 ms

gtm.js

gtm.js

291 ms

Chedeville-Branding-background.jpg

Chedeville-Branding-background.jpg

293 ms

Chedeville_BlueVelvet-1R.jpg

Chedeville_BlueVelvet-1R.jpg

143 ms

S6uyw4BMUTPHjx4wWCWtFCc.woff

S6uyw4BMUTPHjx4wWCWtFCc.woff

290 ms

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

289 ms

S6u9w4BMUTPHh6UVSwiPHw3q5d0.woff

S6u9w4BMUTPHh6UVSwiPHw3q5d0.woff

371 ms

S6u9w4BMUTPHh6UVSwaPHw3q5d0N7w.woff

S6u9w4BMUTPHh6UVSwaPHw3q5d0N7w.woff

370 ms

fl-icons.ttf

fl-icons.ttf

415 ms

736618534.js

736618534.js

143 ms

analytics.js

analytics.js

117 ms

js

js

154 ms

20444 ms

displays.htm

displays.htm

106 ms

chedeville_dark_logo.png

chedeville_dark_logo.png

78 ms

AJodyJazzCompany_PNG.gif

AJodyJazzCompany_PNG.gif

54 ms

Chedeville_White_Life.png

Chedeville_White_Life.png

51 ms

smush-placeholder.png

smush-placeholder.png

132 ms

chedeville.com

chedeville.com

1039 ms

flatsome.js

flatsome.js

222 ms

chunk.slider.js

chunk.slider.js

193 ms

chunk.popups.js

chunk.popups.js

187 ms

chunk.tooltips.js

chunk.tooltips.js

203 ms

woocommerce.js

woocommerce.js

193 ms

kanter_cinema_clarinet_angle.jpg

kanter_cinema_clarinet_angle.jpg

76 ms

Accessibility Review

chedeville.com accessibility score

94

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best Practices

chedeville.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

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

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 doesn't use 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 Chedeville.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 Chedeville.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

chedeville.com

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