Tools & Wizards About Us
charliechoe.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

charliechoe.com

Charlie Choe Sleepwear - thé best brand for comfortable sleepwear - Charlie Choe Sleepwear

Page Load Speed

3.1 sec in total

First Response

132 ms

Resources Loaded

2.6 sec

Page Rendered

306 ms

charliechoe.com screenshot

About Website

Visit charliechoe.com now to see the best up-to-date Charlie Choe content and also check out these interesting facts you probably never knew about charliechoe.com

Charlie Choe is the brand where you can buy comfortable pyjama sets, pyjama pants, pyjama shorts or nightshirts that not only looks good, but also offers the mo

Visit charliechoe.com

Key Findings

We analyzed Charliechoe.com page load time and found that the first response time was 132 ms and then it took 3 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

charliechoe.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value2,050 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

charliechoe.com

132 ms

300 ms

gtm.js

77 ms

powr.js

56 ms

capi.js

546 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 9% of them (6 requests) were addressed to the original Charliechoe.com, 36% (24 requests) were made to Cdn.webshopapp.com and 21% (14 requests) were made to Sdk.beeketing.com. The less responsive or slowest element that took the longest time to load (711 ms) relates to the external source Hidevariants.cmdcbv.app.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.4 kB (8%)

Content Size

796.3 kB

After Optimization

731.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Charliechoe.com main page is 796.3 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. 65% of websites need less resources to load. Javascripts take 509.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 62.3 kB

  • Original 79.6 kB
  • After minification 78.3 kB
  • After compression 17.3 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 62.3 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 162 B

  • Original 183.5 kB
  • After minification 183.3 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. Charlie Choe images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.2 kB

  • Original 509.7 kB
  • After minification 509.7 kB
  • After compression 507.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.

CSS Optimization

-3%

Potential reduce by 671 B

  • Original 23.5 kB
  • After minification 23.5 kB
  • After compression 22.9 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. Charliechoe.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 41 (66%)

Requests Now

62

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Charlie Choe. 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 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

charliechoe.com

charliechoe.com

132 ms

300 ms

gtm.js

gtm.js

77 ms

powr.js

powr.js

56 ms

capi.js

capi.js

546 ms

css

css

50 ms

gui-2-0.css

gui-2-0.css

60 ms

gui-responsive-2-0.css

gui-responsive-2-0.css

75 ms

fixed.css

fixed.css

100 ms

screen.css

screen.css

103 ms

custom.css

custom.css

103 ms

trustpilot.css

trustpilot.css

100 ms

jquery-1-9-1.js

jquery-1-9-1.js

101 ms

jquery-ui-1-10-1.js

jquery-ui-1-10-1.js

108 ms

tp.widget.sync.bootstrap.min.js

tp.widget.sync.bootstrap.min.js

37 ms

email-decode.min.js

email-decode.min.js

16 ms

instafeed-min.js

instafeed-min.js

102 ms

scripts.js

scripts.js

102 ms

custom.js

custom.js

104 ms

gui.js

gui.js

104 ms

gui-responsive-2-0.js

gui-responsive-2-0.js

104 ms

conversion.js

conversion.js

105 ms

fbevents.js

fbevents.js

153 ms

285 ms

charlie-choe.svg

charlie-choe.svg

96 ms

fff

fff

218 ms

flag-en.svg

flag-en.svg

93 ms

flag-nl.svg

flag-nl.svg

131 ms

flag-de.svg

flag-de.svg

132 ms

hero-1-image.jpg

hero-1-image.jpg

133 ms

hero-1-image-mobile.jpg

hero-1-image-mobile.jpg

94 ms

logo-dirkje.png

logo-dirkje.png

130 ms

logo-kokonoko.png

logo-kokonoko.png

132 ms

logo-charlie-choe.png

logo-charlie-choe.png

130 ms

logo-nowaymonday.png

logo-nowaymonday.png

140 ms

fff

fff

227 ms

fff

fff

241 ms

fff

fff

241 ms

hotjar-2279755.js

hotjar-2279755.js

221 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

59 ms

icomoon.woff

icomoon.woff

44 ms

pageview.js

pageview.js

169 ms

awAddGift.js

awAddGift.js

86 ms

beeketing.js

beeketing.js

105 ms

147536.js

147536.js

380 ms

hidevariants-147536.js

hidevariants-147536.js

711 ms

stocknotifier-147536.js

stocknotifier-147536.js

706 ms

83 ms

recent

recent

131 ms

modules.e4b2dc39f985f11fb1e4.js

modules.e4b2dc39f985f11fb1e4.js

31 ms

main.js

main.js

18 ms

trackingUser

trackingUser

412 ms

75 ms

beeketing.0.41fa4b0af8d6bfceac2f.js

beeketing.0.41fa4b0af8d6bfceac2f.js

21 ms

beeketing.1.19d05760fa520b2970db.js

beeketing.1.19d05760fa520b2970db.js

34 ms

beeketing.3.f475d5839949f0aad803.js

beeketing.3.f475d5839949f0aad803.js

36 ms

beeketing.131.849372d45e7048adcda7.js

beeketing.131.849372d45e7048adcda7.js

41 ms

MjEwYjYwMWFjMzc2MTFmNDgzMDE2NjUzMWYxZGZjZGE=.json

MjEwYjYwMWFjMzc2MTFmNDgzMDE2NjUzMWYxZGZjZGE=.json

353 ms

production.json

production.json

314 ms

beeketing.2.3aab4f57ef969e00a765.js

beeketing.2.3aab4f57ef969e00a765.js

11 ms

beeketing.150.c8d8305b8b8e32636123.js

beeketing.150.c8d8305b8b8e32636123.js

10 ms

beeketing.4.67e85ab2118d84d145e1.js

beeketing.4.67e85ab2118d84d145e1.js

44 ms

beeketing.5.06fa403dbf56b868780b.js

beeketing.5.06fa403dbf56b868780b.js

43 ms

beeketing.134.ddc640b2f2def30266a8.js

beeketing.134.ddc640b2f2def30266a8.js

84 ms

9462053

9462053

108 ms

styles.css

styles.css

32 ms

beeketing.142.a5108606e31d364dbaf7.js

beeketing.142.a5108606e31d364dbaf7.js

56 ms

Accessibility Review

charliechoe.com accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

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

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

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

charliechoe.com SEO score

85

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

charliechoe.com

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