10.3 sec in total
1.2 sec
8 sec
1.2 sec
Click here to check amazing DAYGLOW content for South Korea. Otherwise, check out these important facts you probably never knew about dayglow.co.kr
리빙편집샵, 인테리어소품, 러그, 포스터, 키즈, 주방용품 쇼핑몰
Visit dayglow.co.krWe analyzed Dayglow.co.kr page load time and found that the first response time was 1.2 sec and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
dayglow.co.kr performance score
name
value
score
weighting
Value5.3 s
8/100
10%
Value30.0 s
0/100
25%
Value13.6 s
2/100
10%
Value1,280 ms
18/100
30%
Value0.758
6/100
15%
Value26.8 s
0/100
10%
1156 ms
829 ms
7 ms
1223 ms
791 ms
Our browser made a total of 194 requests to load all elements on the main page. We found that 94% of them (182 requests) were addressed to the original Dayglow.co.kr, 2% (4 requests) were made to Web14.logcounter.com and 1% (2 requests) were made to Serial14.logcounter.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Dayglow.co.kr.
Page size can be reduced by 1.3 MB (30%)
4.4 MB
3.0 MB
In fact, the total size of Dayglow.co.kr main page is 4.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. 80% 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. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 121.6 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 45.8 kB, which is 33% 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 121.6 kB or 87% of the original size.
Potential reduce by 917.1 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. Obviously, DAYGLOW needs image optimization as it can save up to 917.1 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 248.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 248.9 kB or 70% of the original size.
Potential reduce by 26.5 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. Dayglow.co.kr needs all CSS files to be minified and compressed as it can save up to 26.5 kB or 81% of the original size.
Number of requests can be reduced by 29 (15%)
193
164
The browser has sent 193 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DAYGLOW. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
dayglow.co.kr
1156 ms
common.css
829 ms
wcslog.js
7 ms
jquery-1.7.2.min.js
1223 ms
flash.js
791 ms
rightbanner.js
593 ms
bookmark.js
397 ms
main.css
395 ms
shopRbanner.html
436 ms
jquery-1.7.min.js
1250 ms
slide.js
592 ms
mainimg.js
610 ms
rolling.js
869 ms
footer.1.css
593 ms
main.js
612 ms
detailpage.js
613 ms
Log_script_logsid.html
647 ms
cookie.js
788 ms
event.1.css
808 ms
img_escrow_mark_org.gif
792 ms
inipay_60x60_gray.png
863 ms
main_08.gif
349 ms
main_07.gif
401 ms
main_06.gif
409 ms
main_05.gif
525 ms
main_04.gif
545 ms
main_03.gif
545 ms
main_11.gif
577 ms
main_22.gif
579 ms
main_23.gif
610 ms
main_24.gif
719 ms
main_25.gif
741 ms
m_16.gif
740 ms
main_17.gif
773 ms
main_16.gif
773 ms
main_15.gif
802 ms
cate_01.gif
917 ms
cate_02.gif
935 ms
cate_03.gif
937 ms
cate_04.gif
971 ms
cate_05.gif
973 ms
cate_06.gif
1000 ms
cate_07.gif
1111 ms
cate_08.gif
1131 ms
cate_09.gif
1132 ms
cate_10.gif
1165 ms
mbtn1.png
1165 ms
mbtn2.png
1195 ms
main1.jpg
1900 ms
main2.jpg
1600 ms
main3.jpg
1581 ms
ban1.jpg
1220 ms
ban2.jpg
1185 ms
ban3.jpg
1190 ms
ban4.jpg
1243 ms
nimg1.jpg
1221 ms
nimg2.jpg
1251 ms
nimg3.jpg
1365 ms
nimg2_1.jpg
1366 ms
nimg2_2.jpg
1389 ms
nimg2_3.jpg
1402 ms
nimg3_1.jpg
1384 ms
nimg3_2.jpg
1418 ms
nimg3_3.jpg
1582 ms
nimg4_1.jpg
1415 ms
nimg4_2.jpg
1470 ms
m
466 ms
[sr].gif
619 ms
mslog.js
596 ms
nimg4_3.jpg
1401 ms
main_63.gif
1384 ms
bbtn_ov.gif
1418 ms
bbtn.gif
1418 ms
btitle1.png
1529 ms
0110060000162.jpg
1516 ms
0050010000052.jpg
1405 ms
0110050000072.jpg
1419 ms
btitle2.png
1417 ms
0120060000022.jpg
1414 ms
0110060000072.jpg
1524 ms
0130030000042.jpg
1514 ms
btitle3.png
1406 ms
0050020000042.jpg
1418 ms
0110050000402.jpg
1418 ms
0110070000012.jpg
1417 ms
choiceban.jpg
1529 ms
0100090000613.jpg
1514 ms
ms.log
405 ms
Conf_dayglow.js
396 ms
0140050000383.jpg
1351 ms
0100090000443.jpg
1380 ms
0100040000323.jpg
1351 ms
0110070000103.jpg
1221 ms
0110050000623.jpg
1331 ms
0110050000643.jpg
1316 ms
[sr].gif
617 ms
emd_pt.js
614 ms
0130010000423.jpg
1193 ms
0100010000873.jpg
1221 ms
0100070000073.jpg
1783 ms
0100010000853.jpg
1220 ms
pro_discount_3.gif
1300 ms
0130040000023.jpg
1204 ms
0110050000073.jpg
1190 ms
0110060000113.jpg
1222 ms
0110050000523.jpg
1221 ms
0100090000573.jpg
1299 ms
0140030000113.jpg
1204 ms
0140050000353.jpg
1192 ms
0110020000153.jpg
1220 ms
0130040000063.jpg
1219 ms
0110050000553.jpg
1328 ms
0100080000153.jpg
1313 ms
0120030000063.jpg
1207 ms
0100080000223.jpg
1222 ms
0110050000473.jpg
1254 ms
HTTP_s.js
811 ms
0100090000353.jpg
1331 ms
0100100000123.jpg
1347 ms
0100050000123.jpg
1321 ms
0130010000163.jpg
1237 ms
0100090000243.jpg
1814 ms
0110060000173.jpg
1255 ms
0050010000283.jpg
1332 ms
0100010000543.jpg
1345 ms
0100040000513.jpg
1321 ms
0100090000463.jpg
1238 ms
0050010000173.jpg
1656 ms
0100030000223.jpg
1365 ms
0100040000443.jpg
1347 ms
0130010000193.jpg
1352 ms
0130010000243.jpg
1342 ms
0120020000653.jpg
1380 ms
0100040000483.jpg
1377 ms
0110050000153.jpg
1384 ms
0050010000273.jpg
1384 ms
0100090000403.jpg
1491 ms
0110050000263.jpg
1398 ms
0110060000063.jpg
1391 ms
0050020000043.jpg
1610 ms
0100010000363.jpg
1380 ms
0110080000283.jpg
1386 ms
0100010000863.jpg
1383 ms
0110020000133.jpg
1380 ms
0110070000093.jpg
1386 ms
0130030000313.jpg
1386 ms
0100010000593.jpg
1386 ms
0100080000133.jpg
1380 ms
0110080000273.jpg
1381 ms
0100060000653.jpg
1387 ms
0130010000413.jpg
1379 ms
0120020000583.jpg
1382 ms
0100100000033.jpg
1387 ms
0140050000323.jpg
1382 ms
0130030000253.jpg
1382 ms
0050020000023.jpg
1385 ms
0120060000103.jpg
1575 ms
0140050000133.jpg
1346 ms
0100030000043.jpg
1277 ms
0130010000363.jpg
1368 ms
0110110000013.jpg
1378 ms
0130010000013.jpg
1358 ms
0100080000083.jpg
1237 ms
0130060000103.jpg
1265 ms
0100030000133.jpg
1359 ms
0120020000193.jpg
1350 ms
0100060000583.jpg
1211 ms
0100010000443.jpg
1414 ms
0100070000033.jpg
1216 ms
0120020000393.jpg
1224 ms
0100020000083.jpg
1323 ms
0100080000063.jpg
1311 ms
index_113.gif
1212 ms
index_112.gif
1224 ms
index_111.gif
1253 ms
index_110.gif
1327 ms
main_105.gif
1310 ms
index_115.gif
1213 ms
index_116.gif
1216 ms
index_117.gif
1212 ms
index_119.gif
1228 ms
main_123.gif
1322 ms
main_127.gif
1308 ms
main_131.gif
1212 ms
main_136.gif
1220 ms
main_137.gif
1212 ms
main_138.gif
1233 ms
dayglow_event4.gif
1324 ms
btn_pop_special_evt_close.gif
1308 ms
index_51.gif
1212 ms
np_btn1.gif
1215 ms
index_63.gif
1210 ms
np_btn2.gif
1224 ms
log_run.php
434 ms
dayglow.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-hidden="true"] elements contain focusable descendents
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
<frame> or <iframe> elements do not have a title
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
dayglow.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
dayglow.co.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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 Dayglow.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 Dayglow.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.
dayglow.co.kr
Open Graph description is not detected on the main page of DAYGLOW. 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: