Tools & Wizards About Us
kinaz.com.tw screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

kinaz.com.tw

KINAZ

Page Load Speed

11.1 sec in total

First Response

1.3 sec

Resources Loaded

9.5 sec

Page Rendered

247 ms

kinaz.com.tw screenshot

About Website

Welcome to kinaz.com.tw homepage info - get ready to check KINAZ best content for Taiwan right away, or after learning these important things about kinaz.com.tw

松本澤國際有限公司

Visit kinaz.com.tw

Key Findings

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

Performance Metrics

kinaz.com.tw performance score

0

Network Requests Diagram

www.kinaz.com.tw

1302 ms

public.js

1395 ms

JsLoader.js

532 ms

xajax.js

1174 ms

xajax_extend.js

745 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 83% of them (65 requests) were addressed to the original Kinaz.com.tw, 3% (2 requests) were made to Googleads.g.doubleclick.net and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Kinaz.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 732.8 kB (18%)

Content Size

4.0 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 29.5 kB

  • Original 37.7 kB
  • After minification 36.1 kB
  • After compression 8.2 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 29.5 kB or 78% of the original size.

Image Optimization

-13%

Potential reduce by 474.0 kB

  • Original 3.6 MB
  • After minification 3.2 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, KINAZ needs image optimization as it can save up to 474.0 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-57%

Potential reduce by 174.3 kB

  • Original 306.1 kB
  • After minification 272.6 kB
  • After compression 131.8 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 174.3 kB or 57% of the original size.

CSS Optimization

-84%

Potential reduce by 55.0 kB

  • Original 65.1 kB
  • After minification 58.2 kB
  • After compression 10.1 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. Kinaz.com.tw needs all CSS files to be minified and compressed as it can save up to 55.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (43%)

Requests Now

75

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.kinaz.com.tw

www.kinaz.com.tw

1302 ms

public.js

public.js

1395 ms

JsLoader.js

JsLoader.js

532 ms

xajax.js

xajax.js

1174 ms

xajax_extend.js

xajax_extend.js

745 ms

style.css

style.css

968 ms

style.css

style.css

667 ms

jquery.min.js

jquery.min.js

2140 ms

jquery.browser.js

jquery.browser.js

1119 ms

pirobox.min.js

pirobox.min.js

1176 ms

jquery.tools.min.js

jquery.tools.min.js

1662 ms

jquery.blockUI.js

jquery.blockUI.js

1816 ms

jquery.menu.js

jquery.menu.js

1857 ms

normal.js

normal.js

1862 ms

conversion.js

conversion.js

29 ms

ytc.js

ytc.js

39 ms

fbds.js

fbds.js

145 ms

bat.js

bat.js

154 ms

logo.jpg

logo.jpg

506 ms

icon_phone.jpg

icon_phone.jpg

281 ms

icon_mail.jpg

icon_mail.jpg

284 ms

icon_fb2.jpg

icon_fb2.jpg

281 ms

bt_lang.jpg

bt_lang.jpg

287 ms

icon_buy.gif

icon_buy.gif

290 ms

bt_search.jpg

bt_search.jpg

533 ms

B4010676467S.jpg

B4010676467S.jpg

2328 ms

B1986168470S.jpg

B1986168470S.jpg

2280 ms

B6436340401S.jpg

B6436340401S.jpg

2229 ms

B4667593947S.jpg

B4667593947S.jpg

2689 ms

B3868606008S.jpg

B3868606008S.jpg

2630 ms

mv_prve.png

mv_prve.png

786 ms

mv_next.png

mv_next.png

1041 ms

B9339721212S.jpg

B9339721212S.jpg

2769 ms

B0387959553S.jpg

B0387959553S.jpg

2643 ms

B6035121700S.jpg

B6035121700S.jpg

2703 ms

B7144921608S.jpg

B7144921608S.jpg

2748 ms

B3745721444S.jpg

B3745721444S.jpg

3898 ms

B4184421558S.jpg

B4184421558S.jpg

3062 ms

B6969134396S.jpg

B6969134396S.jpg

3113 ms

B8972244121S.jpg

B8972244121S.jpg

3127 ms

B1569622235S.jpg

B1569622235S.jpg

3171 ms

B3376022107S.jpg

B3376022107S.jpg

3181 ms

B7456222003S.jpg

B7456222003S.jpg

3486 ms

B6902044214S.jpg

B6902044214S.jpg

3539 ms

B0938591665S.jpg

B0938591665S.jpg

3574 ms

B1125354635S.jpg

B1125354635S.jpg

3586 ms

B7598549152S.jpg

B7598549152S.jpg

3594 ms

B1974454586S.jpg

B1974454586S.jpg

3906 ms

B9882521302S.jpg

B9882521302S.jpg

4184 ms

B7423822293S.jpg

B7423822293S.jpg

3998 ms

B3444661892S.jpg

B3444661892S.jpg

5260 ms

B9040868384S.jpg

B9040868384S.jpg

4021 ms

to_top.jpg

to_top.jpg

4110 ms

qrcode.jpg

qrcode.jpg

4321 ms

61 ms

ga.js

ga.js

19 ms

53 ms

blade_track_gl.js

blade_track_gl.js

35 ms

__utm.gif

__utm.gif

15 ms

34 ms

47 ms

108 ms

globaltrust_75_seal.gif

globaltrust_75_seal.gif

4576 ms

counter.php

counter.php

3967 ms

icon_fbfan.gif

icon_fbfan.gif

4041 ms

close_btn.png

close_btn.png

4131 ms

t_l.png

t_l.png

4180 ms

t_c.png

t_c.png

4048 ms

t_r.png

t_r.png

4018 ms

c_l.png

c_l.png

3857 ms

c_r.png

c_r.png

3633 ms

b_l.png

b_l.png

2530 ms

b_c.png

b_c.png

2482 ms

b_r.png

b_r.png

2529 ms

play.png

play.png

2250 ms

pgto_prev.png

pgto_prev.png

2531 ms

pgto_next.png

pgto_next.png

2906 ms

24 ms

SEO Factors

kinaz.com.tw SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

kinaz.com.tw

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