12.5 sec in total
584 ms
11.8 sec
139 ms
Welcome to xenics.co.kr homepage info - get ready to check Xenics best content for South Korea right away, or after learning these important things about xenics.co.kr
게이밍의자 키보드 마우스 이어폰 헤드셋 컴퓨터책상 게이밍기어 전문 제닉스크리에이티브
Visit xenics.co.krWe analyzed Xenics.co.kr page load time and found that the first response time was 584 ms and then it took 12 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
xenics.co.kr performance score
name
value
score
weighting
Value11.9 s
0/100
10%
Value17.9 s
0/100
25%
Value32.4 s
0/100
10%
Value480 ms
59/100
30%
Value0.135
80/100
15%
Value20.8 s
2/100
10%
584 ms
852 ms
422 ms
640 ms
477 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 87% of them (60 requests) were addressed to the original Xenics.co.kr, 4% (3 requests) were made to Maxcdn.bootstrapcdn.com and 3% (2 requests) were made to Dgc20.acecounter.com. The less responsive or slowest element that took the longest time to load (6 sec) belongs to the original domain Xenics.co.kr.
Page size can be reduced by 480.1 kB (24%)
2.0 MB
1.5 MB
In fact, the total size of Xenics.co.kr main page is 2.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. 35% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 28.0 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 4.5 kB, which is 13% 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 28.0 kB or 79% of the original size.
Potential reduce by 43.7 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. Xenics images are well optimized though.
Potential reduce by 280.4 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 280.4 kB or 65% of the original size.
Potential reduce by 127.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. Xenics.co.kr needs all CSS files to be minified and compressed as it can save up to 127.9 kB or 82% of the original size.
Number of requests can be reduced by 25 (37%)
67
42
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xenics. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
index.php
584 ms
jquery.min.js
852 ms
bootstrap.min.js
422 ms
common.js
640 ms
godo.cart_tab.js
477 ms
font-awesome.min.css
10 ms
style.css
476 ms
style.css
540 ms
bootstrap.min.css
1152 ms
main.css
947 ms
sns.js
953 ms
wcslog.js
10 ms
naverCommonInflowScript.js
959 ms
jquery.min.js
65 ms
bootstrap.min.js
7 ms
jquery-1.7.2.min.js
1489 ms
cookie.js
1383 ms
main_movie.js
1362 ms
style_horizontal.css
564 ms
acecounter_V70.js
270 ms
dgc20.acecounter.com
632 ms
escrow.jpg
1169 ms
close.gif
415 ms
btn_mypage_go.gif
429 ms
bn00.jpg
432 ms
bn01.jpg
479 ms
bn02.jpg
535 ms
bn03.jpg
1073 ms
refur.jpg
844 ms
logo.gif
914 ms
datmenu_login.gif
947 ms
datmenu_join.gif
962 ms
datmenu_order.gif
1012 ms
datmenu_cart.gif
1378 ms
datmenu_english.gif
1390 ms
maintitle_notice.gif
1429 ms
maintitle_notice_more.gif
1493 ms
blog.jpg
1441 ms
face.jpg
1495 ms
twi.jpg
1853 ms
open.jpg
1871 ms
maintitle01.gif
1915 ms
maintitle02.gif
1959 ms
1454404504291s0.jpg
2205 ms
1445838585157s0.jpg
2450 ms
1439960258439s0.jpg
2584 ms
maincon02.jpg
2384 ms
maincon_arww_left.jpg
2452 ms
maincon_arww_right.jpg
2446 ms
maincon03_img.jpg
3169 ms
maincon02_img.jpg
3599 ms
maincon03.gif
2871 ms
maincon_btn01.gif
2868 ms
maincon_btn02.gif
2937 ms
maincon_btn03.gif
3006 ms
maincon03_bott.gif
3288 ms
sitemap.jpg
3403 ms
dgc20.acecounter.com
496 ms
fontawesome-webfont.woff
10 ms
blank.php
2994 ms
main_promo01.jpg
6019 ms
main_promo02.jpg
5109 ms
main_promo03.jpg
5408 ms
main_promo04.jpg
4814 ms
main_promo05.jpg
4713 ms
point.png
3175 ms
maintitle_notice_back.gif
3692 ms
maincon03_midd.gif
4192 ms
m
706 ms
xenics.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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
xenics.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
xenics.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
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xenics.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 Xenics.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.
xenics.co.kr
Open Graph description is not detected on the main page of Xenics. 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: