Tools & Wizards About Us
tongguitar.co.kr screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 74

    SEO

    Google-friendlier than
    32% of websites

tongguitar.co.kr

기타는 관리다 - 통기타이야기

Page Load Speed

13.4 sec in total

First Response

716 ms

Resources Loaded

11.9 sec

Page Rendered

711 ms

tongguitar.co.kr screenshot

About Website

Click here to check amazing Tongguitar content for South Korea. Otherwise, check out these important facts you probably never knew about tongguitar.co.kr

Visit tongguitar.co.kr

Key Findings

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

Performance Metrics

tongguitar.co.kr performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value15.7 s

0/100

25%

SI (Speed Index)

Value19.6 s

0/100

10%

TBT (Total Blocking Time)

Value560 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.834

4/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

tongguitar.co.kr

716 ms

www.tongguitar.co.kr

1296 ms

jquery-1.8.3.min.js

991 ms

common.js

605 ms

ajax.js

403 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 68% of them (71 requests) were addressed to the original Tongguitar.co.kr, 10% (10 requests) were made to Static.xx.fbcdn.net and 7% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (6.7 sec) belongs to the original domain Tongguitar.co.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 730.1 kB (28%)

Content Size

2.6 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 79.6 kB

  • Original 95.8 kB
  • After minification 80.8 kB
  • After compression 16.2 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 15.0 kB, which is 16% 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 79.6 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 147.9 kB

  • Original 1.9 MB
  • After minification 1.7 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. Tongguitar images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 387.6 kB

  • Original 538.2 kB
  • After minification 495.9 kB
  • After compression 150.5 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 387.6 kB or 72% of the original size.

CSS Optimization

-80%

Potential reduce by 115.0 kB

  • Original 142.9 kB
  • After minification 124.6 kB
  • After compression 27.9 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. Tongguitar.co.kr needs all CSS files to be minified and compressed as it can save up to 115.0 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (53%)

Requests Now

98

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tongguitar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

tongguitar.co.kr

tongguitar.co.kr

716 ms

www.tongguitar.co.kr

www.tongguitar.co.kr

1296 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

991 ms

common.js

common.js

605 ms

ajax.js

ajax.js

403 ms

shop.js

shop.js

415 ms

pison.common.js

pison.common.js

422 ms

pison.css.js

pison.css.js

603 ms

jquery.pisonCore.js

jquery.pisonCore.js

831 ms

jquery.pisonUI.js

jquery.pisonUI.js

1055 ms

jquery.pisonUI.css

jquery.pisonUI.css

680 ms

jquery-ui-1.9.1.custom.min.css

jquery-ui-1.9.1.custom.min.css

1012 ms

jquery-ui-1.9.1.custom.min.js

jquery-ui-1.9.1.custom.min.js

1666 ms

style.css

style.css

910 ms

style_table.css

style_table.css

1037 ms

tip-yellow.css

tip-yellow.css

1137 ms

jquery.poshytip.min.js

jquery.poshytip.min.js

1192 ms

pure-min.css

pure-min.css

1461 ms

grids-responsive-min.css

grids-responsive-min.css

1268 ms

pure-assist.css

pure-assist.css

1267 ms

font-awesome.min.css

font-awesome.min.css

22 ms

style.css

style.css

1379 ms

top_head_menu.inner.css

top_head_menu.inner.css

1172 ms

style.css

style.css

1033 ms

jquery.pisonSlider.min.js

jquery.pisonSlider.min.js

1269 ms

style.css

style.css

1198 ms

wrest.js

wrest.js

1151 ms

wcslog.js

wcslog.js

27 ms

nanumgothic.css

nanumgothic.css

69 ms

floating_banner32.jpg

floating_banner32.jpg

272 ms

floating_banner10.jpg

floating_banner10.jpg

249 ms

v2_logo.png

v2_logo.png

555 ms

acoustix_logo.png

acoustix_logo.png

250 ms

head_newbanner_71.jpg

head_newbanner_71.jpg

552 ms

search_button.png

search_button.png

247 ms

_login.gif

_login.gif

550 ms

register02.png

register02.png

550 ms

findidpw2.png

findidpw2.png

552 ms

icon_new.gif

icon_new.gif

557 ms

article.new.png

article.new.png

679 ms

main_banner_54.jpg

main_banner_54.jpg

1707 ms

main_banner_53.jpg

main_banner_53.jpg

1926 ms

cb0008.png

cb0008.png

1071 ms

cb0006.png

cb0006.png

1085 ms

cb0009.png

cb0009.png

1180 ms

cb0004.png

cb0004.png

1051 ms

bottom_info.png

bottom_info.png

3907 ms

v2_bottom_logo.png

v2_bottom_logo.png

1277 ms

bottom_relation.png

bottom_relation.png

1304 ms

btn_1.gif

btn_1.gif

1328 ms

btn_2.gif

btn_2.gif

1401 ms

btn_3.gif

btn_3.gif

1428 ms

btn_4.gif

btn_4.gif

1566 ms

btn_5.gif

btn_5.gif

1639 ms

btn_6.gif

btn_6.gif

1655 ms

btn_7.gif

btn_7.gif

1796 ms

btn_8.gif

btn_8.gif

1825 ms

btn_9.gif

btn_9.gif

1844 ms

btn_10.gif

btn_10.gif

1866 ms

board_mark.png

board_mark.png

2026 ms

563166035_7993828f_DSC_0423.JPG

563166035_7993828f_DSC_0423.JPG

2346 ms

563166035_5b62ae65_NaverBlog_20160218_204803_00.jpg

563166035_5b62ae65_NaverBlog_20160218_204803_00.jpg

2588 ms

563166035_5bea8f82_grw-c-11.jpg

563166035_5bea8f82_grw-c-11.jpg

2177 ms

2089958934_b1e7b754_DSCF4272.jpg

2089958934_b1e7b754_DSCF4272.jpg

4413 ms

2082243163_3ed06179_B2D9B9CCB1E2_KakaoTalk_20160406_140632250.jpg

2082243163_3ed06179_B2D9B9CCB1E2_KakaoTalk_20160406_140632250.jpg

3080 ms

NanumGothic-Regular.woff

NanumGothic-Regular.woff

233 ms

NanumGothic-Bold.woff

NanumGothic-Bold.woff

383 ms

NanumGothic-ExtraBold.woff

NanumGothic-ExtraBold.woff

503 ms

596078393_e6ae1ea9_C8B8C0FC_20160326_002527.jpg

596078393_e6ae1ea9_C8B8C0FC_20160326_002527.jpg

6722 ms

599181922_ea0713f5_DSC_0853.JPG

599181922_ea0713f5_DSC_0853.JPG

3519 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

57 ms

599181922_201728f9_DSC_9902.JPG

599181922_201728f9_DSC_9902.JPG

3120 ms

all.js

all.js

428 ms

analytics.js

analytics.js

33 ms

m

m

555 ms

599181922_8f9b0bd8_DSC_0640.JPG

599181922_8f9b0bd8_DSC_0640.JPG

4189 ms

collect

collect

102 ms

collect

collect

250 ms

599181922_9393f202_DSC_0629.JPG

599181922_9393f202_DSC_0629.JPG

3420 ms

599181922_ed09e30e_DSC_0609.JPG

599181922_ed09e30e_DSC_0609.JPG

3855 ms

599181922_94884d4a_DSC_0614.JPG

599181922_94884d4a_DSC_0614.JPG

6008 ms

prevArrow.gif

prevArrow.gif

3617 ms

nextArrow.gif

nextArrow.gif

3823 ms

224 ms

xd_arbiter.php

xd_arbiter.php

241 ms

xd_arbiter.php

xd_arbiter.php

451 ms

xd_arbiter.php

xd_arbiter.php

141 ms

like_box.php

like_box.php

178 ms

4zvF1Y0eZKv.css

4zvF1Y0eZKv.css

302 ms

FrSU6IlfEX1.css

FrSU6IlfEX1.css

370 ms

SRSW8M763HA.js

SRSW8M763HA.js

508 ms

ldIMPsSoKmy.js

ldIMPsSoKmy.js

647 ms

y97Ig99UVTs.js

y97Ig99UVTs.js

531 ms

KHAtULXOQuz.js

KHAtULXOQuz.js

532 ms

970174_408545089255993_814290040_n.jpg

970174_408545089255993_814290040_n.jpg

357 ms

377482_132299803547191_799901024_n.jpg

377482_132299803547191_799901024_n.jpg

426 ms

226108_356847004396905_2090166427_n.jpg

226108_356847004396905_2090166427_n.jpg

496 ms

12919722_728779637225778_527501723386795843_n.jpg

12919722_728779637225778_527501723386795843_n.jpg

631 ms

12418040_823297594459605_1204655526753342485_n.jpg

12418040_823297594459605_1204655526753342485_n.jpg

566 ms

1936536_888584457915840_9114275683872410474_n.jpg

1936536_888584457915840_9114275683872410474_n.jpg

563 ms

12552970_10204371259595790_9115666461583444778_n.jpg

12552970_10204371259595790_9115666461583444778_n.jpg

564 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

75 ms

1JLnMyDN79z.png

1JLnMyDN79z.png

74 ms

VXcANLwwL5J.js

VXcANLwwL5J.js

79 ms

i8XO-4kv8i7.js

i8XO-4kv8i7.js

74 ms

Accessibility Review

tongguitar.co.kr accessibility score

55

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tongguitar.co.kr best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

tongguitar.co.kr SEO score

74

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

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 Tongguitar.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 Tongguitar.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

tongguitar.co.kr

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