Tools & Wizards About Us
genoss.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

genoss.com

제노스

Page Load Speed

5.4 sec in total

First Response

785 ms

Resources Loaded

3.7 sec

Page Rendered

843 ms

genoss.com screenshot

About Website

Visit genoss.com now to see the best up-to-date Genoss content for South Korea and also check out these interesting facts you probably never knew about genoss.com

좋은 제품이 널리 쓰이게 - 당신의 건강한 삶을 응원하는 글로벌 의료기기 기업

Visit genoss.com

Key Findings

We analyzed Genoss.com page load time and found that the first response time was 785 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

genoss.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value32.9 s

0/100

25%

SI (Speed Index)

Value19.6 s

0/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value4.8 s

78/100

10%

Network Requests Diagram

genoss.com

785 ms

default.css

373 ms

reset.css

380 ms

swiper.min.css

385 ms

common.css

389 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 85% of them (50 requests) were addressed to the original Genoss.com, 7% (4 requests) were made to Fonts.googleapis.com and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Genoss.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.1 MB (35%)

Content Size

11.7 MB

After Optimization

7.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 49.2 kB

  • Original 61.3 kB
  • After minification 46.5 kB
  • After compression 12.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 14.8 kB, which is 24% 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 49.2 kB or 80% of the original size.

Image Optimization

-35%

Potential reduce by 4.0 MB

  • Original 11.5 MB
  • After minification 7.4 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. Obviously, Genoss needs image optimization as it can save up to 4.0 MB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 4.1 kB

  • Original 91.6 kB
  • After minification 91.6 kB
  • After compression 87.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. This website has mostly compressed JavaScripts.

CSS Optimization

-16%

Potential reduce by 4.8 kB

  • Original 29.9 kB
  • After minification 29.8 kB
  • After compression 25.1 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. Genoss.com needs all CSS files to be minified and compressed as it can save up to 4.8 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (49%)

Requests Now

55

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

genoss.com

genoss.com

785 ms

default.css

default.css

373 ms

reset.css

reset.css

380 ms

swiper.min.css

swiper.min.css

385 ms

common.css

common.css

389 ms

main.css

main.css

388 ms

sub.css

sub.css

579 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

749 ms

jquery-migrate-1.4.1.min.js

jquery-migrate-1.4.1.min.js

569 ms

jquery.menu.js

jquery.menu.js

577 ms

common.js

common.js

588 ms

wrest.js

wrest.js

589 ms

placeholders.min.js

placeholders.min.js

764 ms

swiper.min.js

swiper.min.js

798 ms

ScrollTrigger.min.js

ScrollTrigger.min.js

618 ms

common.js

common.js

617 ms

css2

css2

37 ms

css2

css2

58 ms

css2

css2

60 ms

css2

css2

64 ms

pretendardvariable.css

pretendardvariable.css

25 ms

logo.png

logo.png

214 ms

logo_active.png

logo_active.png

214 ms

search_icon.png

search_icon.png

214 ms

mo_menu_icon.png

mo_menu_icon.png

223 ms

search_close.png

search_close.png

222 ms

mv_pause_icon.png

mv_pause_icon.png

384 ms

mv_play_icon.png

mv_play_icon.png

384 ms

mv_arrow_icon.png

mv_arrow_icon.png

386 ms

tit_icon.png

tit_icon.png

386 ms

s1_img_7.png

s1_img_7.png

1353 ms

s1_img_8.png

s1_img_8.png

1168 ms

s1_img_9.png

s1_img_9.png

1320 ms

s1_img_11.png

s1_img_11.png

1513 ms

s1_img_10.png

s1_img_10.png

1540 ms

s1_img_12.png

s1_img_12.png

1155 ms

s2_bg_pc.png

s2_bg_pc.png

1355 ms

s3_img.jpg

s3_img.jpg

1561 ms

s4_icon.png

s4_icon.png

1508 ms

s5_bg_1.png

s5_bg_1.png

1741 ms

s5_play_icon.png

s5_play_icon.png

1548 ms

s5_icon1.png

s5_icon1.png

1697 ms

s6_icon1.png

s6_icon1.png

1701 ms

s6_link_icon.png

s6_link_icon.png

1733 ms

ft_icon_2.png

ft_icon_2.png

1739 ms

sns_blog_b.png

sns_blog_b.png

1754 ms

sns_instagram_b.png

sns_instagram_b.png

1885 ms

sns_smartstore_b.png

sns_smartstore_b.png

1891 ms

cube.png

cube.png

1927 ms

mv_6.jpg

mv_6.jpg

1888 ms

mv_4.png

mv_4.png

2284 ms

mv_7.jpg

mv_7.jpg

2301 ms

s4_bg.png

s4_bg.png

2219 ms

s4_arrow.png

s4_arrow.png

2029 ms

font

font

167 ms

font

font

157 ms

s5_bg_3.jpg

s5_bg_3.jpg

2006 ms

NotoSerifKR.woff

NotoSerifKR.woff

92 ms

font

font

210 ms

Accessibility Review

genoss.com accessibility score

87

Accessibility Issues

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

genoss.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

genoss.com SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Genoss.com 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 Genoss.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

genoss.com

Open Graph data is detected on the main page of Genoss. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: