16.3 sec in total
6.7 sec
9.1 sec
427 ms
Welcome to i-house.web66.com.tw homepage info - get ready to check I House Web 66 best content for Taiwan right away, or after learning these important things about i-house.web66.com.tw
特力屋股份有限公司
Visit i-house.web66.com.twWe analyzed I-house.web66.com.tw page load time and found that the first response time was 6.7 sec and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
i-house.web66.com.tw performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value3.6 s
61/100
25%
Value7.5 s
26/100
10%
Value780 ms
37/100
30%
Value0.165
71/100
15%
Value8.5 s
38/100
10%
6696 ms
29 ms
263 ms
480 ms
723 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 10% of them (11 requests) were addressed to the original I-house.web66.com.tw, 46% (48 requests) were made to S.web66.com.tw and 6% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (6.7 sec) belongs to the original domain I-house.web66.com.tw.
Page size can be reduced by 607.7 kB (53%)
1.2 MB
542.3 kB
In fact, the total size of I-house.web66.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. 55% of websites need less resources to load. Javascripts take 703.8 kB which makes up the majority of the site volume.
Potential reduce by 109.9 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 109.9 kB or 79% of the original size.
Potential reduce by 11.9 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. I House Web 66 images are well optimized though.
Potential reduce by 457.5 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 457.5 kB or 65% of the original size.
Potential reduce by 28.3 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. I-house.web66.com.tw needs all CSS files to be minified and compressed as it can save up to 28.3 kB or 88% of the original size.
Number of requests can be reduced by 60 (62%)
97
37
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I House Web 66. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
i-house.web66.com.tw
6696 ms
js
29 ms
jquery-1.11.1.min.js
263 ms
css22_zh_TW.css
480 ms
colorShare_zh_TW.css
723 ms
lib.js
935 ms
theme.js
770 ms
fix_ieflash.js
758 ms
resizeImgs.js
528 ms
head.css
623 ms
blogTbar.js
606 ms
show_ads.js
23 ms
all.js
45 ms
responseHTML.js
144 ms
a
41 ms
p8banner.js
210 ms
MM_lib.js
251 ms
JB_ObjLib.js
257 ms
head.jpg
634 ms
710x90px-banner.jpg
1107 ms
yellowPages-logo.gif
285 ms
logo-text-home.gif
284 ms
Yellowpage_top_L.gif
45 ms
Yellowpage_top_icon.gif
43 ms
Yellowpage_top_R.gif
45 ms
Yellowpage_bot_L.gif
55 ms
Yellowpage_bot_R.gif
56 ms
blog-side_mail-icon.gif
373 ms
blodside02_icon.gif
373 ms
blodside02_bot.gif
373 ms
contactUs_btn.gif
96 ms
pic1_240.jpg
372 ms
detail-proposal-title.gif
475 ms
sendOrg_title.jpg
711 ms
sendOrg_icon.jpg
624 ms
Ask_login_icon.gif
627 ms
add_btn.gif
635 ms
V.jpg
665 ms
D.jpg
772 ms
upt_submit.jpg
872 ms
upt_reset.jpg
891 ms
recommend_titleBg-L.gif
892 ms
recommend_icon02.gif
927 ms
recommend_titleBg-R.gif
937 ms
recommend_icon.gif
996 ms
headbar_bg.jpg
1248 ms
headbartbtn.gif
1183 ms
side_bg01.gif
1182 ms
side_top01.gif
1250 ms
Hitcount.jsp
836 ms
blog-side_hr-X.gif
1212 ms
side_dot01.gif
1320 ms
ca-pub-4944879299702095.js
203 ms
zrt_lookup.html
194 ms
show_ads_impl.js
142 ms
title_L01.gif
1440 ms
title_bg01.gif
1439 ms
title_R01.gif
1490 ms
Ask_login_add-bg.gif
1478 ms
recommend_titleBg-C.gif
1377 ms
gpt.js
56 ms
ads
396 ms
osd.js
94 ms
pubads_impl_83.js
104 ms
foot_top.gif
1446 ms
s.gif
79 ms
atrk.js
170 ms
Ajax
431 ms
Ajax
431 ms
250x160banner14.jpg
1468 ms
Ajax
430 ms
ads
154 ms
container.html
31 ms
atrk.gif
33 ms
test.png
327 ms
ads
315 ms
8789454182212098732
69 ms
abg.js
81 ms
m_js_controller.js
97 ms
googlelogo_color_112x36dp.png
37 ms
s
46 ms
x_button_blue2.svg
47 ms
Home
570 ms
Home
940 ms
Home
926 ms
Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js
33 ms
adj
170 ms
beacon
122 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
50 ms
lidar.js
16 ms
dvtp_src.js
151 ms
antenna2.js
48 ms
index.html
26 ms
css
88 ms
CSSPlugin.min.js
176 ms
EasePack.min.js
181 ms
TweenLite.min.js
206 ms
dvtp_src_internal28.js
27 ms
pixel
90 ms
t2tv7.html
248 ms
pixel
148 ms
pixel
152 ms
BVtM30trf7q_jfqYeHfjtA.woff
42 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
52 ms
124 ms
i-house.web66.com.tw accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
i-house.web66.com.tw best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
i-house.web66.com.tw SEO score
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
Document uses legible font sizes
JA
N/A
BIG5
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I-house.web66.com.tw can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that I-house.web66.com.tw main page’s claimed encoding is big5. 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.
i-house.web66.com.tw
Open Graph description is not detected on the main page of I House Web 66. 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: