Tools & Wizards About Us
yollyware.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

yollyware.com

YOLLY｜Natural Bamboo Fiber Straw｜Plant Fiber International Inc.

Page Load Speed

39.3 sec in total

First Response

4.7 sec

Resources Loaded

33.8 sec

Page Rendered

851 ms

yollyware.com screenshot

About Website

Welcome to yollyware.com homepage info - get ready to check YOLLY Ware best content right away, or after learning these important things about yollyware.com

YOLLY Natural Bamboo Fiber Straw is the most eco-friendly straws in the world. 100% Natural Bamboo Fiber, Plastic-Free, Biodegradable, Combustible, Chemical-Free, Made in Taiwan. With more than 30 yea...

Visit yollyware.com

Key Findings

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

Performance Metrics

yollyware.com performance score

0

Network Requests Diagram

4651 ms

wp-emoji-release.min.js

637 ms

style.min.css

2189 ms

styles.css

654 ms

woocommerce-layout.css

651 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 94% of them (67 requests) were addressed to the original Yollyware.com, 4% (3 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (15.4 sec) belongs to the original domain Yollyware.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.0 MB (60%)

Content Size

5.1 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yollyware.com main page is 5.1 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. 40% of websites need less resources to load. CSS take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 217.2 kB

  • Original 251.1 kB
  • After minification 247.9 kB
  • After compression 33.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 217.2 kB or 86% of the original size.

Image Optimization

-2%

Potential reduce by 25.6 kB

  • Original 1.6 MB
  • After minification 1.5 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. YOLLY Ware images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 1.1 MB

  • Original 1.3 MB
  • After minification 1.1 MB
  • After compression 250.2 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 1.1 MB or 81% of the original size.

CSS Optimization

-88%

Potential reduce by 1.7 MB

  • Original 2.0 MB
  • After minification 1.8 MB
  • After compression 235.6 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. Yollyware.com needs all CSS files to be minified and compressed as it can save up to 1.7 MB or 88% of the original size.

Requests Breakdown

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

Requests Now

61

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

4651 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

637 ms

style.min.css

style.min.css

2189 ms

styles.css

styles.css

654 ms

woocommerce-layout.css

woocommerce-layout.css

651 ms

woocommerce.css

woocommerce.css

2205 ms

rgs.css

rgs.css

669 ms

font-awesome.min.css

font-awesome.min.css

1076 ms

yollystye.css

yollystye.css

15382 ms

jquery.fancybox.css

jquery.fancybox.css

1114 ms

responsive.css

responsive.css

1721 ms

nectar-slider.css

nectar-slider.css

2445 ms

woocommerce.css

woocommerce.css

1950 ms

select2.css

select2.css

2168 ms

skin-material.css

skin-material.css

2885 ms

js_composer.min.css

js_composer.min.css

7040 ms

css

css

33 ms

jquery.js

jquery.js

2872 ms

jquery-migrate.min.js

jquery-migrate.min.js

2889 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

2919 ms

add-to-cart.min.js

add-to-cart.min.js

3095 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

3109 ms

animate.min.css

animate.min.css

646 ms

scripts.js

scripts.js

673 ms

js.cookie.min.js

js.cookie.min.js

849 ms

woocommerce.min.js

woocommerce.min.js

865 ms

jquery.cookie.min.js

jquery.cookie.min.js

869 ms

cart-fragments.min.js

cart-fragments.min.js

897 ms

priority.js

priority.js

1075 ms

modernizr.js

modernizr.js

1091 ms

imagesLoaded.min.js

imagesLoaded.min.js

1093 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

1344 ms

superfish.js

superfish.js

1298 ms

init.js

init.js

3119 ms

nectar-slider.js

nectar-slider.js

1778 ms

touchswipe.min.js

touchswipe.min.js

1521 ms

select2.full.min.js

select2.full.min.js

1790 ms

wp-embed.min.js

wp-embed.min.js

1743 ms

js_composer_front.min.js

js_composer_front.min.js

1970 ms

yolly_header_logo_dark.png

yolly_header_logo_dark.png

1089 ms

yolly_header_logo_light_retina.png

yolly_header_logo_light_retina.png

1177 ms

yolly_icon_1.png

yolly_icon_1.png

1185 ms

yolly_icon_2.png

yolly_icon_2.png

1725 ms

yolly_icon_3.png

yolly_icon_3.png

1317 ms

yolly_icon_4a.png

yolly_icon_4a.png

1572 ms

yolly_icon_5.png

yolly_icon_5.png

1576 ms

yolly_icon_6.png

yolly_icon_6.png

1403 ms

yolly_home_1.jpg

yolly_home_1.jpg

1646 ms

yolly_home_2-1.jpg

yolly_home_2-1.jpg

1772 ms

yolly_home_tableware.jpg

yolly_home_tableware.jpg

8944 ms

yolly_home_turtle_mobile-1.jpg

yolly_home_turtle_mobile-1.jpg

4451 ms

yolly_home_reddot-1.jpg

yolly_home_reddot-1.jpg

8097 ms

yolly_home_reddot_mobile-1.jpg

yolly_home_reddot_mobile-1.jpg

3763 ms

footer_logo.png

footer_logo.png

1936 ms

yolly_home_slider.jpg

yolly_home_slider.jpg

2485 ms

home_splash4.jpg

home_splash4.jpg

3185 ms

home_splash3-1.jpg

home_splash3-1.jpg

3691 ms

9709 ms

yolly_home_turtle-1.jpg

yolly_home_turtle-1.jpg

4154 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

35 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

4128 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

255 ms

OpenSans-Light-webfont.woff

OpenSans-Light-webfont.woff

4313 ms

OpenSans-Semibold-webfont.woff

OpenSans-Semibold-webfont.woff

4359 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

255 ms

OpenSansBold-webfont.woff

OpenSansBold-webfont.woff

5919 ms

icomoon.woff

icomoon.woff

5892 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

12393 ms

6471 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

234 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

452 ms

SEO Factors

yollyware.com SEO score

0

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

yollyware.com

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