Tools & Wizards About Us
fengyuan.com.tw screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    62% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    34% of websites

  • 99

    SEO

    Google-friendlier than
    95% of websites

fengyuan.com.tw

VTEM Emake - 右豐實業股份有限公司

Page Load Speed

6.6 sec in total

First Response

597 ms

Resources Loaded

5.7 sec

Page Rendered

252 ms

fengyuan.com.tw screenshot

About Website

Welcome to fengyuan.com.tw homepage info - get ready to check Fengyuan best content right away, or after learning these important things about fengyuan.com.tw

右豐實業股份有限公司, 碾米機, 精米機, 選石機, 咖啡脫殼機, 風鼓機, 脫汁機, 礱穀脫殼機, 礱穀精米聯合機, 青梅脫仔粉碎機, 穀物乾燥機, 枝葉粉碎機.

Visit fengyuan.com.tw

Key Findings

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

fengyuan.com.tw performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.085

93/100

15%

TTI (Time to Interactive)

Value10.1 s

26/100

10%

Network Requests Diagram

597 ms

k2.css

206 ms

style.css

410 ms

style.css

406 ms

lytebox.css

412 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 96% of them (71 requests) were addressed to the original Fengyuan.com.tw, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Fengyuan.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 678.5 kB (60%)

Content Size

1.1 MB

After Optimization

452.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 29.6 kB

  • Original 36.0 kB
  • After minification 32.8 kB
  • After compression 6.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. 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.6 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 21.2 kB

  • Original 268.9 kB
  • After minification 247.7 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. Fengyuan images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 430.6 kB

  • Original 591.7 kB
  • After minification 553.4 kB
  • After compression 161.1 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 430.6 kB or 73% of the original size.

CSS Optimization

-84%

Potential reduce by 197.1 kB

  • Original 234.3 kB
  • After minification 187.9 kB
  • After compression 37.2 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. Fengyuan.com.tw needs all CSS files to be minified and compressed as it can save up to 197.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (51%)

Requests Now

71

After Optimization

35

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

597 ms

k2.css

k2.css

206 ms

style.css

style.css

410 ms

style.css

style.css

406 ms

lytebox.css

lytebox.css

412 ms

template.css

template.css

403 ms

modal.css

modal.css

408 ms

camera.css

camera.css

411 ms

css

css

47 ms

mootools-core.js

mootools-core.js

806 ms

core.js

core.js

609 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

830 ms

k2.js

k2.js

613 ms

caption.js

caption.js

625 ms

mootools-more.js

mootools-more.js

1017 ms

vtem_menu.js

vtem_menu.js

845 ms

fg.menu.js

fg.menu.js

845 ms

jquery.min.js

jquery.min.js

156 ms

lytebox.js

lytebox.js

846 ms

behaviour.js

behaviour.js

1005 ms

behaviour.js

behaviour.js

1014 ms

modal.js

modal.js

1012 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1066 ms

camera.min.js

camera.min.js

1068 ms

system.css

system.css

1206 ms

general.css

general.css

1219 ms

template.css

template.css

1217 ms

style2.css

style2.css

1219 ms

responsive.css

responsive.css

1221 ms

menu.js

menu.js

1241 ms

vt_logo_style2.png

vt_logo_style2.png

321 ms

tw.gif

tw.gif

332 ms

en.gif

en.gif

330 ms

phone.png

phone.png

330 ms

system.css

system.css

223 ms

components.css

components.css

230 ms

modules.css

modules.css

396 ms

layouts.css

layouts.css

407 ms

navigation.css

navigation.css

407 ms

forms.css

forms.css

410 ms

typo.css

typo.css

416 ms

error.css

error.css

434 ms

3rd_party.css

3rd_party.css

599 ms

chart

chart

174 ms

vt_body.png

vt_body.png

208 ms

vt_bgwapfooter_style2.png

vt_bgwapfooter_style2.png

209 ms

vt_bgwaphead_style2.png

vt_bgwaphead_style2.png

212 ms

vt_coner_top.png

vt_coner_top.png

213 ms

nav_mobi.png

nav_mobi.png

209 ms

loader.gif

loader.gif

205 ms

JF-15.png

JF-15.png

1006 ms

transparent.gif

transparent.gif

416 ms

jwsigpro_cache_d025285ff5_jf-15.jpg

jwsigpro_cache_d025285ff5_jf-15.jpg

419 ms

jwsigpro_cache_d025285ff5_jf-18.jpg

jwsigpro_cache_d025285ff5_jf-18.jpg

423 ms

jwsigpro_cache_d025285ff5_jf-25.jpg

jwsigpro_cache_d025285ff5_jf-25.jpg

422 ms

jwsigpro_cache_d025285ff5_jf-35.jpg

jwsigpro_cache_d025285ff5_jf-35.jpg

419 ms

jwsigpro_cache_d025285ff5_jf-52.jpg

jwsigpro_cache_d025285ff5_jf-52.jpg

622 ms

jwsigpro_cache_d025285ff5_jf-63.jpg

jwsigpro_cache_d025285ff5_jf-63.jpg

624 ms

jwsigpro_cache_d025285ff5_jf-65.jpg

jwsigpro_cache_d025285ff5_jf-65.jpg

622 ms

jwsigpro_cache_d025285ff5_jf-73.jpg

jwsigpro_cache_d025285ff5_jf-73.jpg

627 ms

jwsigpro_cache_d025285ff5_jf-88.jpg

jwsigpro_cache_d025285ff5_jf-88.jpg

624 ms

jwsigpro_cache_d025285ff5_yf-04.jpg

jwsigpro_cache_d025285ff5_yf-04.jpg

840 ms

jwsigpro_cache_d025285ff5_yf-05.jpg

jwsigpro_cache_d025285ff5_yf-05.jpg

838 ms

jwsigpro_cache_d025285ff5_yf-06.jpg

jwsigpro_cache_d025285ff5_yf-06.jpg

842 ms

vt_title.jpg

vt_title.jpg

840 ms

loading2.gif

loading2.gif

812 ms

title_content.png

title_content.png

1008 ms

menu4.gif

menu4.gif

1013 ms

vt_coner_bottom.png

vt_coner_bottom.png

1014 ms

back_to_top.png

back_to_top.png

1026 ms

camera-loader.gif

camera-loader.gif

978 ms

001.jpg

001.jpg

1144 ms

002.jpg

002.jpg

610 ms

print.css

print.css

205 ms

Accessibility Review

fengyuan.com.tw accessibility score

96

Accessibility Issues

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

Links do not have a discernible name

Best Practices

fengyuan.com.tw best practices score

67

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

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

fengyuan.com.tw SEO score

99

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fengyuan.com.tw 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 Fengyuan.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

fengyuan.com.tw

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