2.7 sec in total
361 ms
2.2 sec
138 ms
Welcome to support.nexon.net homepage info - get ready to check Support Nexon best content for United States right away, or after learning these important things about support.nexon.net
Visit support.nexon.netWe analyzed Support.nexon.net page load time and found that the first response time was 361 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
support.nexon.net performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value6.9 s
6/100
25%
Value4.4 s
74/100
10%
Value1,300 ms
18/100
30%
Value0.064
97/100
15%
Value6.7 s
57/100
10%
361 ms
358 ms
248 ms
155 ms
164 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 19% of them (6 requests) were addressed to the original Support.nexon.net, 38% (12 requests) were made to P8.zdassets.com and 25% (8 requests) were made to P4.zdassets.com. The less responsive or slowest element that took the longest time to load (905 ms) belongs to the original domain Support.nexon.net.
Page size can be reduced by 507.3 kB (69%)
734.0 kB
226.8 kB
In fact, the total size of Support.nexon.net main page is 734.0 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. 40% of websites need less resources to load. Javascripts take 660.3 kB which makes up the majority of the site volume.
Potential reduce by 17.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 17.3 kB or 72% of the original size.
Potential reduce by 0 B
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. Support Nexon images are well optimized though.
Potential reduce by 456.9 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 456.9 kB or 69% of the original size.
Potential reduce by 33.1 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. Support.nexon.net needs all CSS files to be minified and compressed as it can save up to 33.1 kB or 71% of the original size.
Number of requests can be reduced by 7 (28%)
25
18
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Support 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 8 to 1 for JavaScripts and as a result speed up the page load time.
support.nexon.net
361 ms
hc
358 ms
en-us
248 ms
application-1b2d55858cc24c1731c9ebe753c7707b.css
155 ms
style-7c5127890e4b33ba2583c994baa8ef40.css
164 ms
jquery-bdfe7aceb5ca539ae586c3406122925c.js
197 ms
fonts-klavika.css
905 ms
underscore-min.js
683 ms
jquery.cookie.js
671 ms
script-7c5127890e4b33ba2583c994baa8ef40.js
170 ms
locales-a26ad5c1eb40b0bd2446a5ee2a7ea5e60620573f.js
171 ms
host.js
546 ms
vendor_enduser-0325158eb1165785cbd83854980be282.js
225 ms
hc_enduser-7ffe1b02a55be169d47f9233d78dc25a.js
225 ms
nx_header.jpg
287 ms
C050JgkUKP08bkDH2G9EQA-logo.png
136 ms
GITS_game_thumb.jpg
131 ms
icarus_zendesk_thumb.jpg
132 ms
ao_thumb.jpg
207 ms
ca_thumb.jpg
206 ms
db_thumb.jpg
236 ms
dn_thumb.jpg
236 ms
mb_thumb.jpg
242 ms
ms_thumb.jpg
255 ms
vn_thumb.jpg
235 ms
entypo.svg
122 ms
entypo.woff
99 ms
G8r+54APIICrM=
36 ms
dquvRqmrTby8v7PgMKi0AilbAkAZyHi42JjhoolSPlZGX0fTA4P3s50Aw0MZLc7Mz00fjvjJxCGWiX76n0DzliDuAAAA==
35 ms
footer.json
69 ms
nexon_logo_black.png
10 ms
nexon_logo_white.png
25 ms
support.nexon.net accessibility score
support.nexon.net 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
support.nexon.net 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.nexon.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Support.nexon.net 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.
support.nexon.net
Open Graph description is not detected on the main page of Support Nexon. 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: