Tools & Wizards About Us
myo2.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

myo2.net

O2케어 시스템

Page Load Speed

9.6 sec in total

First Response

661 ms

Resources Loaded

8.8 sec

Page Rendered

113 ms

myo2.net screenshot

About Website

Welcome to myo2.net homepage info - get ready to check Myo 2 best content right away, or after learning these important things about myo2.net

생활소형가전 디자인, 기구설계, 금형, 사출, 조립, 포장, 제품개발, PCB개발 개발부터 제품 판매까지 한번에

Visit myo2.net

Key Findings

We analyzed Myo2.net page load time and found that the first response time was 661 ms and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

myo2.net performance score

0

Network Requests Diagram

myo2.net

661 ms

index.php

905 ms

style.css

448 ms

jquery-1.4.2.min.js

1524 ms

common.js

773 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 96% of them (78 requests) were addressed to the original Myo2.net, 2% (2 requests) were made to Kita.net and 1% (1 request) were made to Alluremi.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Myo2.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 82.6 kB (58%)

Content Size

142.3 kB

After Optimization

59.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Myo2.net main page is 142.3 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. Only 10% of websites need less resources to load. Javascripts take 102.2 kB which makes up the majority of the site volume.

HTML Optimization

-24%

Potential reduce by 76 B

  • Original 313 B
  • After minification 306 B
  • After compression 237 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 76 B or 24% of the original size.

Image Optimization

-9%

Potential reduce by 2.7 kB

  • Original 29.7 kB
  • After minification 26.9 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. Myo 2 images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 72.5 kB

  • Original 102.2 kB
  • After minification 90.1 kB
  • After compression 29.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 72.5 kB or 71% of the original size.

CSS Optimization

-72%

Potential reduce by 7.3 kB

  • Original 10.1 kB
  • After minification 8.3 kB
  • After compression 2.8 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. Myo2.net needs all CSS files to be minified and compressed as it can save up to 7.3 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (69%)

Requests Now

80

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

myo2.net

myo2.net

661 ms

index.php

index.php

905 ms

style.css

style.css

448 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

1524 ms

common.js

common.js

773 ms

gnvTop.css

gnvTop.css

790 ms

wrest.js

wrest.js

587 ms

logo_top1.gif

logo_top1.gif

451 ms

korea_1.gif

korea_1.gif

465 ms

english_1.gif

english_1.gif

467 ms

Japan_1.gif

Japan_1.gif

467 ms

chinese_1.gif

chinese_1.gif

466 ms

french_1.gif

french_1.gif

516 ms

spanish_1.gif

spanish_1.gif

892 ms

german_1.gif

german_1.gif

919 ms

mine.gif

mine.gif

922 ms

r_5.gif

r_5.gif

968 ms

r_3.gif

r_3.gif

978 ms

r_1.gif

r_1.gif

1017 ms

login.gif

login.gif

1335 ms

sbox01.gif

sbox01.gif

1371 ms

s-1.gif

s-1.gif

1384 ms

s-2.gif

s-2.gif

1377 ms

s-3.gif

s-3.gif

1484 ms

s-4.gif

s-4.gif

1459 ms

sbox03.gif

sbox03.gif

1776 ms

s-5.gif

s-5.gif

1817 ms

s-20.gif

s-20.gif

1831 ms

s-5-6.gif

s-5-6.gif

1847 ms

s-6.gif

s-6.gif

1881 ms

s-7.gif

s-7.gif

1915 ms

s-8.gif

s-8.gif

2278 ms

s-9.gif

s-9.gif

2270 ms

s-10.gif

s-10.gif

2294 ms

s-11.gif

s-11.gif

2336 ms

s-12.gif

s-12.gif

2323 ms

s-13.gif

s-13.gif

2363 ms

s-14.gif

s-14.gif

2671 ms

s-15.gif

s-15.gif

2723 ms

s-16.gif

s-16.gif

2700 ms

s-18.gif

s-18.gif

2726 ms

logo_top2.gif

logo_top2.gif

2766 ms

n_01.gif

n_01.gif

2875 ms

md.htm

md.htm

918 ms

common.css

common.css

269 ms

n_02.gif

n_02.gif

2670 ms

n_03.gif

n_03.gif

2689 ms

n_04.gif

n_04.gif

2729 ms

n_05.gif

n_05.gif

2715 ms

n_07.gif

n_07.gif

2757 ms

n_06.gif

n_06.gif

2819 ms

main_c1.gif

main_c1.gif

2703 ms

main_d1.gif

main_d1.gif

2679 ms

main_f1.gif

main_f1.gif

2655 ms

md_2.htm

md_2.htm

451 ms

main_e1-1.gif

main_e1-1.gif

2680 ms

main_g1.gif

main_g1.gif

2697 ms

main_h1-1.gif

main_h1-1.gif

2762 ms

notice_t.gif

notice_t.gif

2653 ms

btn_more.gif

btn_more.gif

2672 ms

bull.gif

bull.gif

2675 ms

pg_t.gif

pg_t.gif

2671 ms

style.css

style.css

657 ms

big_main2.gif

big_main2.gif

815 ms

event_n1.gif

event_n1.gif

2611 ms

event_n2.gif

event_n2.gif

2754 ms

event_n3.gif

event_n3.gif

2717 ms

event_n4.gif

event_n4.gif

2681 ms

event_1.gif

event_1.gif

2908 ms

p_title.gif

p_title.gif

2713 ms

m3.gif

m3.gif

2697 ms

m1.gif

m1.gif

2777 ms

m6.gif

m6.gif

2671 ms

copyright.gif

copyright.gif

2678 ms

event_2.gif

event_2.gif

3171 ms

event_3.gif

event_3.gif

2981 ms

top_bg.gif

top_bg.gif

2751 ms

sbox02.gif

sbox02.gif

2762 ms

top_line.gif

top_line.gif

2734 ms

top2_bg.gif

top2_bg.gif

2743 ms

main_bg.jpg

main_bg.jpg

3385 ms

SEO Factors

myo2.net SEO score

0

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Myo2.net 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 Myo2.net main page’s claimed encoding is . 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

myo2.net

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