Tools & Wizards About Us
feph.com.tw screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

feph.com.tw

圓滾滾玫瑰

Page Load Speed

3.5 sec in total

First Response

626 ms

Resources Loaded

2.6 sec

Page Rendered

363 ms

feph.com.tw screenshot

About Website

Click here to check amazing Feph content. Otherwise, check out these important facts you probably never knew about feph.com.tw

Visit feph.com.tw

Key Findings

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

Performance Metrics

feph.com.tw performance score

0

Network Requests Diagram

feph.com.tw

626 ms

jquery.min.js

75 ms

config.js

193 ms

styles.css

900 ms

textstyles.css

360 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 96% of them (25 requests) were addressed to the original Feph.com.tw, 4% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (900 ms) belongs to the original domain Feph.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 111.6 kB (32%)

Content Size

344.3 kB

After Optimization

232.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-63%

Potential reduce by 4.6 kB

  • Original 7.3 kB
  • After minification 7.2 kB
  • After compression 2.7 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 4.6 kB or 63% of the original size.

Image Optimization

-1%

Potential reduce by 1.2 kB

  • Original 214.7 kB
  • After minification 213.5 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. Feph images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 972 B

  • Original 1.3 kB
  • After minification 728 B
  • After compression 338 B

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 972 B or 74% of the original size.

CSS Optimization

-87%

Potential reduce by 104.8 kB

  • Original 121.0 kB
  • After minification 99.7 kB
  • After compression 16.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. Feph.com.tw needs all CSS files to be minified and compressed as it can save up to 104.8 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

25

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

feph.com.tw

feph.com.tw

626 ms

jquery.min.js

jquery.min.js

75 ms

config.js

config.js

193 ms

styles.css

styles.css

900 ms

textstyles.css

textstyles.css

360 ms

header.jpg

header.jpg

872 ms

tables.css

tables.css

246 ms

commonstyles.css

commonstyles.css

181 ms

wrapper_inner_bg.png

wrapper_inner_bg.png

674 ms

top_inner_bg.gif

top_inner_bg.gif

170 ms

body_bg.gif

body_bg.gif

185 ms

main_bg_t.png

main_bg_t.png

352 ms

main_bg_b.png

main_bg_b.png

341 ms

main_bg.gif

main_bg.gif

357 ms

mainbox_inner_bg.gif

mainbox_inner_bg.gif

366 ms

h3_bg.png

h3_bg.png

393 ms

h3_bg_r.png

h3_bg_r.png

504 ms

h3.png

h3.png

543 ms

menu_title_bg_b.png

menu_title_bg_b.png

544 ms

menu_h4_bg.gif

menu_h4_bg.gif

563 ms

menu_h4.png

menu_h4.png

581 ms

menu_li_bg.gif

menu_li_bg.gif

671 ms

menu_bg.png

menu_bg.png

720 ms

btnbox_bg.png

btnbox_bg.png

732 ms

pagetop_button.png

pagetop_button.png

756 ms

footer_bg.png

footer_bg.png

767 ms

SEO Factors

feph.com.tw SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Feph.com.tw can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Feph.com.tw main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

feph.com.tw

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