Tools & Wizards About Us
forgms.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

forgms.com

접속하여 주신 도메인의 기한이 만료되었습니다.

Page Load Speed

28.2 sec in total

First Response

2.7 sec

Resources Loaded

24.6 sec

Page Rendered

918 ms

forgms.com screenshot

About Website

Visit forgms.com now to see the best up-to-date Forgms content and also check out these interesting facts you probably never knew about forgms.com

korea company news is where overseas buyers meet reliable Korean suppliers, manufacturers, products, companies through its business matching news.

Visit forgms.com

Key Findings

We analyzed Forgms.com page load time and found that the first response time was 2.7 sec and then it took 25.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

forgms.com performance score

0

Network Requests Diagram

forgms.com

2727 ms

2014_common.css

800 ms

2014_style.css

2058 ms

2014_main.css

937 ms

b3eec1f.css

2160 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 74% of them (50 requests) were addressed to the original Forgms.com, 7% (5 requests) were made to Pagead2.googlesyndication.com and 7% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Ecltrade.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (15%)

Content Size

7.4 MB

After Optimization

6.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Forgms.com main page is 7.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. 45% of websites need less resources to load. Images take 6.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 87.3 kB

  • Original 105.4 kB
  • After minification 88.6 kB
  • After compression 18.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 16.8 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 87.3 kB or 83% of the original size.

Image Optimization

-5%

Potential reduce by 305.3 kB

  • Original 6.3 MB
  • After minification 6.0 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. Forgms images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 270.9 kB

  • Original 466.8 kB
  • After minification 442.3 kB
  • After compression 195.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 270.9 kB or 58% of the original size.

CSS Optimization

-82%

Potential reduce by 407.1 kB

  • Original 497.1 kB
  • After minification 465.4 kB
  • After compression 90.0 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. Forgms.com needs all CSS files to be minified and compressed as it can save up to 407.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (39%)

Requests Now

62

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forgms.com

forgms.com

2727 ms

2014_common.css

2014_common.css

800 ms

2014_style.css

2014_style.css

2058 ms

2014_main.css

2014_main.css

937 ms

b3eec1f.css

b3eec1f.css

2160 ms

b3eec1f.css

b3eec1f.css

2143 ms

e9cfc62.css

e9cfc62.css

997 ms

common.js

common.js

1168 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

1703 ms

jquery-ui-1.8.16.custom.min.js

jquery-ui-1.8.16.custom.min.js

2620 ms

metadata.js

metadata.js

1411 ms

jquery.example.min.js

jquery.example.min.js

1643 ms

jquery.rolling.js

jquery.rolling.js

1876 ms

rolling_banner.js

rolling_banner.js

1955 ms

jquery.selectbox-0.2.js

jquery.selectbox-0.2.js

2106 ms

adsbygoogle.js

adsbygoogle.js

34 ms

sky1.js

sky1.js

1472 ms

default1.js

default1.js

1555 ms

show_ads.js

show_ads.js

6 ms

sky2.js

sky2.js

1615 ms

default2.js

default2.js

1647 ms

require.min.js

require.min.js

20 ms

ga.js

ga.js

30 ms

WDlb8LTXRznj.jpg

WDlb8LTXRznj.jpg

824 ms

letter.jpg

letter.jpg

20160 ms

201603280309101.jpg

201603280309101.jpg

2149 ms

201603280332481.jpg

201603280332481.jpg

1933 ms

201603280349421.jpg

201603280349421.jpg

1724 ms

201511051133391.jpg

201511051133391.jpg

2152 ms

20140207060630.jpg

20140207060630.jpg

2602 ms

20120904105822.jpg

20120904105822.jpg

3095 ms

white.jpg

white.jpg

253 ms

201603280400401.jpg

201603280400401.jpg

225 ms

201601201137351.jpg

201601201137351.jpg

2399 ms

201511051016561.bmp

201511051016561.bmp

3749 ms

201509170401111.jpg

201509170401111.jpg

940 ms

20140226095223_p_s.jpg

20140226095223_p_s.jpg

934 ms

20131016100115_p_s.jpg

20131016100115_p_s.jpg

597 ms

20140117074917_p_s.jpg

20140117074917_p_s.jpg

981 ms

20140117075005_p_s.jpg

20140117075005_p_s.jpg

2661 ms

20140121114546_p_s.png

20140121114546_p_s.png

4310 ms

20141008024502_p_s.jpg

20141008024502_p_s.jpg

1931 ms

20141007034349_p_s.jpg

20141007034349_p_s.jpg

1965 ms

20140520054338_p_s.5R

20140520054338_p_s.5R

2172 ms

20140519033506_p_s.jpg

20140519033506_p_s.jpg

3961 ms

gms_banner_international.jpg

gms_banner_international.jpg

2669 ms

logo_gms_bottom.gif

logo_gms_bottom.gif

2631 ms

lUIvwrIaqXTX46Sf8a.jpg

lUIvwrIaqXTX46Sf8a.jpg

8348 ms

HDuFAFLLpd3mULAdYTQkPERPLeSiWR.jpg

HDuFAFLLpd3mULAdYTQkPERPLeSiWR.jpg

1369 ms

2014_common.css

2014_common.css

2863 ms

ts_line.gif

ts_line.gif

2861 ms

new_logo.png

new_logo.png

2897 ms

__utm.gif

__utm.gif

27 ms

bg_mmenu2.gif

bg_mmenu2.gif

3009 ms

category_bar.jpg

category_bar.jpg

3041 ms

devide2.gif

devide2.gif

3078 ms

ca-pub-8608296449074091.js

ca-pub-8608296449074091.js

120 ms

zrt_lookup.html

zrt_lookup.html

118 ms

show_ads_impl.js

show_ads_impl.js

52 ms

ads

ads

54 ms

osd.js

osd.js

29 ms

ads

ads

71 ms

ads

ads

40 ms

ads

ads

49 ms

hbAEjbEFAEQAAA==

hbAEjbEFAEQAAA==

2 ms

fontello.svg

fontello.svg

2902 ms

homepage.js

homepage.js

2906 ms

select-icons2.png

select-icons2.png

2874 ms

SEO Factors

forgms.com 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 Forgms.com 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 Forgms.com 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

forgms.com

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