12.2 sec in total
808 ms
10.5 sec
848 ms
Click here to check amazing Wemb content. Otherwise, check out these important facts you probably never knew about wemb.co.kr
Visit wemb.co.krWe analyzed Wemb.co.kr page load time and found that the first response time was 808 ms and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
wemb.co.kr performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value23.3 s
0/100
25%
Value16.7 s
0/100
10%
Value1,010 ms
27/100
30%
Value0.742
6/100
15%
Value18.7 s
3/100
10%
808 ms
2151 ms
668 ms
3450 ms
466 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 69% of them (81 requests) were addressed to the original Wemb.co.kr, 13% (15 requests) were made to Static.xx.fbcdn.net and 8% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Wemb.co.kr.
Page size can be reduced by 1.8 MB (59%)
3.0 MB
1.2 MB
In fact, the total size of Wemb.co.kr main page is 3.0 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. 85% 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. CSS take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 107.4 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 107.4 kB or 84% of the original size.
Potential reduce by 31.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. Wemb images are well optimized though.
Potential reduce by 534.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 534.7 kB or 72% of the original size.
Potential reduce by 1.1 MB
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. Wemb.co.kr needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 89% of the original size.
Number of requests can be reduced by 44 (43%)
103
59
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wemb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
wemb.co.kr
808 ms
www.wemb.co.kr
2151 ms
language-selector.css
668 ms
js_composer.min.css
3450 ms
styles.css
466 ms
cff-style.css
721 ms
font-awesome.min.css
10 ms
form.min.css
1971 ms
custom.css
696 ms
settings.css
1552 ms
font-awesome.min.css
1621 ms
style.css
2440 ms
wpex-visual-composer.css
1447 ms
wpex-visual-composer-extend.css
1917 ms
wpex-responsive.css
1994 ms
style.css
1851 ms
font-awesome.min.css
2314 ms
style.css
1925 ms
jquery.js
2482 ms
jquery-migrate.min.js
1990 ms
jquery.themepunch.tools.min.js
2627 ms
jquery.themepunch.revolution.min.js
2655 ms
nanumgothic.css
23 ms
notosansjp.css
36 ms
all.js
45 ms
jquery.form.min.js
1383 ms
scripts.js
1514 ms
cff-scripts.js
1614 ms
total-min.js
2710 ms
sitepress.js
1754 ms
js_composer_front.js
2037 ms
top_logo1.png
351 ms
kr_main_slid1.jpg
1387 ms
eng_icoe1.png
349 ms
arrow_down.png
348 ms
arrow_up.png
349 ms
kr_main_slid2.jpg
2941 ms
eng_itservicew.png
718 ms
top_arrow.png
717 ms
bottom_arrow.png
716 ms
kr_main_slid3.jpg
848 ms
eng_building1.png
1055 ms
kr_main_1.jpg
1384 ms
eng_itinrfa11.png
935 ms
kr_main_slid6.jpg
1861 ms
eng_wemb1.png
1244 ms
icon_01.jpg
1444 ms
btn_02.jpg
1580 ms
btn_02_on.jpg
1595 ms
icon_02.jpg
1573 ms
icon_03.jpg
1912 ms
icon_04.jpg
1799 ms
main_coebtn.png
1811 ms
bar.jpg
1841 ms
icon_06.jpg
2026 ms
icon_05.jpg
2272 ms
icon_07.jpg
2064 ms
icon_08.jpg
2087 ms
icon_092.jpg
2146 ms
icon_09_over2.jpg
2252 ms
icon_102.jpg
2303 ms
icon_10_over2.jpg
2333 ms
icon_112.jpg
2379 ms
icon_11_over2.jpg
2479 ms
icon_122.jpg
2732 ms
icon_12_over2.jpg
2541 ms
NanumGothic-Regular.woff
89 ms
NanumGothic-Bold.woff
88 ms
NanumGothic-ExtraBold.woff
89 ms
NotoSansJP-Regular.woff
95 ms
NotoSansJP-Medium.woff
92 ms
NotoSansJP-Light.woff
301 ms
NotoSansJP-Thin.woff
301 ms
NotoSansJP-Bold.woff
302 ms
NotoSansJP-Black.woff
300 ms
fontawesome-webfont.woff
83 ms
84 ms
fontawesome-webfont.woff
2272 ms
fontawesome-webfont.woff
3011 ms
new_main_bg001.jpg
3146 ms
541500_491773950878688_959293464_n.jpg
311 ms
new_main_sns_tit001.jpg
2471 ms
xd_arbiter.php
289 ms
xd_arbiter.php
340 ms
new_main_bg002.jpg
2484 ms
revolution.extension.slideanims.min.js
2520 ms
revolution.extension.actions.min.js
2344 ms
revolution.extension.layeranimation.min.js
2393 ms
page.php
126 ms
revolution.extension.navigation.min.js
2295 ms
4n08FrZmW0I.css
256 ms
X6vRG7qpshl.css
253 ms
q68gy-v_YMF.js
258 ms
k19Xse48j5I.js
287 ms
ihptErjAmMX.js
297 ms
1BQnIVjTFoC.js
302 ms
6PDLJFN-l6_.js
295 ms
cUsKAwzqrQw.js
301 ms
main_news2.jpg
2407 ms
main_culture.jpg
2303 ms
922693_1065203273535750_4742368146195446885_n.png
145 ms
541500_491773950878688_959293464_n.jpg
145 ms
wL6VQj7Ab77.png
133 ms
s7jcwEQH7Sx.png
140 ms
wemb_culture21.jpg
2042 ms
6GqoI2ZyIrf.png
10 ms
footer_logo.png
2111 ms
f_icon.png
2156 ms
R9a_DtVRZgv.js
6 ms
cUDgRFxaoIk.js
5 ms
0JBr1QHp8Gi.js
4 ms
kDOzhTr2W91.js
9 ms
b_icon.png
2113 ms
ko.png
2001 ms
en.png
1989 ms
ja.png
2025 ms
quote.png
1863 ms
wemb.co.kr accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
wemb.co.kr 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
Page has valid source maps
wemb.co.kr SEO score
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
Tap targets are not sized appropriately
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wemb.co.kr 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 Wemb.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.
wemb.co.kr
Open Graph description is not detected on the main page of Wemb. 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: