6.7 sec in total
1.2 sec
5.3 sec
258 ms
Visit 30g.tw now to see the best up-to-date 30 G content for Taiwan and also check out these interesting facts you probably never knew about 30g.tw
來自東台灣,集結了陽光、風雨、豐腴土壤的好味道。
Visit 30g.twWe analyzed 30g.tw page load time and found that the first response time was 1.2 sec and then it took 5.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.
30g.tw performance score
1186 ms
407 ms
409 ms
1049 ms
424 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 56% of them (50 requests) were addressed to the original 30g.tw, 22% (20 requests) were made to Static.xx.fbcdn.net and 17% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain 30g.tw.
Page size can be reduced by 1.5 MB (92%)
1.7 MB
140.6 kB
In fact, the total size of 30g.tw main page is 1.7 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. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 39.2 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 8.5 kB, which is 18% 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 39.2 kB or 83% of the original size.
Potential reduce by 1.3 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. Obviously, 30 G needs image optimization as it can save up to 1.3 MB or 95% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 94.3 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 94.3 kB or 63% of the original size.
Potential reduce by 51.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. 30g.tw needs all CSS files to be minified and compressed as it can save up to 51.3 kB or 87% of the original size.
Number of requests can be reduced by 36 (41%)
88
52
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 30 G. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
30g.tw
1186 ms
vegetable.css
407 ms
style.css
409 ms
jquery-1.9.1.min.js
1049 ms
gallery.js
424 ms
menu.js
426 ms
layout.css
811 ms
analytics.js
49 ms
bg.jpg
1281 ms
bg_line.png
205 ms
logo.png
429 ms
icon.png
215 ms
top_line.gif
205 ms
menu_icon.png
211 ms
shopcar.png
411 ms
title01.png
410 ms
title02.png
430 ms
menu01412582522.jpg
1513 ms
btn_bg.png
629 ms
menu01457591945.jpg
1642 ms
menu01415175133.jpg
1961 ms
menu01433907061.jpg
1518 ms
menu01423452816.jpg
1830 ms
menu01435716829.jpg
1727 ms
menu01405578479.jpg
2155 ms
menu01428400216.jpg
2418 ms
menu01427879748.jpg
2254 ms
menu01403070353.jpg
1974 ms
a.png
2032 ms
bottom.png
3248 ms
stw_product_caty01457591169.jpg
2192 ms
stw_product_caty01430200302.jpg
2240 ms
stw_product_caty01412308436.jpg
2369 ms
stw_product_caty01430362607.jpg
2413 ms
footer_bg.jpg
2443 ms
footer_bg02.jpg
2457 ms
line.gif
2581 ms
stw_famer_caty01408413089.jpg
2629 ms
pic.png
2626 ms
farmer.png
2645 ms
spic.png
2659 ms
stw_famer_caty01384158267.jpg
2793 ms
stw_famer_caty01385017598.jpg
2838 ms
stw_famer_caty01415179209.jpg
2842 ms
likebox.php
221 ms
collect
22 ms
collect
16 ms
tw_blog_caty11445322720.jpg
2649 ms
newsline.png
2663 ms
footer_line.png
2799 ms
fb.gif
2841 ms
410ucuAGgaJ.css
179 ms
tSbl8xBI27R.css
222 ms
VyhHmC9SnBT.css
262 ms
q68gy-v_YMF.js
374 ms
FJmpeSpHpjS.js
400 ms
0wM5s1Khldu.js
301 ms
1bNoFZUdlYZ.js
299 ms
OloiM1PZafe.js
301 ms
LTv6ZK-5zxz.js
422 ms
1FCa-btixu2.js
407 ms
Oagsvfb4VWi.js
407 ms
pObvZSrFc_4.js
406 ms
Kt4tkgSRvHH.js
412 ms
H3EKDTObx05.js
412 ms
eR-qA8bp1RM.js
455 ms
google.gif
2660 ms
footer_logo.png
2653 ms
hover.png
2650 ms
12573940_1220248178004503_6438122813831032986_n.jpg
310 ms
10362383_1137563169606338_4618457187294237533_n.jpg
349 ms
12472249_10153807119309598_4962230003870197375_n.jpg
392 ms
1660573_691635240940144_633224943170398787_n.jpg
461 ms
1978659_3961319687805_1054489508_n.jpg
430 ms
1939790_1278582772156006_8892221678179816879_n.jpg
433 ms
600731_1717540088493949_4360672752419825886_n.jpg
507 ms
12800259_10206967503160656_7193365251349694019_n.jpg
494 ms
946797_800084553434165_7418137019916871037_n.jpg
463 ms
10354686_10150004552801856_220367501106153455_n.jpg
469 ms
12806006_181836285527027_3828862405493442998_n.jpg
650 ms
12072609_159077794436442_1619971877630283046_n.jpg
500 ms
11013369_10154493923277837_5720504821497704735_n.jpg
537 ms
11205112_1645694988977365_5400827751934133348_n.jpg
566 ms
10710979_1566868853542884_6199760295810934755_n.jpg
534 ms
wL6VQj7Ab77.png
62 ms
s7jcwEQH7Sx.png
62 ms
gxbPuQdXIZP.png
47 ms
I6-MnjEovm5.js
41 ms
pQrUxxo5oQp.js
80 ms
30g.tw SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 30g.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 30g.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.
30g.tw
Open Graph description is not detected on the main page of 30 G. 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: