Tools & Wizards About Us
charmex.cc screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 42

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

charmex.cc

首页-企业官网

Page Load Speed

6.2 sec in total

First Response

757 ms

Resources Loaded

4.8 sec

Page Rendered

668 ms

charmex.cc screenshot

About Website

Welcome to charmex.cc homepage info - get ready to check Charmex best content right away, or after learning these important things about charmex.cc

Visit charmex.cc

Key Findings

We analyzed Charmex.cc page load time and found that the first response time was 757 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

charmex.cc performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value1,170 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

charmex.cc

757 ms

30536_zh-cn.html.Head.js

1103 ms

30536_zh-cn.html.Body.js

1857 ms

pcstyle.css

112 ms

reset.css

116 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Charmex.cc, 99% (99 requests) were made to Nwzimg.wezhan.cn. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Nwzimg.wezhan.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 502.1 kB (11%)

Content Size

4.4 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Charmex.cc main page is 4.4 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. Only a small number of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 266.7 kB

  • Original 301.3 kB
  • After minification 273.5 kB
  • After compression 34.6 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 266.7 kB or 89% of the original size.

Image Optimization

-4%

Potential reduce by 164.6 kB

  • Original 3.8 MB
  • After minification 3.6 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. Charmex images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 50.3 kB

  • Original 222.8 kB
  • After minification 217.6 kB
  • After compression 172.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 50.3 kB or 23% of the original size.

CSS Optimization

-44%

Potential reduce by 20.4 kB

  • Original 46.8 kB
  • After minification 39.8 kB
  • After compression 26.3 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. Charmex.cc needs all CSS files to be minified and compressed as it can save up to 20.4 kB or 44% of the original size.

Requests Breakdown

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

Requests Now

97

After Optimization

71

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

charmex.cc

charmex.cc

757 ms

30536_zh-cn.html.Head.js

30536_zh-cn.html.Head.js

1103 ms

30536_zh-cn.html.Body.js

30536_zh-cn.html.Body.js

1857 ms

pcstyle.css

pcstyle.css

112 ms

reset.css

reset.css

116 ms

iconfont.css

iconfont.css

129 ms

iconfont.css

iconfont.css

113 ms

iconfont.css

iconfont.css

114 ms

pager.css

pager.css

224 ms

hover-effects.css

hover-effects.css

215 ms

antChain.css

antChain.css

217 ms

30536_Pc_zh-CN.css

30536_Pc_zh-CN.css

511 ms

jquery-3.6.3.min.js

jquery-3.6.3.min.js

217 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

228 ms

smart.animation.min.js

smart.animation.min.js

317 ms

kino.razor.min.js

kino.razor.min.js

317 ms

common.min.js

common.min.js

690 ms

admin.validator.min.js

admin.validator.min.js

323 ms

jquery.cookie.js

jquery.cookie.js

330 ms

jssor.slider-22.2.16-all.min.js

jssor.slider-22.2.16-all.min.js

441 ms

jquery.jqueryzoom.js

jquery.jqueryzoom.js

418 ms

slideshow.js

slideshow.js

424 ms

jqPaginator.min.js

jqPaginator.min.js

434 ms

polyfill.min.js

polyfill.min.js

105 ms

slicknav.css

slicknav.css

106 ms

jquery.slicknav.min.js

jquery.slicknav.min.js

379 ms

modernizr.min.js

modernizr.min.js

103 ms

ResponsiveJsLoader.js

ResponsiveJsLoader.js

829 ms

41376977.png

41376977.png

106 ms

42529823.png

42529823.png

108 ms

41400258.jpg

41400258.jpg

123 ms

41476238.jpg

41476238.jpg

122 ms

41483676.jpg

41483676.jpg

112 ms

41476291.jpg

41476291.jpg

107 ms

41476316.jpg

41476316.jpg

217 ms

41476150.jpg

41476150.jpg

217 ms

41506863.jpg

41506863.jpg

237 ms

41506905.png

41506905.png

253 ms

41506410.jpg

41506410.jpg

234 ms

41506409.png

41506409.png

234 ms

41506402.jpg

41506402.jpg

313 ms

41505935.jpg

41505935.jpg

325 ms

41505874.jpg

41505874.jpg

402 ms

41505762.jpg

41505762.jpg

342 ms

41505846.jpg

41505846.jpg

345 ms

41484618.jpg

41484618.jpg

400 ms

41484610.png

41484610.png

442 ms

41484585.jpg

41484585.jpg

460 ms

41484566.jpg

41484566.jpg

450 ms

41484536.jpg

41484536.jpg

510 ms

41484416.jpg

41484416.jpg

509 ms

41484398.jpg

41484398.jpg

515 ms

41484379.jpg

41484379.jpg

557 ms

41484364.jpg

41484364.jpg

558 ms

41484352.jpg

41484352.jpg

563 ms

41484340.jpg

41484340.jpg

614 ms

41484325.jpg

41484325.jpg

620 ms

41484321.jpg

41484321.jpg

653 ms

41496318.jpg

41496318.jpg

595 ms

iconfont.woff

iconfont.woff

105 ms

iconfont.woff

iconfont.woff

103 ms

41496286.jpg

41496286.jpg

578 ms

41496258.jpg

41496258.jpg

577 ms

41496246.jpg

41496246.jpg

626 ms

41496191.jpg

41496191.jpg

635 ms

41496166.jpg

41496166.jpg

673 ms

41496134.jpg

41496134.jpg

664 ms

41496092.jpg

41496092.jpg

673 ms

41495969.jpg

41495969.jpg

582 ms

41495657.png

41495657.png

643 ms

41493347.jpg

41493347.jpg

629 ms

41493108.jpg

41493108.jpg

654 ms

41493253.jpg

41493253.jpg

651 ms

41493078.jpg

41493078.jpg

663 ms

41493052.jpg

41493052.jpg

664 ms

41494723.jpg

41494723.jpg

705 ms

41494721.jpg

41494721.jpg

647 ms

41494672.jpg

41494672.jpg

686 ms

41494620.jpg

41494620.jpg

647 ms

41494482.jpg

41494482.jpg

672 ms

41494452.jpg

41494452.jpg

636 ms

41494443.jpg

41494443.jpg

659 ms

41505202.jpg

41505202.jpg

663 ms

41496320.jpg

41496320.jpg

664 ms

41496290.jpg

41496290.jpg

678 ms

41400211.jpg

41400211.jpg

683 ms

41455878.jpg

41455878.jpg

627 ms

41456044.jpg

41456044.jpg

659 ms

41409066.jpg

41409066.jpg

654 ms

41446781.jpg

41446781.jpg

662 ms

41473499.png

41473499.png

742 ms

41473497.png

41473497.png

680 ms

41399217.jpg

41399217.jpg

634 ms

no-data.png

no-data.png

104 ms

41380937.jpeg

41380937.jpeg

620 ms

41382119.png

41382119.png

616 ms

41389169.png

41389169.png

647 ms

41389168.png

41389168.png

667 ms

ga_icon.png

ga_icon.png

104 ms

Core-Babeled.js

Core-Babeled.js

291 ms

Accessibility Review

charmex.cc accessibility score

42

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

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

charmex.cc 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

charmex.cc SEO score

67

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

High

Tap targets are not sized appropriately

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 Charmex.cc 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 Charmex.cc 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

charmex.cc

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