50.1 sec in total
1.8 sec
47.9 sec
393 ms
Welcome to grimmpress.com.tw homepage info - get ready to check Grimmpress best content for Taiwan right away, or after learning these important things about grimmpress.com.tw
格林繪本網
Visit grimmpress.com.twWe analyzed Grimmpress.com.tw page load time and found that the first response time was 1.8 sec and then it took 48.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 23 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
grimmpress.com.tw performance score
1830 ms
2578 ms
8071 ms
2203 ms
2070 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 54% of them (69 requests) were addressed to the original Grimmpress.com.tw, 19% (24 requests) were made to Static.xx.fbcdn.net and 8% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Grimmpress.com.tw.
Page size can be reduced by 662.0 kB (49%)
1.3 MB
678.3 kB
In fact, the total size of Grimmpress.com.tw main page is 1.3 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. 65% of websites need less resources to load. Images take 509.9 kB which makes up the majority of the site volume.
Potential reduce by 82.8 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 82.8 kB or 85% of the original size.
Potential reduce by 54.6 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, Grimmpress needs image optimization as it can save up to 54.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 266.9 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 266.9 kB or 63% of the original size.
Potential reduce by 257.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. Grimmpress.com.tw needs all CSS files to be minified and compressed as it can save up to 257.6 kB or 83% of the original size.
Number of requests can be reduced by 44 (44%)
100
56
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grimmpress. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
grimmpress.com.tw
1830 ms
017all.css
2578 ms
jquery-1.4.3.min.js
8071 ms
jquery.fancybox-1.3.4.js
2203 ms
jquery.fancybox-1.3.4.css
2070 ms
google.js
592 ms
jcarousellite_1.0.1.min.js
792 ms
hoverIntent.js
1231 ms
superfish.js
1091 ms
swfobject_modified.js
3788 ms
jquery.ad-gallery.css
1835 ms
jquery.ad-gallery.js
3234 ms
all4.css
2434 ms
JS_maintain.js
2260 ms
ga.js
74 ms
get_flash_player.gif
67 ms
ic4.jpg
851 ms
ic5.jpg
853 ms
ic1.png
1304 ms
2016012517091852.gif
5314 ms
2016012817433957.jpg
9990 ms
2016010410002138.jpg
17127 ms
ic2.png
1396 ms
2013062016295951.jpg
3064 ms
2015010506403130.jpg
7843 ms
2014100810504785.jpg
6131 ms
2015120116371750.jpg
10091 ms
2015120116301167.jpg
11799 ms
2015120116325226.jpg
16537 ms
2012022410593446.png
8051 ms
2011112515432595.png
8306 ms
2014090406502172.png
8557 ms
2014100910043790.jpg
9378 ms
2014100910072283.png
9667 ms
2016031810405527.jpg
19775 ms
040.jpg
11145 ms
2016032210574719.png
19775 ms
2016032211051132.jpg
19774 ms
2016040113422320.jpg
19775 ms
2016032211184548.jpg
19775 ms
201602241402581.jpg
19775 ms
ic20.png
19775 ms
2016022414221121.jpg
19775 ms
2016022414450237.jpg
19775 ms
2016022415074653.jpg
19775 ms
2016022415262394.jpg
19775 ms
2016012909462194.jpg
19775 ms
2016012910084970.jpg
19775 ms
2016012910385556.jpg
19775 ms
2016012817110211.jpg
19775 ms
2016010514201396.jpg
19775 ms
analytics.js
54 ms
20160113130458100.jpg
19771 ms
all.js
129 ms
boxcJZVmz7I
246 ms
bmeI25Dck6w
318 ms
__utm.gif
67 ms
collect
49 ms
210 ms
xd_arbiter.php
183 ms
xd_arbiter.php
248 ms
collect
190 ms
www-embed-player-vfl5foy2V.css
58 ms
www-embed-player.js
84 ms
base.js
126 ms
F5EcQNuXvzCwnROrenDy46C3KsouVqfn29hTt0MreZk.js
35 ms
ad_status.js
66 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
72 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
76 ms
201601131310436.jpg
19929 ms
2015122916142247.jpg
19926 ms
2015122916320424.jpg
20475 ms
2015122916435058.jpg
20382 ms
028_01.jpg
19712 ms
028_03.jpg
16308 ms
029.jpg
15168 ms
032_2012_3.jpg
15441 ms
popup.png
14054 ms
049.jpg
18072 ms
logo11.jpg
18584 ms
logo12.jpg
14688 ms
bg5.jpg
19263 ms
tableftB.gif
13563 ms
tabrightB.gif
13693 ms
adtop.png
15380 ms
033_01.gif
13052 ms
033_03.jpg
10088 ms
028_04.jpg
19651 ms
ping
127 ms
like_box.php
388 ms
zhxgx__rVIm.css
204 ms
EWO3D1XXkFA.css
228 ms
R1VRobHkino.css
248 ms
h6YhJ1Ax_V1.css
299 ms
2IHg3lLstcq.css
316 ms
SRSW8M763HA.js
342 ms
ldIMPsSoKmy.js
339 ms
y97Ig99UVTs.js
271 ms
KHAtULXOQuz.js
293 ms
W4NL_XloU4d.js
332 ms
eACiSk3I2K6.js
333 ms
FOagnU9QnXq.js
395 ms
rR4Qw0p7TFQ.js
403 ms
ULtnh-HfQSw.js
339 ms
6IFzBT9uHU-.js
401 ms
10403298_10153066743863453_6779901396594037664_n.jpg
346 ms
safe_image.php
368 ms
safe_image.php
553 ms
safe_image.php
570 ms
1508086_10153066739178453_6762008695296608028_n.jpg
322 ms
12718198_10154135601098453_8193361983647474593_n.jpg
543 ms
12928378_10154135610493453_6282844507959398895_n.jpg
542 ms
12919780_10154135610498453_5053131912295560757_n.jpg
533 ms
12963562_10154135610483453_2719373179853260312_n.jpg
534 ms
12961716_10154133597943453_367031436346199262_n.jpg
554 ms
12805856_10154133607318453_3483894123814468421_n.jpg
535 ms
12963582_10154133607308453_1876478107125838410_n.jpg
555 ms
12985511_10154133607303453_8807859864954271753_n.jpg
563 ms
wL6VQj7Ab77.png
149 ms
1JLnMyDN79z.png
152 ms
ex8r-_gkt_Y.png
305 ms
bNvHN6v1NeH.png
142 ms
t-wz8gw1xG1.png
144 ms
gm-8CYVMZ_l.png
144 ms
ye4Amg-qrtc.js
143 ms
VXcANLwwL5J.js
63 ms
i8XO-4kv8i7.js
64 ms
grimmpress.com.tw SEO score
![]()
ZH
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grimmpress.com.tw can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Grimmpress.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.
grimmpress.com.tw
Open Graph description is not detected on the main page of Grimmpress. 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: