4.7 sec in total
683 ms
3.6 sec
456 ms
Click here to check amazing Slowtrip content. Otherwise, check out these important facts you probably never knew about slowtrip.kr
Visit slowtrip.krWe analyzed Slowtrip.kr page load time and found that the first response time was 683 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
slowtrip.kr performance score
683 ms
233 ms
11 ms
290 ms
207 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Slowtrip.kr, 40% (38 requests) were made to Blogimgs.naver.net and 17% (16 requests) were made to T.static.blog.naver.net. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Blogfiles14.naver.net.
Page size can be reduced by 1.2 MB (70%)
1.7 MB
519.3 kB
In fact, the total size of Slowtrip.kr 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. 70% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 430 B
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 430 B or 44% of the original size.
Potential reduce by 53.7 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, Slowtrip needs image optimization as it can save up to 53.7 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 915.4 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 915.4 kB or 74% of the original size.
Potential reduce by 248.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. Slowtrip.kr needs all CSS files to be minified and compressed as it can save up to 248.3 kB or 85% of the original size.
Number of requests can be reduced by 71 (75%)
95
24
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Slowtrip. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
slowtrip.kr
683 ms
mc2yo
233 ms
Frameset-981964519.js
11 ms
PostList.nhn
290 ms
NBlogHidden.nhn
207 ms
Hidden-597428542.js
7 ms
MusicPlayer-449972894.js
19 ms
LayoutTopCommon-484882993.css
23 ms
player-846d457.css
42 ms
RemoveSubDomain-dea9950.js
44 ms
Jindo152-363950062.js
48 ms
LayoutTopCommon-730083628.js
45 ms
JindoComponent-318925938.js
63 ms
PostList-1027637939.css
46 ms
gnb_quirks_euckr.nhn
127 ms
likeit_blog.css
111 ms
likeit.css
151 ms
SeViewerBlog-165931490.css
40 ms
PostTopCommon-327917359.js
41 ms
splugin.js
166 ms
PostBottomCommon-1023812380.js
111 ms
PostBottomCommon_utf8-169531666.js
100 ms
likeIt.list.js
112 ms
allowSwfForChrome-7dd9772.js
108 ms
LayoutBottomCommon-902441421.js
158 ms
slowtrip_blog.jpg
2071 ms
spc.gif
170 ms
PostList.nhn
311 ms
IMG_0517.jpg
1186 ms
dthumb.phinf.naver.net
694 ms
blank.gif
171 ms
btn_confirm2.gif
165 ms
O%ED%98%95%20%EC%8A%AC%EB%A1%9C%EC%9A%B0%ED%8A%B8%EB%A6%BD.JPG
457 ms
0028_login.png
166 ms
btn_qk_set.gif
167 ms
btn_what2.gif
167 ms
btn_clse_ly2.gif
169 ms
spc.gif
168 ms
btn_urlcopy.gif
169 ms
btn_thin_close.gif
265 ms
btn_close8.gif
267 ms
ico_file.gif
267 ms
btn_download2.gif
267 ms
btn_cancel3.gif
267 ms
btn_close3.gif
268 ms
btn_close5.gif
268 ms
btn_confirm.gif
269 ms
btn_cancel.gif
270 ms
btn_close_1.gif
271 ms
btn_viewexif.gif
271 ms
btn_originaldn.gif
271 ms
tit_viewexif.gif
272 ms
ico_notice2.gif
272 ms
btn_close.gif
273 ms
btn_close3.gif
275 ms
btn_close.gif
273 ms
btn_ok.gif
273 ms
btn_close2.gif
275 ms
btn_confirm_pop2.gif
276 ms
btn_cancel_pop2.gif
276 ms
btn_close.gif
276 ms
ico_help.gif
154 ms
0154_966.gif
238 ms
promo_npay.png
236 ms
0006_ico1_down.gif
217 ms
bg_qk_ly2.gif
217 ms
sp_post_btn.png
217 ms
ico_tag.gif
218 ms
sp_arr1.gif
218 ms
bg_likeit2.gif
219 ms
sp_likeit_pc3.png
219 ms
WidgetListAsync.nhn
368 ms
lg_photoviewer.gif
138 ms
btn_left.gif
138 ms
btn_right.gif
139 ms
btn_original2.png
140 ms
btn_close.gif
139 ms
0102_image.gif
139 ms
0156_back.gif
143 ms
weather_19_s_bg.gif
143 ms
btn_blogsearch.gif
140 ms
shadow.png
140 ms
shadow02.png
140 ms
bg_not_available_word.gif
141 ms
O%C7%FC+%BD%BD%B7%CE%BF%EC%C6%AE%B8%B3.JPG
489 ms
1085752.gif
63 ms
0162_icon.gif
26 ms
btn_rst_clse.gif
25 ms
ico_n_photo.gif
17 ms
weather_19_3s.png
471 ms
0137_head.gif
16 ms
0137_arw.gif
17 ms
0138_footer.gif
15 ms
0138_head.gif
5 ms
0138_body.gif
5 ms
getLoginStatus.nhn
689 ms
slowtrip.kr SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Slowtrip.kr can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Slowtrip.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.
slowtrip.kr
Open Graph description is not detected on the main page of Slowtrip. 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: