Tools & Wizards About Us
forhome.com.tw screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

forhome.com.tw

北歐風｜工業風｜復古設計家具 Forhome | 歡迎光臨

Page Load Speed

5.5 sec in total

First Response

1.3 sec

Resources Loaded

3.4 sec

Page Rendered

741 ms

forhome.com.tw screenshot

About Website

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

Forhome提供最新的設計家具，包含工業風、北歐風的設計家具，無論是要找沙發、桌椅或櫃架，在Forhome可以輕易的尋找到北歐風與工業風的空間佈置靈感，創造獨具風格的生活美學。

Visit forhome.com.tw

Key Findings

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

Performance Metrics

forhome.com.tw performance score

0

Network Requests Diagram

www.forhome.com.tw

1349 ms

newDesign-build1-1447404723056.css

103 ms

page-renderer.min.css

84 ms

newDesign-build2-1447404723056.css

112 ms

newDesign-home.css

108 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Forhome.com.tw, 29% (17 requests) were made to Dl.dropboxusercontent.com and 16% (9 requests) were made to Asset-1442.kxcdn.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Forhome.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 690.2 kB (11%)

Content Size

6.4 MB

After Optimization

5.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 71.5 kB

  • Original 87.7 kB
  • After minification 87.6 kB
  • After compression 16.1 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 71.5 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 267.6 kB

  • Original 5.8 MB
  • After minification 5.5 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. Forhome images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 243.0 kB

  • Original 390.2 kB
  • After minification 388.4 kB
  • After compression 147.2 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 243.0 kB or 62% of the original size.

CSS Optimization

-80%

Potential reduce by 108.1 kB

  • Original 134.3 kB
  • After minification 132.5 kB
  • After compression 26.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. Forhome.com.tw needs all CSS files to be minified and compressed as it can save up to 108.1 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (44%)

Requests Now

52

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.forhome.com.tw

www.forhome.com.tw

1349 ms

newDesign-build1-1447404723056.css

newDesign-build1-1447404723056.css

103 ms

page-renderer.min.css

page-renderer.min.css

84 ms

newDesign-build2-1447404723056.css

newDesign-build2-1447404723056.css

112 ms

newDesign-home.css

newDesign-home.css

108 ms

mytheme_1422280903.css

mytheme_1422280903.css

78 ms

analytics.js

analytics.js

23 ms

lang.png

lang.png

21 ms

1773-%E5%AE%98%E7%B6%B2%E9%A0%81%E9%9D%A215.png

1773-%E5%AE%98%E7%B6%B2%E9%A0%81%E9%9D%A215.png

691 ms

cart.png

cart.png

17 ms

ecommerce.js

ecommerce.js

47 ms

menu.png

menu.png

27 ms

06.png

06.png

732 ms

forhome%20top7.jpg

forhome%20top7.jpg

339 ms

forhome%20top1.jpg

forhome%20top1.jpg

337 ms

collect

collect

18 ms

collect

collect

71 ms

A3.jpg

A3.jpg

73 ms

forhome%20top2.jpg

forhome%20top2.jpg

405 ms

forhome%20top3.jpg

forhome%20top3.jpg

412 ms

forhome%20top4.jpg

forhome%20top4.jpg

409 ms

forhome%201-1.jpg

forhome%201-1.jpg

411 ms

forhome%201-2.jpg

forhome%201-2.jpg

1144 ms

forhome%201-3.jpg

forhome%201-3.jpg

410 ms

forhome%201-4.jpg

forhome%201-4.jpg

1300 ms

forhome%201-5.jpg

forhome%201-5.jpg

581 ms

forhome%201-6.jpg

forhome%201-6.jpg

595 ms

forhome%201-7.jpg

forhome%201-7.jpg

750 ms

forhome%201-8.jpg

forhome%201-8.jpg

605 ms

forhome%201-9.jpg

forhome%201-9.jpg

793 ms

ionicons.ttf

ionicons.ttf

42 ms

D1.jpg

D1.jpg

56 ms

D2.jpg

D2.jpg

56 ms

page-renderer.min.js

page-renderer.min.js

76 ms

D2.jpg

D2.jpg

736 ms

A3.jpg

A3.jpg

933 ms

D1.jpg

D1.jpg

884 ms

FB_FindUsOnFacebook-144.png

FB_FindUsOnFacebook-144.png

167 ms

YouTube-logo-full_color.png

YouTube-logo-full_color.png

215 ms

vimeo_logo_blue.png

vimeo_logo_blue.png

221 ms

video.png

video.png

219 ms

ps.js

ps.js

113 ms

newDesign-build1-1427367838074.js

newDesign-build1-1427367838074.js

142 ms

adapter.js

adapter.js

138 ms

general-18c7ceb0730dc198665d8e0995c2c977.js

general-18c7ceb0730dc198665d8e0995c2c977.js

222 ms

newDesign-build2-1427335228360.js

newDesign-build2-1427335228360.js

186 ms

blade_track_gl.js

blade_track_gl.js

64 ms

tracker.js

tracker.js

62 ms

gtm.js

gtm.js

72 ms

translation.json

translation.json

23 ms

translation.json

translation.json

24 ms

ui.totop.png

ui.totop.png

651 ms

fbevents.js

fbevents.js

87 ms

conversion.js

conversion.js

27 ms

31 ms

29 ms

30 ms

pv

pv

8 ms

SEO Factors

forhome.com.tw SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forhome.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 English language. Our system also found out that Forhome.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

forhome.com.tw

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