Tools & Wizards About Us
gfcl.com.tw screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

gfcl.com.tw

禾康肥料

Page Load Speed

4.1 sec in total

First Response

631 ms

Resources Loaded

3.1 sec

Page Rendered

410 ms

gfcl.com.tw screenshot

About Website

Click here to check amazing Gfcl content for Taiwan. Otherwise, check out these important facts you probably never knew about gfcl.com.tw

國產推薦肥料,有機審字號肥料,微生物肥料,好康633,好康522,好康果樹肥155,台肥活力磷寶,台肥活力鉀寶,禾康即溶肥,有機肥,化學肥,台灣熊蜂,禾康肥料,以色列滴灌設備,台肥即溶肥,台肥金旺43號,種子 ,日本種子,歐洲種子,肥料行,肥料那裡買,田寶11號,大壯牌,禾康即溶肥,鈣勇硝酸鈣,

Visit gfcl.com.tw

Key Findings

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

Performance Metrics

gfcl.com.tw performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value4.9 s

65/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

gfcl.com.tw

631 ms

stylesheet.css

197 ms

slideshow.css

150 ms

news.css

148 ms

carousel.css

149 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 80% of them (67 requests) were addressed to the original Gfcl.com.tw, 12% (10 requests) were made to Static.xx.fbcdn.net and 7% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (978 ms) belongs to the original domain Gfcl.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 459.8 kB (38%)

Content Size

1.2 MB

After Optimization

760.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gfcl.com.tw main page is 1.2 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. 45% of websites need less resources to load. Images take 744.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 33.5 kB

  • Original 40.1 kB
  • After minification 30.3 kB
  • After compression 6.5 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 9.8 kB, which is 24% 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 33.5 kB or 84% of the original size.

Image Optimization

-13%

Potential reduce by 98.2 kB

  • Original 744.5 kB
  • After minification 646.2 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, Gfcl needs image optimization as it can save up to 98.2 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

-72%

Potential reduce by 244.8 kB

  • Original 340.2 kB
  • After minification 332.7 kB
  • After compression 95.4 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 244.8 kB or 72% of the original size.

CSS Optimization

-87%

Potential reduce by 83.2 kB

  • Original 95.9 kB
  • After minification 70.4 kB
  • After compression 12.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. Gfcl.com.tw needs all CSS files to be minified and compressed as it can save up to 83.2 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (20%)

Requests Now

83

After Optimization

66

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gfcl.com.tw

gfcl.com.tw

631 ms

stylesheet.css

stylesheet.css

197 ms

slideshow.css

slideshow.css

150 ms

news.css

news.css

148 ms

carousel.css

carousel.css

149 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

339 ms

jquery-ui-1.8.16.custom.min.js

jquery-ui-1.8.16.custom.min.js

509 ms

jquery-ui-1.8.16.custom.css

jquery-ui-1.8.16.custom.css

278 ms

common.js

common.js

222 ms

jquery.cycle.js

jquery.cycle.js

223 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

260 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

409 ms

iconcart.gif

iconcart.gif

892 ms

logo-1.png

logo-1.png

568 ms

Product.png

Product.png

333 ms

edm.png

edm.png

379 ms

News.png

News.png

423 ms

Story.png

Story.png

424 ms

Message.png

Message.png

457 ms

Downloads.png

Downloads.png

485 ms

ContactUs.png

ContactUs.png

500 ms

Ceremony.png

Ceremony.png

500 ms

gfclgif-201x700.gif

gfclgif-201x700.gif

978 ms

Creditcard-icon-201x120.png

Creditcard-icon-201x120.png

699 ms

taita-785x319.jpg

taita-785x319.jpg

653 ms

16-785x319.jpg

16-785x319.jpg

650 ms

banner-785x319-785x319.jpg

banner-785x319-785x319.jpg

647 ms

lipro50-785x319.jpg

lipro50-785x319.jpg

648 ms

999-160x160.jpg

999-160x160.jpg

648 ms

2-09-160x160.jpg

2-09-160x160.jpg

650 ms

potassium-160x160.jpg

potassium-160x160.jpg

670 ms

lipro50-160x160.jpg

lipro50-160x160.jpg

669 ms

rosa-160x160.jpg

rosa-160x160.jpg

662 ms

GREENEEM-160x160.jpg

GREENEEM-160x160.jpg

718 ms

ez2013917112879457-160x160.jpg

ez2013917112879457-160x160.jpg

711 ms

0030-160x160.jpg

0030-160x160.jpg

739 ms

ez2013322144175043-160x160.jpg

ez2013322144175043-160x160.jpg

741 ms

ez2013622133813320-160x160.jpg

ez2013622133813320-160x160.jpg

739 ms

ez20139314830060-160x160.jpg

ez20139314830060-160x160.jpg

697 ms

logo1-160x160.png

logo1-160x160.png

705 ms

9-160x160.jpg

9-160x160.jpg

727 ms

IMG_7857-160x160.jpg

IMG_7857-160x160.jpg

678 ms

alga280-160x160.jpg

alga280-160x160.jpg

653 ms

banner_01-107x55.png

banner_01-107x55.png

691 ms

shengmay-107x55.png

shengmay-107x55.png

681 ms

banner_02-107x55.png

banner_02-107x55.png

664 ms

banner_03-107x55.png

banner_03-107x55.png

611 ms

banner_04-107x55.png

banner_04-107x55.png

594 ms

topbg.jpg

topbg.jpg

615 ms

top-bg.jpg

top-bg.jpg

702 ms

arrow-down.png

arrow-down.png

457 ms

button-search.png

button-search.png

460 ms

login01.png

login01.png

461 ms

list.png

list.png

489 ms

listok.jpg

listok.jpg

515 ms

FBlogin.png

FBlogin.png

535 ms

loading.gif

loading.gif

538 ms

new.png

new.png

514 ms

likebox.php

likebox.php

114 ms

Push.png

Push.png

445 ms

button.png

button.png

464 ms

Sell.png

Sell.png

475 ms

Latest.png

Latest.png

624 ms

button-previous.png

button-previous.png

625 ms

button-next.png

button-next.png

623 ms

footbg.jpg

footbg.jpg

619 ms

arrows.png

arrows.png

608 ms

bullets.png

bullets.png

614 ms

C-D3sjGKj3j.css

C-D3sjGKj3j.css

289 ms

zEMlMNmIXUJ.css

zEMlMNmIXUJ.css

358 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

495 ms

b94UUzHjapV.js

b94UUzHjapV.js

625 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

491 ms

TTCre3391I0.js

TTCre3391I0.js

516 ms

1526502_643547002375410_1082425298_n.jpg

1526502_643547002375410_1082425298_n.jpg

368 ms

382278_486402234756555_397734122_n.jpg

382278_486402234756555_397734122_n.jpg

508 ms

1911991_727592860594986_7265599066266325554_n.jpg

1911991_727592860594986_7265599066266325554_n.jpg

656 ms

12243100_760193190781062_604210471742685613_n.jpg

12243100_760193190781062_604210471742685613_n.jpg

877 ms

12112471_1497514043882761_8172856089407521092_n.jpg

12112471_1497514043882761_8172856089407521092_n.jpg

610 ms

10274341_536709159771032_4253041941311817324_n.jpg

10274341_536709159771032_4253041941311817324_n.jpg

628 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

72 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

72 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

72 ms

f6T91Deal_q.js

f6T91Deal_q.js

136 ms

Accessibility Review

gfcl.com.tw accessibility score

73

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

SEO Factors

gfcl.com.tw SEO score

50

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

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

gfcl.com.tw

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