28.2 sec in total
2.1 sec
25.4 sec
790 ms
Click here to check amazing Tos Nexon content for South Korea. Otherwise, check out these important facts you probably never knew about tos.nexon.com
최고급 아이템 획득 기회와 정착 지원 상자 받고 빠르게 100레벨을 달성하세요.
Visit tos.nexon.comWe analyzed Tos.nexon.com page load time and found that the first response time was 2.1 sec and then it took 26.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
tos.nexon.com performance score
name
value
score
weighting
Value18.7 s
0/100
10%
Value41.5 s
0/100
25%
Value27.7 s
0/100
10%
Value170 ms
93/100
30%
Value0.427
22/100
15%
Value34.2 s
0/100
10%
2084 ms
370 ms
454 ms
813 ms
1492 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 13% of them (9 requests) were addressed to the original Tos.nexon.com, 41% (29 requests) were made to S.nx.com and 31% (22 requests) were made to Js.nx.com. The less responsive or slowest element that took the longest time to load (17.2 sec) relates to the external source S.nx.com.
Page size can be reduced by 654.2 kB (14%)
4.8 MB
4.1 MB
In fact, the total size of Tos.nexon.com 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. 35% of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 45.7 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.7 kB or 82% of the original size.
Potential reduce by 30.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. Tos Nexon images are well optimized though.
Potential reduce by 538.1 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 538.1 kB or 73% of the original size.
Potential reduce by 39.7 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. Tos.nexon.com needs all CSS files to be minified and compressed as it can save up to 39.7 kB or 81% of the original size.
Number of requests can be reduced by 35 (51%)
68
33
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tos Nexon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
tos.nexon.com
2084 ms
redirector.aspx
370 ms
index.aspx
454 ms
style.css
813 ms
jquery.min.js
1492 ms
tos.160329.event.js
1753 ms
jquery.fancybox-1.3.4.css
477 ms
jquery.fancybox-1.3.4.js
749 ms
ngb_head.js
813 ms
ps.min.js
1028 ms
aosmgr_common.js
1045 ms
ngb_AOS.js
1071 ms
ngw.ui.min.js
1027 ms
gamewebUtil.js
745 ms
helper.js
469 ms
board.js
468 ms
gnb.min.js
1246 ms
ngb_headstart.js
240 ms
npf_auth_c.js
254 ms
ngb_login.aspx
2014 ms
captchalogin
2017 ms
ngb_pcbanglogin.js
257 ms
ngb_util.js
481 ms
nxmember.js
256 ms
makePCIDCookie.js
259 ms
playlog.min.js
258 ms
GnxVisitorTracking.min.js
258 ms
ngb_RSAHash.js
308 ms
act.nhs
1453 ms
NGMModuleInfo.js
229 ms
npf_ngm.js
234 ms
platform.js
474 ms
util.min.js
227 ms
session.aspx
1922 ms
modernizr-custom.min.js
238 ms
img_item_01.jpg
11766 ms
img_item_03.jpg
11554 ms
img_item_04.jpg
11658 ms
img_item_05.jpg
10226 ms
img_item_06.jpg
11897 ms
img_item_07.jpg
12192 ms
img_item_08.jpg
10737 ms
img_protect_layer_btn0_0114.png
10971 ms
img_protect_layer_btn1_0114.png
11203 ms
img_protect_layer_btn2_0114.png
11462 ms
gnb.css
246 ms
gameinfo.js
268 ms
json2.min.js
266 ms
ico_freecharge.gif
11680 ms
bg_body.gif
11522 ms
set_bt.gif
11630 ms
spr_event_nav_0406.png
11582 ms
spr_sns_share.png
11640 ms
img_section1_0406.jpg
17195 ms
img_leaf1.png
12929 ms
img_leaf2.png
11813 ms
img_leaf3.png
11821 ms
img_leaf4.png
11863 ms
img_leaf5.png
12047 ms
img_leaf6.png
12053 ms
img_leaf7.png
12087 ms
img_leaf8.png
12089 ms
img_leaf9.png
12280 ms
img_leaf10.png
12286 ms
img_section2.jpg
17066 ms
img_protect_layer_0114.jpg
13229 ms
login_layer.css
201 ms
ngb_bodystart.js
204 ms
ngb_bodyend.js
206 ms
dimmed.html
200 ms
tit_layer.gif
235 ms
tos.nexon.com 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
tos.nexon.com 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
Issues were logged in the Issues panel in Chrome Devtools
tos.nexon.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Tos.nexon.com 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 Tos.nexon.com 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.
tos.nexon.com
Open Graph data is detected on the main page of Tos Nexon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: