12.6 sec in total
2 sec
10 sec
612 ms
Visit ozrank.co.kr now to see the best up-to-date Ozrank content for South Korea and also check out these interesting facts you probably never knew about ozrank.co.kr
국내외의 흥미롭고, 유익한 순위와 통계 자료를 소개하는 블로그입니다.
Visit ozrank.co.krWe analyzed Ozrank.co.kr page load time and found that the first response time was 2 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.
ozrank.co.kr performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value9.8 s
0/100
25%
Value7.6 s
25/100
10%
Value380 ms
70/100
30%
Value0.025
100/100
15%
Value9.7 s
28/100
10%
2018 ms
703 ms
618 ms
651 ms
863 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Ozrank.co.kr, 16% (25 requests) were made to S1.daumcdn.net and 9% (14 requests) were made to Blogpfthumb.phinf.naver.net. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Story-web-0.kakaocdn.net.
Page size can be reduced by 1.8 MB (41%)
4.4 MB
2.6 MB
In fact, the total size of Ozrank.co.kr main page is 4.4 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.0 MB which makes up the majority of the site volume.
Potential reduce by 233.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. 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 233.9 kB or 80% of the original size.
Potential reduce by 89.1 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. Ozrank images are well optimized though.
Potential reduce by 966.5 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 966.5 kB or 65% of the original size.
Potential reduce by 551.4 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. Ozrank.co.kr needs all CSS files to be minified and compressed as it can save up to 551.4 kB or 91% of the original size.
Number of requests can be reduced by 68 (45%)
151
83
The browser has sent 151 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ozrank. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
ozrank.co.kr
2018 ms
style.css
703 ms
lightbox.min.css
618 ms
style.css
651 ms
profile.js
863 ms
jigu-latest.min.js
1145 ms
T.js
706 ms
EAF2.js
993 ms
common.js
1187 ms
gallery.js
874 ms
flash.js
946 ms
PHON.js
1072 ms
swfobject.js
1091 ms
dialog.css
1178 ms
reset.css
1245 ms
tabloid.css
1739 ms
items.css
1506 ms
util.css
1369 ms
tistory-grid-min.css
2129 ms
items.js
1376 ms
menubar.css
1503 ms
addthis_widget.js
35 ms
669 ms
adsbygoogle.js
15 ms
WidgetRender.nhn
479 ms
searchDragSelection.js
1144 ms
lightbox.min.js
1115 ms
td.min.js
922 ms
roosevelt_dk_bt.js
279 ms
check.php
305 ms
tab_top.gif
500 ms
count.php
494 ms
rss.gif
309 ms
2769303656D2BF6F1CCCD5
2447 ms
2447E04556CDCF05103E2B
1499 ms
2420D74656C33A8235C587
1069 ms
2129D83C56B9FF60072E9A
1027 ms
266D263555181DEE1FC1A3
1598 ms
241072505517B6B025835B
1363 ms
23393042553644BE3595BE
1771 ms
2266FF405501A6E421EA12
1776 ms
225BAD4155B8C664161224
1266 ms
2377A450557D9E6F1177EC
1253 ms
25470347558D9BA918FFE6
2089 ms
262A493C55E8533F2CF592
1167 ms
2678864555A141931E2FA7
1476 ms
270D053B558AB70D084D43
1098 ms
21591B3F567C102306D51D
1387 ms
220CCE33564211EA2CF0BB
1779 ms
2769303656D2BF6F1CCCD5
1883 ms
2769303656D2BF6F1CCCD5
2143 ms
new_ico_5.gif
507 ms
tab_isleaf.gif
505 ms
22124737566D62F3345A78
2927 ms
close.png
279 ms
loading.gif
460 ms
prev.png
278 ms
next.png
276 ms
2152C43A559947841C22A2
1691 ms
2578A15054E9DEFE15A821
1925 ms
26397241559C02BD01C1B1
1410 ms
251BCE3556B9941231337B
1237 ms
22225E3E569E53570E4BA2
1320 ms
2420D74656C33A8235C587
1221 ms
217655505640C47B02A7B7
2442 ms
25470347558D9BA918FFE6
1926 ms
270DCB3A55BCD80505B09B
1961 ms
2447E04556CDCF05103E2B
1565 ms
215D4F4C563A17E611D6D4
1594 ms
270D053B558AB70D084D43
1058 ms
2560A9495512C7612B7A9D
1924 ms
sdk.js
454 ms
kakao.story.min.js
505 ms
layers.648fb6c882fbeb98be27.js
49 ms
ca-pub-6520695641120375.js
254 ms
zrt_lookup.html
245 ms
show_ads_impl.js
162 ms
WidgetView.nhn
266 ms
index.html
1069 ms
ads
264 ms
jquery.min.js
126 ms
osd.js
58 ms
section_connect_widget-2fd595e.css
643 ms
jindo.min-78c07e0.js
650 ms
agent.ie11-6694cec.js
649 ms
BuddyConnectWidget-242001126.js
647 ms
kakao.story.min.js
1265 ms
172 ms
xd_arbiter.php
288 ms
xd_arbiter.php
466 ms
300lo.json
62 ms
8245714425829110859
159 ms
abg.js
210 ms
m_js_controller.js
230 ms
googlelogo_color_112x36dp.png
224 ms
footsteps
2126 ms
sh.7c7179124ea24ac6ba46caac.html
89 ms
custom-messages.b767dde2b68c466842fa.js
98 ms
page.php
128 ms
s
59 ms
x_button_blue2.png
60 ms
n9bB4wqXk2L.css
322 ms
_rx8naC75Dy.js
518 ms
3o1espZ6Mhb.js
546 ms
nfTYZZc0iSn.js
683 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
4 ms
bg_skin8.gif
310 ms
blogpfthumb.phinf.naver.net
483 ms
b.gif
278 ms
login_basic.gif
40 ms
wish%289812%29+BROCHURE.jpg
50 ms
profileImage.jpg
50 ms
baby-443393__180.jpg
49 ms
pixabay_com_20160104_121143.jpg
55 ms
%C8%A3%C7%F6%BF%F9%B5%E5.PNG
50 ms
tumblr_mf3n35v1cX1r14f0xo1_500.jpg
87 ms
earth.gif
53 ms
%C0%E5%B9%CC.jpg
56 ms
050129+0161.jpg
54 ms
20131028_124319.jpg
59 ms
006.png
60 ms
abs01_IMG_0352-5.jpg
55 ms
img_profile_none.gif
277 ms
b.gif
264 ms
ico_arr2.gif
264 ms
btn_skin8_addn.gif
292 ms
btn_skin9_admin.png
276 ms
btn_skin9_download.png
279 ms
btn_skin9_help.png
279 ms
views2.json
109 ms
widget_logo.gif
844 ms
info.html
767 ms
2719A34E5559DF9A08CC50
906 ms
2402FD365544DA242F88BA
952 ms
2678864555A141931E2FA7
1193 ms
2743C237556B254522C4DC
1584 ms
270D053B558AB70D084D43
808 ms
login_basic.gif
33 ms
11042977_353335104873194_1831886780073304306_n.png
490 ms
wL6VQj7Ab77.png
74 ms
s7jcwEQH7Sx.png
81 ms
10998391_353330121540359_3572890470608945201_n.png
556 ms
follow
1409 ms
activeview
14 ms
ar_up.png
301 ms
ar_dn.png
400 ms
level_mark_3.gif
465 ms
R9a_DtVRZgv.js
77 ms
cUDgRFxaoIk.js
80 ms
0JBr1QHp8Gi.js
82 ms
kDOzhTr2W91.js
134 ms
follow.css
1397 ms
boot.min.js
1620 ms
follow.min.js
2962 ms
ozrank.co.kr 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
Image elements do not have [alt] attributes
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.
ozrank.co.kr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
ozrank.co.kr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ozrank.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 Ozrank.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.
ozrank.co.kr
Open Graph data is detected on the main page of Ozrank. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: