Tools & Wizards About Us
charliemary.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

charliemary.com

CharlieMary | Circular fashion brand from Amsterdam

Page Load Speed

10.8 sec in total

First Response

2 sec

Resources Loaded

8.5 sec

Page Rendered

369 ms

charliemary.com screenshot

About Website

Welcome to charliemary.com homepage info - get ready to check Charlie Mary best content for Netherlands right away, or after learning these important things about charliemary.com

With our season-less collections, we offer classic everyday pieces with a modern and relevant aesthetic. We make comfortable, timeless, high-quality garments that can be worn longer, passed on, and re...

Visit charliemary.com

Key Findings

We analyzed Charliemary.com page load time and found that the first response time was 2 sec and then it took 8.8 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

charliemary.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

charliemary.com

2011 ms

jqtransform.css

87 ms

styles.css

263 ms

widgets.css

251 ms

slider.css

250 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 97% of them (72 requests) were addressed to the original Charliemary.com, 3% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Charliemary.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (32%)

Content Size

3.2 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 62.6 kB

  • Original 73.4 kB
  • After minification 64.4 kB
  • After compression 10.8 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 9.0 kB, which is 12% 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 62.6 kB or 85% of the original size.

Image Optimization

-17%

Potential reduce by 422.9 kB

  • Original 2.5 MB
  • After minification 2.0 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. Obviously, Charlie Mary needs image optimization as it can save up to 422.9 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-76%

Potential reduce by 425.0 kB

  • Original 555.7 kB
  • After minification 427.8 kB
  • After compression 130.7 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 425.0 kB or 76% of the original size.

CSS Optimization

-84%

Potential reduce by 127.8 kB

  • Original 151.6 kB
  • After minification 120.5 kB
  • After compression 23.8 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. Charliemary.com needs all CSS files to be minified and compressed as it can save up to 127.8 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

73

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

charliemary.com

charliemary.com

2011 ms

jqtransform.css

jqtransform.css

87 ms

styles.css

styles.css

263 ms

widgets.css

widgets.css

251 ms

slider.css

slider.css

250 ms

jquery.js

jquery.js

1108 ms

prototype.js

prototype.js

377 ms

ccard.js

ccard.js

1017 ms

validation.js

validation.js

333 ms

builder.js

builder.js

330 ms

effects.js

effects.js

350 ms

dragdrop.js

dragdrop.js

415 ms

controls.js

controls.js

417 ms

slider.js

slider.js

435 ms

js.js

js.js

468 ms

form.js

form.js

498 ms

script.js

script.js

499 ms

menu.js

menu.js

519 ms

translate.js

translate.js

559 ms

cookies.js

cookies.js

583 ms

func.js

func.js

582 ms

jquery.jqtransform.js

jquery.jqtransform.js

603 ms

jquery.easing.1.3.min.js

jquery.easing.1.3.min.js

649 ms

jquery.slider.js

jquery.slider.js

670 ms

efects.js

efects.js

664 ms

menu1.css

menu1.css

687 ms

easyzoom.js

easyzoom.js

743 ms

easyzoom.css

easyzoom.css

745 ms

ga.js

ga.js

56 ms

logo.gif

logo.gif

127 ms

homeSYOU.jpg

homeSYOU.jpg

452 ms

maywunderwerk.png

maywunderwerk.png

126 ms

vejaV10.jpg

vejaV10.jpg

408 ms

O-My-Bag.jpg

O-My-Bag.jpg

278 ms

file_name_37.jpg

file_name_37.jpg

125 ms

file_name_423.jpg

file_name_423.jpg

177 ms

file_name_409.jpg

file_name_409.jpg

175 ms

file_name_308.jpg

file_name_308.jpg

188 ms

file_name_435.jpg

file_name_435.jpg

258 ms

file_name_430.jpg

file_name_430.jpg

261 ms

file_name_397.jpg

file_name_397.jpg

275 ms

file_name_377.jpg

file_name_377.jpg

337 ms

file_name_381.jpg

file_name_381.jpg

351 ms

file_name_373.jpg

file_name_373.jpg

365 ms

gift.png

gift.png

366 ms

telephone.png

telephone.png

417 ms

paypal.png

paypal.png

435 ms

discover.png

discover.png

457 ms

visa_straight.png

visa_straight.png

456 ms

aex.png

aex.png

482 ms

mastercard.png

mastercard.png

499 ms

maestro.png

maestro.png

519 ms

shopping_bag.png

shopping_bag.png

516 ms

line2.png

line2.png

533 ms

toplinksap.png

toplinksap.png

532 ms

controls-sprite.png

controls-sprite.png

546 ms

slide_prev.png

slide_prev.png

563 ms

slide_next.png

slide_next.png

586 ms

new.png

new.png

605 ms

proximanova.otf

proximanova.otf

692 ms

WPAPI.php

WPAPI.php

3750 ms

__utm.gif

__utm.gif

55 ms

facebook.png

facebook.png

587 ms

twitter.png

twitter.png

602 ms

instagram.png

instagram.png

628 ms

pinterest.png

pinterest.png

652 ms

line.png

line.png

613 ms

footer_li.png

footer_li.png

634 ms

menu-icon.png

menu-icon.png

652 ms

springessentials21.jpg

springessentials21.jpg

253 ms

runway.png

runway.png

796 ms

Screen-Shot-2016-02-17-at-13.11.52.png

Screen-Shot-2016-02-17-at-13.11.52.png

723 ms

dixansdamour_2_1.jpg

dixansdamour_2_1.jpg

327 ms

print.css

print.css

96 ms

Accessibility Review

charliemary.com accessibility score

97

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

Links do not have a discernible name

Best Practices

charliemary.com best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

charliemary.com SEO score

80

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    NL

  • Encoding

    UTF-8

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

charliemary.com

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