25.6 sec in total
1.6 sec
23.7 sec
407 ms
Welcome to weeklytrade.co.kr homepage info - get ready to check Weeklytrade best content for South Korea right away, or after learning these important things about weeklytrade.co.kr
Visit weeklytrade.co.krWe analyzed Weeklytrade.co.kr page load time and found that the first response time was 1.6 sec and then it took 24.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
weeklytrade.co.kr performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value7.7 s
3/100
25%
Value20.5 s
0/100
10%
Value5,410 ms
0/100
30%
Value0.069
96/100
15%
Value15.4 s
7/100
10%
1574 ms
598 ms
1228 ms
1891 ms
908 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 59% of them (66 requests) were addressed to the original Weeklytrade.co.kr, 9% (10 requests) were made to Static.xx.fbcdn.net and 8% (9 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain Weeklytrade.co.kr.
Page size can be reduced by 345.3 kB (45%)
767.5 kB
422.3 kB
In fact, the total size of Weeklytrade.co.kr main page is 767.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% 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. Javascripts take 373.7 kB which makes up the majority of the site volume.
Potential reduce by 45.3 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 45.3 kB or 75% of the original size.
Potential reduce by 19.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. Weeklytrade images are well optimized though.
Potential reduce by 232.0 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 232.0 kB or 62% of the original size.
Potential reduce by 48.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. Weeklytrade.co.kr needs all CSS files to be minified and compressed as it can save up to 48.9 kB or 85% of the original size.
Number of requests can be reduced by 56 (52%)
107
51
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weeklytrade. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
index.html
1574 ms
rankup_style.css
598 ms
rankup_style_news.css
1228 ms
prototype.js
1891 ms
form.js
908 ms
common.js
1449 ms
js_rolling.js
992 ms
language.pack.js
1135 ms
wcslog.js
22 ms
rankup_menu.js
1390 ms
rankup_popup.js
817 ms
nanumgothic.css
33 ms
adsbygoogle.js
11 ms
rankup_board.js
722 ms
skin_style.css
475 ms
rankup_tab.js
562 ms
logo_13899346510353.png
336 ms
banner_kita.png
591 ms
banner_02.png
469 ms
tm_login.gif
335 ms
tm_join.gif
334 ms
tm_mypage.gif
336 ms
top1_search_btn.gif
598 ms
top1_menu_bg1.gif
591 ms
top_menu_line.png
592 ms
top1_menu_bg3.gif
595 ms
dp_bclose.gif
609 ms
thumb_14600746326770.png
894 ms
thumb_14600196460936.jpg
894 ms
thumb_14600221686474.jpg
890 ms
thumb_14598984605398.jpg
889 ms
banner_14144864818526.gif
18427 ms
thumb_14600893476626.jpg
892 ms
thumb_14600810363725.jpg
18427 ms
thumb_14600801890255.jpg
18425 ms
thumb_14600230224098.jpg
18428 ms
thumb_14598981301757.jpg
18426 ms
thumb_14594839332900.jpg
18427 ms
thumb_14594728176370.jpg
19017 ms
thumb_14594725855840.jpg
19135 ms
thumb_14594187226922.jpg
18988 ms
no_75_50.gif
18814 ms
thumb_14599859257871.jpg
19015 ms
banner_14562958744588.gif
19294 ms
banner_14592391947677.gif
19498 ms
no_225_150.gif
19191 ms
mp_arrow_pre.gif
19278 ms
thumb_14600896195179.jpg
19484 ms
thumb_14600757673104.jpg
19374 ms
thumb_14594716961872.jpg
19584 ms
thumb_14594706805874.jpg
19699 ms
m
582 ms
load_category_item.ajax.php
19619 ms
NanumGothic-Regular.woff
328 ms
NanumGothic-Bold.woff
417 ms
NanumGothic-ExtraBold.woff
633 ms
ca-pub-2523653112194856.js
152 ms
zrt_lookup.html
207 ms
show_ads_impl.js
144 ms
ads
350 ms
osd.js
18 ms
multiProcess.html
19420 ms
thumb_14588724824272.jpg
19375 ms
mp_arrow_next.gif
19387 ms
banner_14599082501933.gif
20027 ms
sdk.js
122 ms
dot_ic03.gif
19372 ms
icon_top.gif
19322 ms
logo_gray.gif
19325 ms
top1_menu_bg2.gif
19330 ms
top_menu_bottom_bg1.gif
19384 ms
17830 ms
top_menu_bottom_bg2.gif
19450 ms
ads
299 ms
xd_arbiter.php
51 ms
xd_arbiter.php
240 ms
top_menu_bottom_bg3.gif
19484 ms
ga.js
97 ms
m
17789 ms
m_js_controller.js
19 ms
abg.js
17 ms
favicon
170 ms
s
206 ms
googlelogo_color_112x36dp.png
17675 ms
nessie_icon_tiamat_white.png
193 ms
x_button_blue2.png
192 ms
dotline01.gif
19233 ms
like_box.php
17771 ms
gray_table_title_bg.gif
19240 ms
dot_ic01.gif
19340 ms
arrow_ic1.gif
19368 ms
mr_tab_off_bg.gif
19404 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
11 ms
dot_ic02.gif
1911 ms
kGVFUQ4LgBj.css
67 ms
c0qM4_fl0zF.css
79 ms
SRSW8M763HA.js
91 ms
ldIMPsSoKmy.js
110 ms
y97Ig99UVTs.js
89 ms
KHAtULXOQuz.js
90 ms
10968468_323903761150808_5897178578566502125_n.jpg
60 ms
1454591_319995618208289_8810238922223054139_n.jpg
21 ms
10660270_1472020306402521_6783427632598576429_n.jpg
20 ms
11204916_1626160827622145_8573307426245944685_n.jpg
22 ms
10897846_792272244178010_5591600539629450160_n.jpg
25 ms
1508130_460433697396617_676225940_n.jpg
26 ms
1962665_10202213394510961_486983283_n.jpg
23 ms
wL6VQj7Ab77.png
9 ms
1JLnMyDN79z.png
11 ms
VXcANLwwL5J.js
5 ms
i8XO-4kv8i7.js
8 ms
weeklytrade.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
Form elements do not have associated labels
Links do not have a discernible name
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.
weeklytrade.co.kr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
weeklytrade.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
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weeklytrade.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 Weeklytrade.co.kr 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.
weeklytrade.co.kr
Open Graph description is not detected on the main page of Weeklytrade. 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: