10.1 sec in total
610 ms
9.4 sec
132 ms
Welcome to rankey.com homepage info - get ready to check Rankey best content for South Korea right away, or after learning these important things about rankey.com
PC, 모바일 시장조사. 웹사이트, 앱 순위 발표. 쇼핑몰 결산보고서, 주간리포트, IT컬럼 제공.
Visit rankey.comWe analyzed Rankey.com page load time and found that the first response time was 610 ms and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
rankey.com performance score
610 ms
2062 ms
798 ms
397 ms
837 ms
Our browser made a total of 189 requests to load all elements on the main page. We found that 95% of them (179 requests) were addressed to the original Rankey.com, 1% (2 requests) were made to Gtb1.acecounter.com and 1% (2 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Rankey.com.
Page size can be reduced by 794.1 kB (45%)
1.8 MB
981.6 kB
In fact, the total size of Rankey.com main page is 1.8 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. 30% of websites need less resources to load. Images take 913.8 kB which makes up the majority of the site volume.
Potential reduce by 107.6 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 13.5 kB, which is 11% 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 107.6 kB or 84% of the original size.
Potential reduce by 105.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. Obviously, Rankey needs image optimization as it can save up to 105.2 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 363.7 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 363.7 kB or 77% of the original size.
Potential reduce by 217.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. Rankey.com needs all CSS files to be minified and compressed as it can save up to 217.6 kB or 84% of the original size.
Number of requests can be reduced by 104 (56%)
187
83
The browser has sent 187 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rankey. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
rankey.com
610 ms
www.rankey.com
2062 ms
style.css
798 ms
slideStyle.css
397 ms
jquery-1.4.2.min.js
837 ms
FusionCharts.js
407 ms
jquery.xmldom-1.0.min.js
409 ms
ChartFun.js
595 ms
index.js
806 ms
common.js
612 ms
jquery.tools.min.js
791 ms
main_menu.js
816 ms
main_banner.js
989 ms
flashobj.js
993 ms
highcharts.src.js
1597 ms
excanvas.compiled.js
1006 ms
common.js
1019 ms
main_201204.css
842 ms
common_rank.js
1391 ms
auto_complete.js
998 ms
getBanner.php
825 ms
getBanner.php
838 ms
common_rank_mobile.js
1035 ms
wcslog.js
19 ms
t_small-a.png
180 ms
top_go_home.gif
208 ms
top_go_toolbar.gif
211 ms
top_big3_01on.gif
205 ms
top_big3_02on.gif
204 ms
top_big3_03on.gif
208 ms
top_btu_login.gif
203 ms
top_menu_join.gif
402 ms
top_menu_customer.gif
398 ms
top_menu_help.gif
398 ms
top_menu_sitemap.gif
401 ms
newloginform_01.png
402 ms
newloginform_02.png
406 ms
newloginform_04.png
593 ms
newloginform_05.png
595 ms
newloginform_06.png
596 ms
newloginform_07.png
598 ms
newloginform_08.png
599 ms
newloginform_09.png
609 ms
newloginform_10.png
790 ms
newloginform_11.png
791 ms
newloginform_13.png
795 ms
newloginform_14.png
796 ms
newloginform_15.png
799 ms
newloginform_16.png
811 ms
newloginform_17.png
989 ms
newloginform_18.png
989 ms
spacer.gif
993 ms
tab_general_off.gif
995 ms
tab_logn_on.gif
998 ms
login_01.gif
1017 ms
login_03.gif
1185 ms
login_05.gif
1186 ms
btn_login2.gif
1192 ms
btn_re_send.gif
1194 ms
btn_what_logn.gif
1201 ms
layer_logn.png
1210 ms
gtb1.acecounter.com
620 ms
like.php
199 ms
acecounter_mainscript.js
1189 ms
top_logo.gif
1221 ms
select_on.gif
1221 ms
layer_on.gif
1220 ms
top_search_btn.gif
1220 ms
search01.gif
1236 ms
vpc6VNjRPXV.js
477 ms
LVx-xkvaJ0b.png
539 ms
menu_ranking_on.gif
1192 ms
menu_ranking_01_on.gif
1193 ms
menu_ranking_02_on.gif
1194 ms
menu_ranking_03_on.gif
1197 ms
menu_ranking_04_on.gif
1207 ms
menu_ranking_05_on.gif
1230 ms
menu_ranking_06_on.gif
1193 ms
menu_data_on.gif
1193 ms
menu_data_01_on.gif
1197 ms
menu_data_02_on.gif
1199 ms
menu_data_03_on.gif
1210 ms
menu_data_04_on.gif
1230 ms
menu_data_05_on.gif
1194 ms
menu_data_06_on.gif
1193 ms
menu_data_07_on.gif
1197 ms
menu_data_banner.gif
1200 ms
menu_mobile_on.gif
1209 ms
menu_mobile_01_on.gif
1229 ms
menu_mobile_02_on.gif
1191 ms
menu_mobile_03_on.gif
1192 ms
menu_mobile_04_on.gif
1197 ms
menu_insight_on.gif
1200 ms
menu_insight_01_on.gif
1209 ms
menu_insight_02_on.gif
1229 ms
menu_insight_03_on.gif
1192 ms
menu_insight_04_on.gif
1193 ms
menu_data_08_on.gif
1196 ms
menu_cnsulting_01_on.gif
1199 ms
menu_cnsulting_02_on.gif
1204 ms
menu_cnsulting_03_on.gif
1229 ms
ga.js
33 ms
m
650 ms
gtb1.acecounter.com
427 ms
ajax_index.php
1300 ms
menu_cnsulting_04_on.gif
1159 ms
menu_blog_on.gif
1169 ms
menu_blog_01_on.gif
1172 ms
menu_blog_02_on.gif
1185 ms
__utm.gif
25 ms
menu_blog_03_on.gif
1216 ms
menu_blog_04_on.gif
1190 ms
menu_service_on.gif
1201 ms
menu_service_01_on.gif
1203 ms
menu_service_02_on.gif
1212 ms
menu_service_03_on.gif
1255 ms
menu_service_04_on.gif
1285 ms
menu_service_05_on.gif
1190 ms
menu_all_on.gif
1203 ms
menu_blog_05_on.gif
1204 ms
layer_pop_bg_20120924.png
1213 ms
btn_detail_view.gif
1257 ms
btn_close.gif
1279 ms
2015_annual_e-commerce.jpg
1593 ms
blogbanner_01.jpg
1215 ms
mainbanner_20130723.jpg
1613 ms
mobile_data_service.jpg
2019 ms
banner_sns_f.gif
1262 ms
ranking_icon_no3.gif
1274 ms
data_title.gif
1220 ms
data_bullet.gif
1291 ms
data_icon_week.gif
1321 ms
data_btu_report.gif
1405 ms
data_title_s01.gif
1470 ms
data_title_s02.gif
1464 ms
data_title_s03.gif
1394 ms
app_title.gif
1420 ms
list_arr_prev.gif
1417 ms
list_arr_next.gif
1488 ms
week_title01.gif
1501 ms
more.gif
1521 ms
17882_rankey.jpg
1422 ms
column_title.gif
1416 ms
hkj.gif
1493 ms
facebook_title.gif
1498 ms
facebook_img.gif
1516 ms
text_more.gif
1482 ms
btn_prev2.gif
1430 ms
btn_next2.gif
1425 ms
newsletter_title.gif
1497 ms
newsletter_btu_apply.gif
1497 ms
notice_title.gif
1508 ms
icon_new_orange.gif
1483 ms
lightgrey_topleft.gif
1432 ms
lightgrey_topright.gif
1425 ms
lightgrey_btmleft.gif
1500 ms
lightgrey_btmright.gif
1493 ms
btn_closepopup.gif
1502 ms
copyright_menu.gif
1485 ms
footer_new_03.gif
1407 ms
copyright_090120.gif
1345 ms
footer_new_05.gif
1386 ms
2016newyearsday.jpg
2091 ms
btn_close3.gif
1292 ms
re_install_popup.png
1491 ms
top_bg.gif
1234 ms
newloginform_03.png
1211 ms
newloginform_12.png
1300 ms
top_search_bg.gif
1286 ms
menu_bg.gif
1301 ms
navigator.png
1241 ms
banner_sns_bg.gif
1309 ms
1338512853241.gif
1556 ms
1425530252286.gif
1324 ms
ic_arrow_up.gif
1302 ms
bg_hline.gif
1241 ms
icon_s.gif
1313 ms
thisweek_icon_0.gif
1401 ms
9.gif
1397 ms
rankey_com_tmp_20121221.jpg
1328 ms
tab01_on.jpg
201 ms
tab02_on.jpg
205 ms
tab03_on.jpg
201 ms
btn_prev_over.gif
200 ms
btn_next_over.gif
210 ms
quick_01_over.gif
202 ms
quick_02_over.gif
397 ms
quick_03_over.gif
398 ms
quick_05_over.gif
398 ms
rankey.com SEO score
KO
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rankey.com 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 Rankey.com main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
rankey.com
Open Graph description is not detected on the main page of Rankey. 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: