Tools & Wizards About Us
flashwax.co.kr screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

flashwax.co.kr

flashwax.co.kr

Page Load Speed

6.2 sec in total

First Response

683 ms

Resources Loaded

5.3 sec

Page Rendered

282 ms

flashwax.co.kr screenshot

About Website

Welcome to flashwax.co.kr homepage info - get ready to check Flashwax best content right away, or after learning these important things about flashwax.co.kr

도메인, 도메인등록, 퀵돔등록, 도메인연장, 도메인이전, 무료 파킹, 무료포워딩 제공, 국내 최저가 도메인 서비스 제공, 웹호스팅, 서버호스팅, 홈페이지제작, 쇼핑몰, 서버, IDC

Visit flashwax.co.kr

Key Findings

We analyzed Flashwax.co.kr page load time and found that the first response time was 683 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

flashwax.co.kr performance score

0

Network Requests Diagram

flashwax.co.kr

683 ms

top.html

200 ms

mainm.html

853 ms

product_list.js

213 ms

bookmark.js

393 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 92% of them (95 requests) were addressed to the original Flashwax.co.kr, 3% (3 requests) were made to Web9.logcounter.com and 2% (2 requests) were made to Serial9.logcounter.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Flashwax.co.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 206.5 kB (14%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Flashwax.co.kr main page is 1.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. 35% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-40%

Potential reduce by 248 B

  • Original 615 B
  • After minification 597 B
  • After compression 367 B

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 248 B or 40% of the original size.

Image Optimization

-7%

Potential reduce by 83.0 kB

  • Original 1.3 MB
  • After minification 1.2 MB

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. Flashwax images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 123.2 kB

  • Original 168.9 kB
  • After minification 150.1 kB
  • After compression 45.7 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 123.2 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (19%)

Requests Now

102

After Optimization

83

  • AJAX
  • Images
  • JavaScript

The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flashwax. 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 as a result speed up the page load time.

Network Requests Diagram

flashwax.co.kr

flashwax.co.kr

683 ms

top.html

top.html

200 ms

mainm.html

mainm.html

853 ms

product_list.js

product_list.js

213 ms

bookmark.js

bookmark.js

393 ms

design_func.js

design_func.js

392 ms

flash.js

flash.js

586 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

23 ms

logo3.png

logo3.png

402 ms

6_1.png

6_1.png

389 ms

5_1.png

5_1.png

390 ms

4_1.png

4_1.png

395 ms

3_1.png

3_1.png

400 ms

2_1.png

2_1.png

583 ms

1_1.png

1_1.png

584 ms

menu_01.png

menu_01.png

587 ms

menu_02.png

menu_02.png

589 ms

menu_00.png

menu_00.png

591 ms

menu_04.png

menu_04.png

589 ms

menu_05.png

menu_05.png

771 ms

menu_06.png

menu_06.png

772 ms

menu_07.png

menu_07.png

777 ms

menu_08.png

menu_08.png

780 ms

menu_09.png

menu_09.png

782 ms

menu_10.png

menu_10.png

783 ms

img_01.png

img_01.png

961 ms

img_02.png

img_02.png

963 ms

img_03.png

img_03.png

969 ms

img_04.png

img_04.png

972 ms

img_05.png

img_05.png

973 ms

img_06.png

img_06.png

975 ms

Log_script_logsid.html

Log_script_logsid.html

1147 ms

cookie.js

cookie.js

1151 ms

jquery.js

jquery.js

1542 ms

shoppingtab_template_1.js

shoppingtab_template_1.js

1160 ms

bee_shopping_tab.js

bee_shopping_tab.js

1160 ms

1.png

1.png

2330 ms

2.png

2.png

2113 ms

3.png

3.png

2313 ms

2.png

2.png

1742 ms

3.png

3.png

1383 ms

4.png

4.png

2133 ms

5.PNG

5.PNG

1560 ms

0060010000023.jpg

0060010000023.jpg

1571 ms

22

22

1573 ms

25

25

1758 ms

0040010000013.jpg

0040010000013.jpg

1758 ms

6

6

1929 ms

0050010000153.jpg

0050010000153.jpg

1945 ms

26

26

1767 ms

0140010000103.jpg

0140010000103.jpg

1936 ms

3

3

1940 ms

27

27

1939 ms

0130010000023.jpg

0130010000023.jpg

1949 ms

0130010000033.jpg

0130010000033.jpg

1949 ms

15

15

1770 ms

0040010000043.jpg

0040010000043.jpg

1940 ms

0100010000013.jpg

0100010000013.jpg

1939 ms

6.png

6.png

1939 ms

0020010000033.jpg

0020010000033.jpg

1950 ms

0090010000013.jpg

0090010000013.jpg

1950 ms

5

5

1774 ms

0020010000093.jpg

0020010000093.jpg

1938 ms

0020010000023.jpg

0020010000023.jpg

1940 ms

0010010000113.jpg

0010010000113.jpg

1936 ms

2

2

1951 ms

8

8

1950 ms

[sr].gif

[sr].gif

624 ms

mslog.js

mslog.js

844 ms

0040010000023.jpg

0040010000023.jpg

1774 ms

0050010000113.jpg

0050010000113.jpg

1938 ms

21

21

1934 ms

0050010000013.jpg

0050010000013.jpg

1937 ms

bottombanner0.gif

bottombanner0.gif

1559 ms

bottombanner1_IN.gif

bottombanner1_IN.gif

1553 ms

bottombanner3.gif

bottombanner3.gif

1374 ms

bottombanner13.gif

bottombanner13.gif

1536 ms

Conf_flashwax.js

Conf_flashwax.js

398 ms

bottombanner6.gif

bottombanner6.gif

1347 ms

bottombanner14.gif

bottombanner14.gif

1343 ms

ms.log

ms.log

406 ms

bottombanner2_KOOKMIN.gif

bottombanner2_KOOKMIN.gif

1193 ms

line.png

line.png

1171 ms

footer1.png

footer1.png

1171 ms

[sr].gif

[sr].gif

632 ms

emd_pt.js

emd_pt.js

633 ms

footer2.png

footer2.png

1165 ms

footer3.png

footer3.png

1168 ms

footer4.png

footer4.png

1167 ms

1_01.png

1_01.png

1172 ms

footer01_04_2.png

footer01_04_2.png

1172 ms

footer01_05.png

footer01_05.png

1171 ms

footer01_06.png

footer01_06.png

1166 ms

footer01_07.png

footer01_07.png

1166 ms

footer01_08.png

footer01_08.png

1169 ms

footer01_09.png

footer01_09.png

1171 ms

footer01_10.png

footer01_10.png

1171 ms

btn_mbanner.png

btn_mbanner.png

1172 ms

tab_cart_on_1.gif

tab_cart_on_1.gif

1164 ms

tab_today_off_1.gif

tab_today_off_1.gif

1165 ms

tab_wish_off_1.gif

tab_wish_off_1.gif

1164 ms

btn_fix_ctrl_1.gif

btn_fix_ctrl_1.gif

1168 ms

HTTP_s.js

HTTP_s.js

977 ms

SEO Factors

flashwax.co.kr SEO score

0

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    N/A

  • Encoding

    EUC-KR

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flashwax.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 Flashwax.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.

Social Sharing Optimization

flashwax.co.kr

Open Graph description is not detected on the main page of Flashwax. 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: