12.4 sec in total
1.8 sec
9.8 sec
777 ms
Visit cappleblog.co.kr now to see the best up-to-date Cappleblog content for South Korea and also check out these interesting facts you probably never knew about cappleblog.co.kr
Visit cappleblog.co.krWe analyzed Cappleblog.co.kr page load time and found that the first response time was 1.8 sec and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
cappleblog.co.kr performance score
1819 ms
13 ms
1561 ms
1607 ms
1398 ms
Our browser made a total of 227 requests to load all elements on the main page. We found that 1% of them (3 requests) were addressed to the original Cappleblog.co.kr, 11% (26 requests) were made to S1.daumcdn.net and 8% (19 requests) were made to Ts.daumcdn.net. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source S1.daumcdn.net.
Page size can be reduced by 1.1 MB (43%)
2.7 MB
1.5 MB
In fact, the total size of Cappleblog.co.kr main page is 2.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. 55% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 103.7 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 103.7 kB or 81% of the original size.
Potential reduce by 120.2 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. Cappleblog images are well optimized though.
Potential reduce by 373.6 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 373.6 kB or 61% of the original size.
Potential reduce by 541.8 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. Cappleblog.co.kr needs all CSS files to be minified and compressed as it can save up to 541.8 kB or 90% of the original size.
Number of requests can be reduced by 98 (49%)
198
100
The browser has sent 198 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cappleblog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
cappleblog.co.kr
1819 ms
ga.js
13 ms
style.css
1561 ms
CAppleJSH.js
1607 ms
captcha.css
1398 ms
lightbox.min.css
1458 ms
style.css
1458 ms
profile.js
1702 ms
jigu-latest.min.js
1958 ms
T.js
1493 ms
EAF2.js
1807 ms
common.js
2400 ms
gallery.js
1694 ms
flash.js
1747 ms
PHON.js
1930 ms
swfobject.js
1940 ms
dialog.css
2005 ms
reset.css
2012 ms
tabloid.css
2687 ms
items.css
2416 ms
util.css
2199 ms
tistory-grid-min.css
3027 ms
items.js
2218 ms
menubar.css
2443 ms
rainbow.js
2423 ms
628 ms
__utm.gif
10 ms
wp_ad_300_js.php
739 ms
WidgetRender.nhn
749 ms
rsense_ad.js
716 ms
CAppleJSF.js
478 ms
lightbox.min.js
1667 ms
td.min.js
1034 ms
roosevelt_dk_bt.js
593 ms
__utm.gif
10 ms
check.php
276 ms
style.css
443 ms
2149EA4753BA20C71F36A7
1341 ms
223F553C53B63A323535DA
1723 ms
2131C63953B529930CB019
1696 ms
2674B03553B3DED328F4FB
2119 ms
25650C36539AC3A42EA08A
2231 ms
217B9046538831C10FD1DC
1440 ms
247BDB435387EF583042D1
2127 ms
250BD53A5201601A029B58
1988 ms
2470634051CB75D7159812
1795 ms
2656633B51BA98C10EBFDB
2096 ms
2410E43D51B7DA662AC8D7
2096 ms
2556CB3A51B65EE130B274
1499 ms
2719B53D51A058344BC74A
1773 ms
015B4F3851A0094033371D
1954 ms
26643A33519BD5D42D8E4A
1947 ms
14181A4E50F5EDD904559D
2155 ms
1418803E50BF46982D2720
1691 ms
count.php
318 ms
223F553C53B63A323535DA
1531 ms
0319773E519CE3331E8F19
1759 ms
223F553C53B63A323535DA
1338 ms
2642563351C2EAD002D944
1601 ms
01666F47518F1CAF3390A9
1850 ms
1226C850509BD02535E570
2229 ms
253874345165198302C530
1750 ms
233B7235516803E302A94E
1696 ms
close.png
209 ms
loading.gif
481 ms
prev.png
255 ms
next.png
239 ms
211E773A51A5E1C03A01CA
1750 ms
2131C63953B529930CB019
1238 ms
2131C63953B529930CB019
1314 ms
2674B03553B3DED328F4FB
1911 ms
2611AF3351A1BD55294B0E
1806 ms
22259E35519EBA4D33CDA2
1820 ms
135438454F686AAF1200D4
1851 ms
171FD03A516623CC0A1F6C
1927 ms
2556CB3A51B65EE130B274
1355 ms
1971C24050C338660BAB5A
1657 ms
226ABF4E5163767A06DAE3
1758 ms
26643A33519BD5D42D8E4A
1516 ms
237EF736519AF49626475A
1764 ms
logo_capple.png
237 ms
N_FR220.png
477 ms
blogicon.png
434 ms
2149EA4753BA20C71F36A7
1194 ms
140D613F4F7A3F50308836
1196 ms
164BE0405022172A136E4B
1302 ms
0366E9375164D4CB324B9C
1384 ms
all.js
269 ms
menu01.png
461 ms
menu02.png
492 ms
menu03.png
781 ms
menu04.png
637 ms
menu05.png
638 ms
menu06.png
700 ms
container_bg.png
706 ms
wfr.php
1886 ms
c_arrow.gif
652 ms
bulld.gif
785 ms
bullc.gif
784 ms
arrow_grey_right.png
833 ms
WidgetView.nhn
293 ms
classic.js
6 ms
wait.gif
1389 ms
footer_right.png
1073 ms
plusone.js
68 ms
jquery.min.js
42 ms
35 ms
dpx.js
29 ms
tpid=1EE704455B25D55625031F36028DE7E7
14 ms
p
35 ms
cb=gapi.loaded_0
3 ms
footsteps
2024 ms
dpx
4 ms
match_redirect
9 ms
29931
20 ms
match_redirect
20 ms
tpid=CE29559E5B25D556A6234E3802E65B7E
6 ms
50 ms
xd_arbiter.php
237 ms
xd_arbiter.php
443 ms
lr.gif
8 ms
match_redirect
4 ms
sync
14 ms
section_connect_widget2-413879d.css
446 ms
jindo.min-78c07e0.js
452 ms
agent.ie11-6694cec.js
451 ms
BuddyConnectWidget-242001126.js
450 ms
BuddyConnectBriefWidget-898830988.js
450 ms
match_redirect
4 ms
CE29559E5B25D556A6234E3802E65B7E
38 ms
59 ms
match_redirect
6 ms
ProfilesEngineServlet
11 ms
ProfilesEngineServlet
21 ms
classicoutline.gif
3 ms
tc.js
9 ms
p
56 ms
tap.php
11 ms
exelate
5 ms
match_redirect
4 ms
v2
56 ms
dpx
9 ms
engine
88 ms
27519
32 ms
pixel
23 ms
generic
15 ms
i.match
183 ms
xrefid.xgi
10 ms
generic
9 ms
1407
170 ms
2964
12 ms
2831
254 ms
pixel
15 ms
5386
13 ms
2981
201 ms
13583
11 ms
3085
22 ms
52154.gif
6 ms
4448
14 ms
19 ms
4470
14 ms
25 ms
58 ms
line_skin20_v.gif
47 ms
login_basic.gif
50 ms
ico_arr2.gif
509 ms
%BB%E7%BA%BB_-_c30-park1978p.jpg
85 ms
%B7%CE%B0%ED.png
81 ms
tumblr_m8jk6nInJO1qzt4vjo1_r1_500.gif
84 ms
%BB%E7%BA%BB_-_41ab8fc53c245-destiny1052.jpg
85 ms
%BB%E7%BA%BB_-_%C1%BE%B9%CE%BB%E7%C1%F8-hansdg119.jpg
82 ms
%B5%BF%B0%C7%B8%F1%BF%E5.jpg
98 ms
office.jpg
133 ms
20131013_194245.jpg
132 ms
b.gif
507 ms
ico_skin21_arr.gif
42 ms
ico_up.gif
40 ms
btn_skin20_pgn.gif
42 ms
i.match
108 ms
btn_skin21_add_2.png
37 ms
btn_skin20_adm_2.png
36 ms
btn_skin20_dnld_2.png
38 ms
spotx_match
3 ms
fb_match
9 ms
u.php
26 ms
an
6 ms
lj_match
5 ms
merge
11 ms
4229
16 ms
cw_match
5 ms
rtset
21 ms
rb_match
4 ms
tap.php
9 ms
view_ad.html
511 ms
ox_match
4 ms
sd
6 ms
pm_match
5 ms
Pug
45 ms
pixel
16 ms
g_match
5 ms
match_redirect
7 ms
pixel
45 ms
aa_px
4 ms
house_remon_300600.gif
1992 ms
jquery-1.6.2.min.js
707 ms
300.php
686 ms
rta.js
26 ms
pop_ad.php
702 ms
210.png
472 ms
index.php
692 ms
style.css
462 ms
jquery.min.js
6 ms
wowslider.js
660 ms
script.js
461 ms
249462708s.jpg
1158 ms
320_bg.jpg
464 ms
inter_top.jpg
470 ms
md.png
478 ms
241437906s.jpg
1160 ms
248051333s.jpg
1161 ms
226122836s.jpg
1164 ms
250474184s.jpg
1204 ms
234707803s.jpg
1234 ms
230836148s.jpg
1590 ms
211639220s.jpg
1602 ms
245785547s.jpg
1602 ms
248620379s.jpg
1386 ms
cappleblog.co.kr SEO score
KO
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cappleblog.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean 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 Cappleblog.co.kr 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.
cappleblog.co.kr
Open Graph data is detected on the main page of Cappleblog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: