Tools & Wizards About Us
comefree.com.tw screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

comefree.com.tw

網路開店 | 網路開店123 | 網路開店平台 | 網路開店課程 | 網路開店系統 | 網路開店比較 | 網路開店價格 | 網路行銷 | SEO

Page Load Speed

8.8 sec in total

First Response

678 ms

Resources Loaded

8 sec

Page Rendered

133 ms

comefree.com.tw screenshot

About Website

Visit comefree.com.tw now to see the best up-to-date Comefree content for Taiwan and also check out these interesting facts you probably never knew about comefree.com.tw

網路開店第一品牌，國際級最專業、最安全、最穩定的網路開店平台，提供多樣化的行銷模組，亦有每週開班、永久免費的教育訓練，降低老闆們初跨電子商務的軟硬體成本！網路開店 | 網路開店123 | 網路開店平台 | 網路開店課程 | 網路開店系統 | 網路開店比較 | 網路開店價格 | 網路行銷 | SEO

Visit comefree.com.tw

Key Findings

We analyzed Comefree.com.tw page load time and found that the first response time was 678 ms and then it took 8.1 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

comefree.com.tw performance score

0

Network Requests Diagram

comefree.com.tw

678 ms

www.comefree.com.tw

1944 ms

shop123_utf8.css

3173 ms

jquery-1.8.3.min.js

2413 ms

chrome.js

1265 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 10% of them (5 requests) were addressed to the original Comefree.com.tw, 75% (36 requests) were made to Fs1.shop123.com.tw and 4% (2 requests) were made to Assets.pinterest.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Fs1.shop123.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 467.8 kB (76%)

Content Size

617.9 kB

After Optimization

150.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 141.3 kB

  • Original 174.9 kB
  • After minification 170.4 kB
  • After compression 33.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 141.3 kB or 81% of the original size.

Image Optimization

-40%

Potential reduce by 11.1 kB

  • Original 28.1 kB
  • After minification 16.9 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. Obviously, Comefree needs image optimization as it can save up to 11.1 kB or 40% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 171.5 kB

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

CSS Optimization

-87%

Potential reduce by 143.9 kB

  • Original 164.8 kB
  • After minification 141.2 kB
  • After compression 20.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. Comefree.com.tw needs all CSS files to be minified and compressed as it can save up to 143.9 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

46

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

comefree.com.tw

comefree.com.tw

678 ms

www.comefree.com.tw

www.comefree.com.tw

1944 ms

shop123_utf8.css

shop123_utf8.css

3173 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

2413 ms

chrome.js

chrome.js

1265 ms

watermark.js

watermark.js

1268 ms

jquery.hoverIntent.js

jquery.hoverIntent.js

1270 ms

jquery.fancybox.css

jquery.fancybox.css

1651 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

1690 ms

jquery.fancybox-buttons.css

jquery.fancybox-buttons.css

1459 ms

jquery.fancybox-buttons.js

jquery.fancybox-buttons.js

1459 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

1852 ms

jquery.fancybox-thumbs.css

jquery.fancybox-thumbs.css

1655 ms

jquery.fancybox-thumbs.js

jquery.fancybox-thumbs.js

1841 ms

jquery.blockUI.js

jquery.blockUI.js

2432 ms

jquery.marquee.min.js

jquery.marquee.min.js

1701 ms

jquery.nextval.js

jquery.nextval.js

2480 ms

shop123Validate.css

shop123Validate.css

1865 ms

alt.js

alt.js

1272 ms

banner.js

banner.js

1752 ms

pinit.js

pinit.js

6 ms

all.js

all.js

252 ms

body_background_image.gif

body_background_image.gif

200 ms

2009298logo_name.jpg

2009298logo_name.jpg

588 ms

20092989slogo_off.png

20092989slogo_off.png

194 ms

20092979slogo_off.png

20092979slogo_off.png

195 ms

website_module_shoping_car_icon.png

website_module_shoping_car_icon.png

395 ms

store_type_left.gif

store_type_left.gif

197 ms

store_type_middle.gif

store_type_middle.gif

392 ms

store_type_right.gif

store_type_right.gif

391 ms

200929137picture_name1454567024.jpg

200929137picture_name1454567024.jpg

3263 ms

link_top_icon.png

link_top_icon.png

393 ms

logo_background_image.gif

logo_background_image.gif

574 ms

ajax_product_module_api.php

ajax_product_module_api.php

295 ms

store_type_background.gif

store_type_background.gif

571 ms

buy_header_header_bottom_extend.gif

buy_header_header_bottom_extend.gif

574 ms

pinit_main.js

pinit_main.js

130 ms

footer_licence_background.gif

footer_licence_background.gif

572 ms

classie.js

classie.js

744 ms

shop123_system_developer.png

shop123_system_developer.png

934 ms

sosa.jpg

sosa.jpg

945 ms

65 ms

xd_arbiter.php

xd_arbiter.php

139 ms

xd_arbiter.php

xd_arbiter.php

264 ms

ajax_product_module_api.php

ajax_product_module_api.php

289 ms

demoa6_open_all_shopcar_close_btn.jpg

demoa6_open_all_shopcar_close_btn.jpg

197 ms

ajax_product_module_api.php

ajax_product_module_api.php

293 ms

ping

ping

43 ms

SEO Factors

comefree.com.tw SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    ZH

  • Encoding

    UTF-8

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

comefree.com.tw

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