Tools & Wizards About Us
innogs.com screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

innogs.com

innogskorea

Page Load Speed

14.6 sec in total

First Response

3.6 sec

Resources Loaded

10.8 sec

Page Rendered

180 ms

innogs.com screenshot

About Website

Welcome to innogs.com homepage info - get ready to check Innogs best content for South Korea right away, or after learning these important things about innogs.com

A Quasar Framework app

Visit innogs.com

Key Findings

We analyzed Innogs.com page load time and found that the first response time was 3.6 sec and then it took 11 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

innogs.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.049

99/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

Network Requests Diagram

innogs.com

3560 ms

jquery-1.9.1.js

4703 ms

jquery-ui-1.10.3.custom.min.js

5057 ms

common.js

629 ms

jquery.vticker.js

632 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 73% of them (11 requests) were addressed to the original Innogs.com, 20% (3 requests) were made to Fonts.gstatic.com and 7% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Innogs.com.

Page Optimization Overview & Recommendations

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

Content Size

342.2 kB

After Optimization

293.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Innogs.com main page is 342.2 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. 55% of websites need less resources to load. Images take 301.0 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 6.9 kB

  • Original 9.3 kB
  • After minification 8.1 kB
  • After compression 2.5 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 1.2 kB, which is 13% 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 6.9 kB or 73% of the original size.

Image Optimization

-5%

Potential reduce by 15.4 kB

  • Original 301.0 kB
  • After minification 285.6 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. Innogs images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 5.7 kB

  • Original 8.0 kB
  • After minification 5.7 kB
  • After compression 2.3 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 5.7 kB or 71% of the original size.

CSS Optimization

-85%

Potential reduce by 20.4 kB

  • Original 23.9 kB
  • After minification 20.6 kB
  • After compression 3.5 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. Innogs.com needs all CSS files to be minified and compressed as it can save up to 20.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (36%)

Requests Now

11

After Optimization

7

  • Images
  • JavaScript
  • CSS

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Innogs. 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

innogs.com

innogs.com

3560 ms

jquery-1.9.1.js

jquery-1.9.1.js

4703 ms

jquery-ui-1.10.3.custom.min.js

jquery-ui-1.10.3.custom.min.js

5057 ms

common.js

common.js

629 ms

jquery.vticker.js

jquery.vticker.js

632 ms

jquery.ticker.js

jquery.ticker.js

430 ms

layout-en.css

layout-en.css

845 ms

base.css

base.css

218 ms

nanumgothic.css

nanumgothic.css

21 ms

img_innogs.png

img_innogs.png

216 ms

visual_innogs.png

visual_innogs.png

2373 ms

btn_innogs.png

btn_innogs.png

1073 ms

NanumGothic-Bold.woff

NanumGothic-Bold.woff

96 ms

NanumGothic-ExtraBold.woff

NanumGothic-ExtraBold.woff

134 ms

NanumGothic-Regular.woff

NanumGothic-Regular.woff

203 ms

Accessibility Review

innogs.com accessibility score

56

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

innogs.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

innogs.com 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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    EUC-KR

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Innogs.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Innogs.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

innogs.com

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