9.2 sec in total
959 ms
7.5 sec
793 ms
Visit 2proo.net now to see the best up-to-date 2 Proo content for South Korea and also check out these interesting facts you probably never knew about 2proo.net
게임, 컴퓨터, 블로그, 트위터, 페이스북, SNS, IT, 스마트폰, 아이폰, 인터넷
Visit 2proo.netWe analyzed 2proo.net page load time and found that the first response time was 959 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
2proo.net performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value21.6 s
0/100
25%
Value18.4 s
0/100
10%
Value5,010 ms
0/100
30%
Value0.012
100/100
15%
Value20.7 s
2/100
10%
959 ms
1120 ms
953 ms
93 ms
1338 ms
Our browser made a total of 214 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original 2proo.net, 13% (27 requests) were made to S1.daumcdn.net and 12% (26 requests) were made to Tpc.googlesyndication.com. 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.7 MB (36%)
4.8 MB
3.1 MB
In fact, the total size of 2proo.net main page is 4.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 261.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. 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 261.6 kB or 80% of the original size.
Potential reduce by 33.0 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. 2 Proo images are well optimized though.
Potential reduce by 915.2 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.2 kB or 72% of the original size.
Potential reduce by 509.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. 2proo.net needs all CSS files to be minified and compressed as it can save up to 509.2 kB or 91% of the original size.
Number of requests can be reduced by 88 (43%)
206
118
The browser has sent 206 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 2 Proo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
2proo.net
959 ms
style.css
1120 ms
imagefix.js
953 ms
plusone.js
93 ms
shareEntryWithSNS.css
1338 ms
shareEntryWithSNS.js
1338 ms
lightbox.min.css
1341 ms
style.css
1345 ms
profile.js
1588 ms
jigu-latest.min.js
1887 ms
T.js
1567 ms
EAF2.js
1798 ms
common.js
2271 ms
gallery.js
1579 ms
flash.js
1800 ms
PHON.js
1814 ms
swfobject.js
1825 ms
dialog.css
2028 ms
reset.css
2031 ms
tabloid.css
2557 ms
items.css
2300 ms
util.css
2139 ms
tistory-grid-min.css
2992 ms
items.js
2261 ms
menubar.css
2392 ms
636 ms
show_ads.js
24 ms
adsbygoogle.js
7 ms
_n2s_2proonit_2.js
1190 ms
addthis_widget.js
12 ms
functions.js
2259 ms
wcslog.js
8 ms
lightbox.min.js
2267 ms
td.min.js
1241 ms
roosevelt_dk_bt.js
890 ms
cb=gapi.loaded_0
21 ms
check.php
291 ms
bg2.jpg
497 ms
2445D34B56688E27253A9F
1505 ms
266E60365621671C09E36F
2017 ms
2234A33955EDED002AF364
1342 ms
2427AC4355D624C220667F
1618 ms
240F634F55AD79FB0D1E42
2185 ms
233F264C5511AE910E1890
1477 ms
2446AE3C5483F76913AE4F
1741 ms
2231F33E544D270C0FF6DC
1850 ms
2377AD4B538E17111919B0
1512 ms
26513741538E053A01C148
1343 ms
273D3B3653712F1B2D9706
1474 ms
226A5B3A53628B6915203E
1162 ms
2124034352AA1D730507C3
1301 ms
2624AF4C52A62CED0824DA
1857 ms
2232A9415220601C181141
1825 ms
133B734751671118233419
1427 ms
240F064052FC72A7404C2B
1851 ms
275C9C3452ADBF24060860
1736 ms
2proo-twitter.png
768 ms
tab_top.gif
40 ms
2445D34B56688E27253A9F
1711 ms
2610E24A5331375F13EDA7
1697 ms
tab_isleaf.gif
36 ms
tab_closed.gif
35 ms
navi_back_active.gif
35 ms
tab_treed.gif
38 ms
tab_treed_end.gif
36 ms
navi_back_active_end.gif
37 ms
2011_badge.png
35 ms
2010_best.png
38 ms
2009_best.png
37 ms
251EDA4053A339BE04D840
1531 ms
135C3B3550F9C8C12C7A5D
1519 ms
277E2442538DC4100D3FE0
1764 ms
close.png
266 ms
loading.gif
507 ms
prev.png
312 ms
next.png
265 ms
274B303C55D6CB542AED50
1464 ms
217DEE46548A00A90A2002
1809 ms
2541FF3451FFE3691018C0
2173 ms
17639C48509EB908060C53
2040 ms
204B9D044B331DF85F4E03
2177 ms
2736B733538D516902BB55
2163 ms
186608194BC5BFE14A2BA9
1697 ms
2proo-facebook.png
759 ms
2proo-google-plus.png
757 ms
2proo-rss.png
761 ms
2proo-mail.png
757 ms
bestofbest.png
1061 ms
powerpress.jpg
1061 ms
powerrevu.jpg
1061 ms
powerhook.jpg
1286 ms
160E7B0B4A0E2AF8930459
2250 ms
211F813F52B7759F038777
1458 ms
217B40425234D06F0A540F
1749 ms
2153033651FFF6731C08C0
2487 ms
12611839507FF6AC2B123B
1851 ms
1562901649C8D11B7562F3
1762 ms
112D774F5092C1011644AA
1410 ms
2376CD4F50F9D2C83E0BC1
1323 ms
16511A505092BCD60325D7
1320 ms
157085505079CBFF3DE580
1322 ms
1867C31C4CBF2A88069B07
1281 ms
1459521F4A154E7B31F169
1454 ms
1123131749C8D21F5557B8
1798 ms
266E60365621671C09E36F
2241 ms
2253354F538D80271CF3C4
1985 ms
2234A33955EDED002AF364
1318 ms
217AE5455339CA643082A0
1319 ms
2339E43A54836AB3110D36
1512 ms
263D9A3352E8B5A6199104
1541 ms
2249B536520562020D6220
2105 ms
2036B4234A15459217A01D
1863 ms
223D784654837F452054CC
1402 ms
all.js
198 ms
header.jpg
1002 ms
menu.gif
479 ms
searchbox.gif
451 ms
sidesep.gif
483 ms
ca-pub-2996290631316423.js
100 ms
zrt_lookup.html
158 ms
show_ads_impl.js
94 ms
72.gif
423 ms
widgetsep.png
432 ms
icons.gif
645 ms
ads
417 ms
osd.js
48 ms
ads
394 ms
_n2s_2proonit_336_280.html
493 ms
ads
339 ms
190 ms
xd_arbiter.php
182 ms
xd_arbiter.php
440 ms
cb=gapi.loaded_1
90 ms
cb=gapi.loaded_2
104 ms
person
287 ms
widgets.js
140 ms
footer.jpg
1232 ms
wp-logo.png
723 ms
m
683 ms
analytics.js
90 ms
jquery.min.js
167 ms
collect
55 ms
postmessageRelay
161 ms
300lo.json
133 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
540 ms
footsteps
1650 ms
sh.7c7179124ea24ac6ba46caac.html
50 ms
11647380608117599057
245 ms
abg.js
246 ms
m_js_controller.js
417 ms
googlelogo_color_112x36dp.png
505 ms
rs=AGLTcCOIysoEmtW85aiKIBLdKHmHc4_EPw
46 ms
rs=AGLTcCPhDrHY2vagSjsLFOxeufqSzVU3ow
45 ms
rs=AGLTcCOvAWAIwZ-qjnJEzv_BcS3vnXe-Og
148 ms
css
267 ms
css
517 ms
api.js
136 ms
core:rpc:shindig.random:shindig.sha1.js
438 ms
2536007149-postmessagerelay.js
438 ms
photo.jpg
519 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
582 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
651 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
651 ms
xd_arbiter.php
301 ms
layers.3643cb2e25fb91c29386.js
148 ms
jquery.min.js
336 ms
_n2s_banner_common_v4.js
1807 ms
rs=AGLTcCOvAWAIwZ-qjnJEzv_BcS3vnXe-Og
262 ms
x_button_blue2.png
253 ms
s
242 ms
redir.html
404 ms
ko.js
103 ms
favicon
303 ms
nessie_icon_tiamat_white.png
102 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
233 ms
rs=AGLTcCOvAWAIwZ-qjnJEzv_BcS3vnXe-Og
70 ms
1110483011076234234
143 ms
powered-by-google.png
78 ms
3612101313967097366
121 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
173 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
179 ms
follow_button.6a78875565a912489e9aef879c881358.ko.html
106 ms
1486599094210719689
165 ms
16007383708153807406
126 ms
7668319945654874025
110 ms
1194220173060472603
173 ms
info.json
222 ms
2776294190211992454
145 ms
11780329468857426023
135 ms
iframe.html
119 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
66 ms
2010514829645880737
116 ms
17514935314301472097
105 ms
6820756480564368508
96 ms
18073282122023566340
128 ms
pixel
134 ms
16162285747073343807
86 ms
2244794566658057827
114 ms
8566062469964251933
49 ms
679652595953022272
38 ms
18041984748437253081
57 ms
10608946043997531416
35 ms
5778414452700825082
57 ms
4879422396540341646
61 ms
jot
101 ms
398.b1907833e17d0f2ae2d0.js
17 ms
418.c1e799867a24cec49c32.js
14 ms
282.e0306c23072913fd0749.js
13 ms
462.e1ea0a277a6d8506fcc8.js
14 ms
323.f23492176de8311ca24d.js
14 ms
activeview
14 ms
_n2s_adinfo_nitmus_common.php
1168 ms
activeview
17 ms
ui
31 ms
2proo.net 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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
2proo.net 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
2proo.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 2proo.net can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that 2proo.net 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.
2proo.net
Open Graph data is detected on the main page of 2 Proo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: