7.6 sec in total
1.4 sec
5.6 sec
554 ms
Click here to check amazing R 16 Korea content for United States. Otherwise, check out these important facts you probably never knew about r16korea.com
R16 Korea는 전세계적인 스트리트 댄스 토너먼트 대회이자 도시 문화 축제입니다.
Visit r16korea.comWe analyzed R16korea.com page load time and found that the first response time was 1.4 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
r16korea.com performance score
1439 ms
20 ms
149 ms
202 ms
391 ms
Our browser made a total of 151 requests to load all elements on the main page. We found that 38% of them (57 requests) were addressed to the original R16korea.com, 22% (33 requests) were made to Static.xx.fbcdn.net and 9% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Cartelimg.cafe24.com.
Page size can be reduced by 535.7 kB (21%)
2.6 MB
2.1 MB
In fact, the total size of R16korea.com main page is 2.6 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 2.1 MB which makes up the majority of the site volume.
Potential reduce by 42.9 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 10.7 kB, which is 20% 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 42.9 kB or 81% of the original size.
Potential reduce by 201.8 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. R 16 Korea images are well optimized though.
Potential reduce by 194.1 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 194.1 kB or 63% of the original size.
Potential reduce by 96.9 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. R16korea.com needs all CSS files to be minified and compressed as it can save up to 96.9 kB or 81% of the original size.
Number of requests can be reduced by 73 (49%)
148
75
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of R 16 Korea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
www.r16korea.com
1439 ms
analytics.js
20 ms
fbevents.js
149 ms
wp-emoji-release.min.js
202 ms
frontend_style.css
391 ms
jquery.fancybox-1.3.4.css
393 ms
nivo-lightbox.css
395 ms
default.css
401 ms
pagenavi-css.css
400 ms
boldr.min.css
402 ms
style.css
585 ms
css
23 ms
css
35 ms
style.css
586 ms
jquery.js
782 ms
jquery-migrate.min.js
601 ms
jquery.mousewheel-3.0.4.pack.js
599 ms
jquery.fancybox-1.3.4.pack.js
602 ms
nivo-lightbox.min.js
780 ms
script.js
803 ms
boldr.min.js
804 ms
velocity.min.js
17 ms
enhance.js
814 ms
zoom.css
816 ms
classes.css
974 ms
collect
25 ms
collect
56 ms
88 ms
webbg13.jpg
2404 ms
R16_TICKET_BANNER_KOR.jpg
643 ms
boldr.min.css
219 ms
select-arrow.png
219 ms
search-icon.png
218 ms
11952816_10153275142944737_6195743576017970979_o-668x392.jpg
783 ms
road-to-r16-recap-cover-668x392.jpg
640 ms
DM8F9377-668x392.jpg
615 ms
EP-1-SCREENCAP-edit-668x392.jpg
1017 ms
Slide2-668x392.png
1438 ms
11952816_10153275142944737_6195743576017970979_o-260x260.jpg
641 ms
road-to-r16-recap-cover-260x260.jpg
973 ms
EP-1-SCREENCAP-edit-260x260.jpg
811 ms
Slide2-260x260.png
1238 ms
Slide9-260x260.png
978 ms
mainb.png
1008 ms
bboydojor16banner.jpg
1361 ms
tickban.jpg
1175 ms
r16b.jpg
1204 ms
instagram.jpg
1215 ms
kto.jpg
1371 ms
mcb.jpg
1424 ms
undis.jpg
1425 ms
bc.jpg
1436 ms
arts.jpg
1613 ms
puma.jpg
1614 ms
snrd.jpg
1624 ms
alca.jpg
1635 ms
mtn.jpg
1636 ms
caliph.jpg
1636 ms
swag.jpg
1748 ms
kbsn.jpg
1760 ms
cartel.jpg
1793 ms
ist.png
1813 ms
facebook.png
1853 ms
twitter.png
1853 ms
youtube.png
1942 ms
r16_logo_180.png
964 ms
surveypop.jpg
1608 ms
1753 ms
arrow-left.png
1933 ms
widgets.js
87 ms
likebox.php
384 ms
72 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
124 ms
syndication
94 ms
304104327243501569
194 ms
410ucuAGgaJ.css
293 ms
pERLJfhzcxv.css
361 ms
Czh0gDTFcBt.css
430 ms
Ek6lpayKeeB.css
568 ms
EoarYgA68t4.css
559 ms
5VZ003vMUZg.css
572 ms
dAhyk4_vXRy.css
505 ms
q68gy-v_YMF.js
626 ms
FJmpeSpHpjS.js
640 ms
0wM5s1Khldu.js
582 ms
1bNoFZUdlYZ.js
652 ms
njO1TPvGzoR.js
649 ms
1QuX41zDRrx.js
650 ms
Oagsvfb4VWi.js
706 ms
LTv6ZK-5zxz.js
890 ms
1FCa-btixu2.js
696 ms
IjqSyiwKeaX.js
696 ms
yasHAKDGNFx.js
762 ms
pQrUxxo5oQp.js
773 ms
n6VgtouijQL.js
763 ms
b8XhdWI9eAN.js
765 ms
_UYztdBNTjs.js
773 ms
kvx5eeRG4FE.js
964 ms
Nn19HjwCsOL.js
830 ms
proxy.jpg
196 ms
proxy.jpg
219 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
30 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
86 ms
TVPHd8Qw_normal.png
83 ms
Mv4fgDci_normal.jpg
82 ms
DUL9cvyg_normal.jpeg
86 ms
jot
25 ms
12278778_935798676457327_1882026930409883864_n.jpg
355 ms
safe_image.php
334 ms
10995304_856141467756382_8193082431688141488_n.png
405 ms
1936070_888504587914418_1828347457881421168_n.jpg
536 ms
12705359_956383454454865_2528407618520892548_n.jpg
537 ms
12745704_1560205524297943_2279836071911584384_n.jpg
610 ms
424806_3153764399594_657352755_n.jpg
538 ms
10302021_452546748263535_5209381299739930098_n.jpg
539 ms
1937011_134681976925028_7930664164745547942_n.jpg
540 ms
10416622_1006021709474051_7965109272189003911_n.jpg
603 ms
944456_988807397823121_4527538904032789857_n.jpg
671 ms
12419430_496244657226262_444195630_n.jpg
604 ms
12378283_955467731167670_1755385650_n.jpg
608 ms
12514615_206094253075384_1670406910_n.jpg
608 ms
wL6VQj7Ab77.png
99 ms
s7jcwEQH7Sx.png
97 ms
QDwYpIaRyfG.png
98 ms
l5aPruN9xMM.png
100 ms
bNvHN6v1NeH.png
98 ms
b53Ajb4ihCP.gif
100 ms
K00K-UgnsKu.png
136 ms
K_65vAc89SX.png
68 ms
combined.css
14 ms
smoothDivScroll.css
5 ms
stack_161235.js
46 ms
jquery.min.js
5 ms
stackpile.api-bfb5078e74.js
34 ms
play_small.png
29 ms
917370_614083832072293_728042638_n.jpg
36 ms
small_share_sprite.png
15 ms
917530_1692591924332320_284482755_n.jpg
27 ms
12383464_997310137002207_1105975157_n.jpg
25 ms
12825785_1293469684001510_1802577840_n.jpg
24 ms
12797602_203811959983380_1086154047_n.jpg
22 ms
12784045_197776280591385_1717242356_n.jpg
21 ms
12141898_485285941673359_249198761_n.jpg
20 ms
12826275_822382587908454_98969411_n.jpg
25 ms
12751540_524388747732247_37837208_n.jpg
24 ms
collect
13 ms
collect
15 ms
stackpile.api-bfb5078e74.js
14 ms
nr-885.min.js
43 ms
a53393d12f
44 ms
I6-MnjEovm5.js
69 ms
r16korea.com SEO score
N/A
KR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise R16korea.com 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), while the claimed language is . Our system also found out that R16korea.com 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.
r16korea.com
Open Graph description is not detected on the main page of R 16 Korea. 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: