8.4 sec in total
1.4 sec
6.4 sec
530 ms
Visit nextime.co.kr now to see the best up-to-date Nextime content and also check out these interesting facts you probably never knew about nextime.co.kr
Visit nextime.co.krWe analyzed Nextime.co.kr page load time and found that the first response time was 1.4 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
nextime.co.kr performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value23.3 s
0/100
25%
Value8.5 s
17/100
10%
Value390 ms
68/100
30%
Value0.22
56/100
15%
Value9.1 s
33/100
10%
1400 ms
378 ms
384 ms
593 ms
1060 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 93% of them (86 requests) were addressed to the original Nextime.co.kr, 3% (3 requests) were made to Img.echosting.cafe24.com and 2% (2 requests) were made to Img.cafe24.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Nextime.co.kr.
Page size can be reduced by 102.6 kB (3%)
3.4 MB
3.3 MB
In fact, the total size of Nextime.co.kr main page is 3.4 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. 65% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 45.9 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 5.5 kB, which is 11% 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 45.9 kB or 88% of the original size.
Potential reduce by 51.4 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. Nextime images are well optimized though.
Potential reduce by 5.3 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 5.3 kB or 75% of the original size.
Number of requests can be reduced by 22 (24%)
91
69
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nextime. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
nextime.co.kr
1400 ms
common.js
378 ms
cid.generate.js
384 ms
optimizer.php
593 ms
optimizer.php
1060 ms
btn_prd_zoom.gif
635 ms
txt_prog_001.gif
643 ms
img_loading_bar.gif
1055 ms
c46193a0ad90e724e82cf09b7a1d7dcb_7_top.jpg
572 ms
cate_best30_out.png
193 ms
67a580fc7f9133f5e985290879e5be3d.jpg
804 ms
ac1e75c375e7dd6647c32e599958dc13.jpg
769 ms
tit_main_BestSeller.png
386 ms
icon_main_best02.png
390 ms
egreenmall_262.jpg
1577 ms
icon_main_best03.png
583 ms
egreenmall_261.jpg
1142 ms
icon_main_best01.png
775 ms
egreenmall_260.jpg
1535 ms
icon_main_best04.png
968 ms
egreenmall_259.jpg
1567 ms
icon_main_best05.png
1048 ms
egreenmall_258.jpg
2120 ms
tit_main_NewArrival.png
1244 ms
egreenmall_126.jpg
1751 ms
custom_2.gif
1441 ms
egreenmall_116.jpg
1830 ms
egreenmall_55.jpg
1917 ms
egreenmall_50.jpg
2139 ms
egreenmall_257.jpg
1959 ms
egreenmall_228.jpg
2132 ms
egreenmall_244.jpg
2222 ms
egreenmall_223.jpg
2300 ms
egreenmall_256.jpg
2343 ms
egreenmall_251.jpg
2503 ms
egreenmall_250.jpg
2512 ms
egreenmall_240.jpg
2330 ms
egreenmall_233.jpg
2613 ms
egreenmall_222.jpg
2683 ms
egreenmall_171.jpg
2522 ms
egreenmall_167.jpg
2535 ms
icon_rec.gif
623 ms
icon_new_p.gif
626 ms
egreenmall_162.jpg
2886 ms
egreenmall_120.jpg
2516 ms
custom_1.gif
2480 ms
egreenmall_119.jpg
2539 ms
egreenmall_241.jpg
2620 ms
egreenmall_235.jpg
2309 ms
egreenmall_249.jpg
2506 ms
egreenmall_246.jpg
2141 ms
egreenmall_243.jpg
2488 ms
egreenmall_242.jpg
2473 ms
weblog.js
653 ms
async
2202 ms
SubCategory
2185 ms
egreenmall_231.jpg
2093 ms
egreenmall_230.jpg
2112 ms
egreenmall_229.jpg
2105 ms
egreenmall_219.jpg
2081 ms
egreenmall_212.jpg
2084 ms
egreenmall_209.jpg
1761 ms
egreenmall_207.jpg
1888 ms
egreenmall_205.jpg
1786 ms
egreenmall_202.jpg
1787 ms
egreenmall_198.jpg
1716 ms
egreenmall_197.jpg
1707 ms
egreenmall_195.jpg
1905 ms
egreenmall_194.jpg
1671 ms
egreenmall_192.jpg
1610 ms
egreenmall_191.jpg
1607 ms
egreenmall_189.jpg
1881 ms
egreenmall_188.jpg
1529 ms
egreenmall_187.jpg
1572 ms
egreenmall_184.jpg
1579 ms
btn_todayprev.png
1595 ms
btn_todaynext.png
1610 ms
bot_csCenter.png
1552 ms
bot_bankInfo.png
1572 ms
bn_allAt.png
1578 ms
bn_cashReceipts.png
1447 ms
bn_fairTrade.png
1529 ms
bn_inicis.png
1516 ms
bn_ssl.png
1508 ms
bn_hosting.png
1459 ms
top_bg.png
1399 ms
contents_bg.png
1372 ms
cate_out_bg.png
1441 ms
bot_bg.png
1367 ms
ban_01.jpg
1553 ms
m_visual_btn_on.png
1384 ms
m_visual_btn_off.png
1351 ms
nextime.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
Image elements do not have [alt] attributes
Links do not have a discernible name
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
nextime.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
Missing source maps for large first-party JavaScript
nextime.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
KO
KO
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nextime.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 Nextime.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.
nextime.co.kr
Open Graph description is not detected on the main page of Nextime. 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: