Tools & Wizards About Us
ingis.net screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

ingis.net

홈페이지제작회사 ING IS

Page Load Speed

14.8 sec in total

First Response

3.5 sec

Resources Loaded

11.2 sec

Page Rendered

130 ms

ingis.net screenshot

About Website

Click here to check amazing ING IS content. Otherwise, check out these important facts you probably never knew about ingis.net

반응형웹 모바일웹 어플 제작 웹퍼블리싱 홈페이지제작 전문회사 전문업체

Visit ingis.net

Key Findings

We analyzed Ingis.net page load time and found that the first response time was 3.5 sec and then it took 11.3 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

ingis.net performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.065

97/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

ingis.net

3485 ms

jquery.min.js

1618 ms

index.html

1939 ms

index_bg.gif

448 ms

popup_img01.jpg

1344 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 27% of them (12 requests) were addressed to the original Ingis.net, 67% (30 requests) were made to Mhomepage.com and 2% (1 request) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Mhomepage.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 128.3 kB (37%)

Content Size

348.9 kB

After Optimization

220.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ingis.net main page is 348.9 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. 15% of websites need less resources to load. Images take 221.8 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 9.5 kB

  • Original 12.5 kB
  • After minification 12.0 kB
  • After compression 3.1 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. 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 9.5 kB or 75% of the original size.

Image Optimization

-19%

Potential reduce by 43.0 kB

  • Original 221.8 kB
  • After minification 178.7 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, ING IS needs image optimization as it can save up to 43.0 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 69.1 kB

  • Original 106.0 kB
  • After minification 103.0 kB
  • After compression 36.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 69.1 kB or 65% of the original size.

CSS Optimization

-78%

Potential reduce by 6.7 kB

  • Original 8.6 kB
  • After minification 5.9 kB
  • After compression 1.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. Ingis.net needs all CSS files to be minified and compressed as it can save up to 6.7 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (25%)

Requests Now

44

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ingis.net

ingis.net

3485 ms

jquery.min.js

jquery.min.js

1618 ms

index.html

index.html

1939 ms

index_bg.gif

index_bg.gif

448 ms

popup_img01.jpg

popup_img01.jpg

1344 ms

popup_img02.jpg

popup_img02.jpg

1147 ms

popup_img02_2.jpg

popup_img02_2.jpg

920 ms

popup_img03.jpg

popup_img03.jpg

1216 ms

popup_img04.jpg

popup_img04.jpg

1458 ms

memo_sicon.png

memo_sicon.png

894 ms

event_sicon.png

event_sicon.png

1355 ms

mdbt.png

mdbt.png

1401 ms

cbt.png

cbt.png

1597 ms

style.css

style.css

910 ms

maps

maps

34 ms

script.js

script.js

710 ms

location.js

location.js

731 ms

kakao.min.js

kakao.min.js

2526 ms

b12.gif

b12.gif

703 ms

myphoto_img-ingis.png

myphoto_img-ingis.png

3660 ms

logo_img-ingis.png

logo_img-ingis.png

709 ms

intro_bg.png

intro_bg.png

230 ms

m_line.png

m_line.png

456 ms

foot_btn01_new.gif

foot_btn01_new.gif

457 ms

foot_btn02_new.gif

foot_btn02_new.gif

467 ms

foot_btn03_new.gif

foot_btn03_new.gif

683 ms

foot_btn09_new.gif

foot_btn09_new.gif

684 ms

foot_btn04_new.gif

foot_btn04_new.gif

699 ms

foot_btn05_new.gif

foot_btn05_new.gif

912 ms

foot_btn06_new.gif

foot_btn06_new.gif

910 ms

icon_myweb.gif

icon_myweb.gif

931 ms

icon_mypw.gif

icon_mypw.gif

935 ms

icon_mysinsang.gif

icon_mysinsang.gif

943 ms

icon_mysearch.gif

icon_mysearch.gif

1138 ms

icon_myncard.gif

icon_myncard.gif

1139 ms

icon_copy.gif

icon_copy.gif

1164 ms

nextstep.gif

nextstep.gif

1169 ms

cnacelstep.gif

cnacelstep.gif

1179 ms

sendemsbt.gif

sendemsbt.gif

1366 ms

icon_ncard.gif

icon_ncard.gif

1366 ms

icon_email.gif

icon_email.gif

1396 ms

icon_t.gif

icon_t.gif

1403 ms

kakao.jpg

kakao.jpg

1414 ms

foot_bg.gif

foot_bg.gif

1574 ms

chart

chart

23 ms

Accessibility Review

ingis.net accessibility score

72

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

ingis.net best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

ingis.net SEO score

92

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    KO

  • Language Claimed

    KO

  • Encoding

    EUC-KR

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ingis.net can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Ingis.net 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

ingis.net

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