8.1 sec in total
796 ms
6 sec
1.3 sec
Click here to check amazing 123 Blog content for Taiwan. Otherwise, check out these important facts you probably never knew about 123blog.tw
123blog
Visit 123blog.twWe analyzed 123blog.tw page load time and found that the first response time was 796 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
123blog.tw performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value9.6 s
0/100
25%
Value12.0 s
4/100
10%
Value5,140 ms
0/100
30%
Value0.06
98/100
15%
Value16.7 s
5/100
10%
796 ms
806 ms
610 ms
387 ms
8 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original 123blog.tw, 19% (24 requests) were made to P.bluezz.tw and 16% (21 requests) were made to Img.bluezz.tw. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source P.bluezz.tw.
Page size can be reduced by 170.2 kB (8%)
2.1 MB
1.9 MB
In fact, the total size of 123blog.tw main page is 2.1 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 1.8 MB which makes up the majority of the site volume.
Potential reduce by 33.5 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 33.5 kB or 78% of the original size.
Potential reduce by 52.1 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. 123 Blog images are well optimized though.
Potential reduce by 76.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 76.5 kB or 41% of the original size.
Potential reduce by 8.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. 123blog.tw needs all CSS files to be minified and compressed as it can save up to 8.2 kB or 81% of the original size.
Number of requests can be reduced by 61 (50%)
123
62
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 123 Blog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
123blog.tw
796 ms
jquery.min.js
806 ms
j.js
610 ms
css.php
387 ms
show_ads.js
8 ms
ad.js
418 ms
qr_img_bluezz.php
720 ms
s_33008_37437.jpg
1143 ms
counter_img.php
1247 ms
b_1000_top.png
406 ms
b_1000_m.png
406 ms
top.jpg
981 ms
bar_05.png
405 ms
android_adver_175.jpg
406 ms
adver_bluezz_menu.jpg
639 ms
ctopL.jpg
886 ms
ctopRM.jpg
863 ms
ctopR.jpg
887 ms
rss.gif
715 ms
tag.gif
715 ms
s_2955_9506.jpg
924 ms
s_32936_35903.jpg
1137 ms
s_32554_30375.jpg
1138 ms
s_33039_38079.jpg
1135 ms
s_32929_38139.jpg
1129 ms
s_32823_33481.jpg
1571 ms
s_32989_37192.jpg
1756 ms
s_32454_28033.jpg
1556 ms
s_32789_33052.jpg
1555 ms
s_20175_20977.jpg
1771 ms
s_32828_33587.jpg
1775 ms
s_31491_27238.jpg
1983 ms
s_33072_38846.jpg
2206 ms
w640_33083_39089.jpg
2859 ms
w640_33073_38888.jpg
2600 ms
w640_33072_38846.jpg
3043 ms
w640_33063_38681.jpg
3066 ms
w640_33059_38605.jpg
3262 ms
w640_33053_38385.jpg
3484 ms
w640_33047_38221.jpg
3854 ms
w640_33039_38079.jpg
4109 ms
w640_33027_37870.jpg
4317 ms
w640_33013_37598.jpg
4342 ms
top_bar.png
879 ms
bar_01.jpg
1040 ms
bar_02.jpg
1229 ms
bar_03.jpg
1230 ms
ca-pub-8868013038106852.js
104 ms
zrt_lookup.html
103 ms
show_ads_impl.js
104 ms
menu_icon_bg.gif
403 ms
hot_pic_bg.jpg
1211 ms
pic_bg.gif
1209 ms
pic_t_bg.gif
1306 ms
plusone.js
235 ms
o.gif
383 ms
subject_icon.gif
406 ms
ctopPL.jpg
1350 ms
ctopM.jpg
1540 ms
ad.html
483 ms
ga.js
54 ms
b_1000_bottom.png
1489 ms
likebox.php
153 ms
ads
474 ms
osd.js
33 ms
p2
32 ms
like.php
137 ms
ads
392 ms
__utm.gif
46 ms
ads
400 ms
ads
380 ms
roNeOY-tz5Y.css
149 ms
UHhaxo8Cs3k.css
182 ms
_rx8naC75Dy.js
201 ms
x5F9OMjKyLw.js
199 ms
ICDbTSzjQEg.js
188 ms
TTCre3391I0.js
179 ms
cb=gapi.loaded_0
26 ms
cb=gapi.loaded_1
58 ms
badge
175 ms
vpc6VNjRPXV.js
273 ms
LVx-xkvaJ0b.png
171 ms
jquery.min.js
80 ms
swfobject.js
105 ms
postmessageRelay
67 ms
RBlogo-sh2.png
439 ms
api.js
40 ms
core:rpc:shindig.random:shindig.sha1.js
197 ms
2536007149-postmessagerelay.js
114 ms
rs=AGLTcCOIysoEmtW85aiKIBLdKHmHc4_EPw
96 ms
rs=AGLTcCOP6COjm_DFOSfBgSnJyl5PUX2hyw
105 ms
rs=AGLTcCPXZ9VE5EZeKKJHrXSN-HhlkqIV9A
166 ms
10393690_740529709337530_2378439585996578052_n.jpg
208 ms
1012015_569089919814844_262912448_n.png
211 ms
12472540_1037996399590913_246473880989065611_n.jpg
265 ms
970389_657726597600706_1079110596_n.jpg
267 ms
32606_157427587754114_128685032_n.jpg
266 ms
wL6VQj7Ab77.png
84 ms
s7jcwEQH7Sx.png
84 ms
adcall.aspx
733 ms
abg.js
197 ms
grlryt2bdKIyfMSOhzd1eA.woff
306 ms
d-QWLnp4didxos_6urzFtg.woff
372 ms
vxNK-E6B13CyehuDCmvQvw.woff
373 ms
m_js_controller.js
194 ms
googlelogo_color_112x36dp.png
288 ms
5620543176598363700
242 ms
rs=AGLTcCPXZ9VE5EZeKKJHrXSN-HhlkqIV9A
40 ms
rs=AGLTcCPXZ9VE5EZeKKJHrXSN-HhlkqIV9A
115 ms
s
119 ms
x_button_blue2.png
106 ms
I6-MnjEovm5.js
100 ms
vlXaquuXMrr.js
104 ms
nessie_icon_tiamat_white.png
39 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
16 ms
2015060509184759-2284.jpg
851 ms
pixel
21 ms
429 ms
index.html
206 ms
rta.js
18 ms
beacon.js
6 ms
rta3.aspx
418 ms
jquery.min.js
13 ms
jquery.cookie.min.js
9 ms
ec.js
206 ms
etag
417 ms
activeview
14 ms
etag
207 ms
123blog.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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
123blog.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
123blog.tw SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
JA
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 123blog.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 Chinese language. Our system also found out that 123blog.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.
123blog.tw
Open Graph description is not detected on the main page of 123 Blog. 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: