Tools & Wizards About Us
joyye.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

joyye.com

Custom Ceramics Homeware, Mugs, Tableware, Cookware Supplier | JOYYE ARTS & CRAFTS CO., LTD.

Page Load Speed

2.8 sec in total

First Response

366 ms

Resources Loaded

1.9 sec

Page Rendered

550 ms

joyye.com screenshot

About Website

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

Joyye, a professional ceramics tableware and homeware supplier from China, we dedicate to providing custom ceramic homeware of multiple crafts focused on quality, for the everyday life of everyone all...

Visit joyye.com

Key Findings

We analyzed Joyye.com page load time and found that the first response time was 366 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

joyye.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value660 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.202

61/100

15%

TTI (Time to Interactive)

Value9.8 s

27/100

10%

Network Requests Diagram

joyye.com

366 ms

joyye.com

318 ms

gqc722t7tp

79 ms

js

108 ms

global.css

74 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 74% of them (50 requests) were addressed to the original Joyye.com, 7% (5 requests) were made to Ueeshop.ly200-cdn.com and 4% (3 requests) were made to Linkedin.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Analytics.ly200.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 187.5 kB (2%)

Content Size

9.0 MB

After Optimization

8.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 57.8 kB

  • Original 67.2 kB
  • After minification 49.5 kB
  • After compression 9.4 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 17.8 kB, which is 26% 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 57.8 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 71.3 kB

  • Original 8.5 MB
  • After minification 8.4 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. JOYYE images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 8.8 kB

  • Original 389.4 kB
  • After minification 389.4 kB
  • After compression 380.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. This website has mostly compressed JavaScripts.

CSS Optimization

-59%

Potential reduce by 49.5 kB

  • Original 83.4 kB
  • After minification 40.1 kB
  • After compression 33.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. Joyye.com needs all CSS files to be minified and compressed as it can save up to 49.5 kB or 59% of the original size.

Requests Breakdown

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

Requests Now

63

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

joyye.com

joyye.com

366 ms

joyye.com

joyye.com

318 ms

gqc722t7tp

gqc722t7tp

79 ms

js

js

108 ms

global.css

global.css

74 ms

themes.css

themes.css

147 ms

user.css

user.css

205 ms

style.css

style.css

208 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

283 ms

en.js

en.js

219 ms

global.js

global.js

219 ms

themes.js

themes.js

228 ms

user.js

user.js

272 ms

main.js

main.js

276 ms

responsive.css

responsive.css

292 ms

font.css

font.css

79 ms

font.css

font.css

87 ms

font.css

font.css

83 ms

jquery.bxslider.js

jquery.bxslider.js

296 ms

jquery.bxslider.css

jquery.bxslider.css

312 ms

analytics.js

analytics.js

1047 ms

in.js

in.js

72 ms

clarity.js

clarity.js

16 ms

b0967e96dd.png

b0967e96dd.png

137 ms

12e7c8007d.jpg

12e7c8007d.jpg

482 ms

d158df1547.jpg

d158df1547.jpg

412 ms

df8f0dc3f5.jpg

df8f0dc3f5.jpg

494 ms

4c8aa49a1b.jpg

4c8aa49a1b.jpg

495 ms

8634dbd42d.jpg

8634dbd42d.jpg

655 ms

c60500864d.jpg

c60500864d.jpg

348 ms

fd0d70f956.jpg

fd0d70f956.jpg

557 ms

d7557fd427.jpg.500x500.jpg

d7557fd427.jpg.500x500.jpg

482 ms

ae94a7e4b8.jpg.500x500.jpg

ae94a7e4b8.jpg.500x500.jpg

548 ms

be342b9e55.jpg.500x500.jpg

be342b9e55.jpg.500x500.jpg

549 ms

9b75618b24.jpg.500x500.jpg

9b75618b24.jpg.500x500.jpg

562 ms

d0298c5771.jpg.500x500.jpg

d0298c5771.jpg.500x500.jpg

564 ms

2c5e5c7561.jpg.500x500.jpg

2c5e5c7561.jpg.500x500.jpg

615 ms

c510ac1524.jpg.500x500.jpg

c510ac1524.jpg.500x500.jpg

617 ms

871ca2dfb5.jpg.500x500.jpg

871ca2dfb5.jpg.500x500.jpg

626 ms

8f9f29e327.jpg

8f9f29e327.jpg

632 ms

9492783596.png

9492783596.png

632 ms

dad353ecf5.jpg

dad353ecf5.jpg

683 ms

720355da06.jpg

720355da06.jpg

686 ms

db9cf8c408.png

db9cf8c408.png

696 ms

close_btn.png

close_btn.png

700 ms

header_search.png

header_search.png

686 ms

search_black.png

search_black.png

715 ms

font.woff

font.woff

111 ms

font.woff

font.woff

104 ms

coffee_img3.png

coffee_img3.png

681 ms

coffe_arrow.png

coffe_arrow.png

685 ms

play_btn.png

play_btn.png

696 ms

location.png

location.png

700 ms

phone.png

phone.png

701 ms

message.png

message.png

736 ms

icon_follow_2.svg

icon_follow_2.svg

748 ms

icon_chat_menu.png

icon_chat_menu.png

752 ms

fbevents.js

fbevents.js

81 ms

coffee_next.png

coffee_next.png

703 ms

coffee_prev.png

coffee_prev.png

706 ms

controls.png

controls.png

707 ms

FollowCompany.js

FollowCompany.js

109 ms

FollowCompany

FollowCompany

1 ms

FollowCompany

FollowCompany

128 ms

6f5ay4wjjgv2mxytnoozqs0bh

6f5ay4wjjgv2mxytnoozqs0bh

21 ms

in.js

in.js

10 ms

cwphtfsvdwm4k6n91alllgs6q

cwphtfsvdwm4k6n91alllgs6q

44 ms

c.gif

c.gif

8 ms

Accessibility Review

joyye.com accessibility score

59

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.

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

joyye.com best practices score

83

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

SEO Factors

joyye.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

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

joyye.com

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