Tools & Wizards About Us
autovis.co.kr screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

autovis.co.kr

오토비스

Page Load Speed

7.9 sec in total

First Response

1.3 sec

Resources Loaded

6.2 sec

Page Rendered

420 ms

autovis.co.kr screenshot

About Website

Welcome to autovis.co.kr homepage info - get ready to check Autovis best content right away, or after learning these important things about autovis.co.kr

오토비스

Visit autovis.co.kr

Key Findings

We analyzed Autovis.co.kr page load time and found that the first response time was 1.3 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

autovis.co.kr performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value1.354

0/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

autovis.co.kr

1289 ms

css

31 ms

css

49 ms

jquery-ui-1.8.16.custom.css

430 ms

slick.css

577 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 87% of them (90 requests) were addressed to the original Autovis.co.kr, 10% (10 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Autovis.co.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 181.8 kB (7%)

Content Size

2.6 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Autovis.co.kr main page is 2.6 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. 70% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 68.0 kB

  • Original 81.3 kB
  • After minification 65.1 kB
  • After compression 13.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.2 kB, which is 20% 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 68.0 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 33.6 kB

  • Original 2.1 MB
  • After minification 2.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. Autovis images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 62.3 kB

  • Original 324.6 kB
  • After minification 310.4 kB
  • After compression 262.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 62.3 kB or 19% of the original size.

CSS Optimization

-18%

Potential reduce by 17.8 kB

  • Original 100.4 kB
  • After minification 97.7 kB
  • After compression 82.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. Autovis.co.kr needs all CSS files to be minified and compressed as it can save up to 17.8 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (52%)

Requests Now

93

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

autovis.co.kr

autovis.co.kr

1289 ms

css

css

31 ms

css

css

49 ms

jquery-ui-1.8.16.custom.css

jquery-ui-1.8.16.custom.css

430 ms

slick.css

slick.css

577 ms

goods_info_style.css

goods_info_style.css

578 ms

goods_info_user.css

goods_info_user.css

588 ms

lib.css

lib.css

631 ms

common.css

common.css

893 ms

board.css

board.css

650 ms

buttons.css

buttons.css

770 ms

mobile_pagination.css

mobile_pagination.css

771 ms

broadcast.css

broadcast.css

840 ms

user.css

user.css

866 ms

swiper.css

swiper.css

964 ms

jquery_swipe.css

jquery_swipe.css

962 ms

jquery.min.js

jquery.min.js

1229 ms

jquery-ui.min.js

jquery-ui.min.js

1278 ms

jquery.poshytip.min.js

jquery.poshytip.min.js

1082 ms

jquery.activity-indicator-1.0.0.min.js

jquery.activity-indicator-1.0.0.min.js

1108 ms

jquery.cookie.js

jquery.cookie.js

1156 ms

jquery.slides.min.js

jquery.slides.min.js

1155 ms

jquery.placeholder.js

jquery.placeholder.js

1298 ms

jquery.validate.js

jquery.validate.js

1329 ms

jquery.ezmark.min.js

jquery.ezmark.min.js

1348 ms

custom-select-box.js

custom-select-box.js

1348 ms

custom-mobile-pagination.js

custom-mobile-pagination.js

1425 ms

slick.min.js

slick.min.js

1490 ms

jquery.event.swipe.js

jquery.event.swipe.js

1515 ms

swiper.js

swiper.js

1570 ms

dev-tools.js

dev-tools.js

1540 ms

goods-display_mobile.js

goods-display_mobile.js

1740 ms

design.js

design.js

1623 ms

common.js

common.js

1703 ms

common-mobile.js

common-mobile.js

1731 ms

front-layout.js

front-layout.js

1928 ms

base64.js

base64.js

1786 ms

js

js

52 ms

skin-responsive.js

skin-responsive.js

1617 ms

L10n_KR.js

L10n_KR.js

1501 ms

jquery.event.drag-1.5.min.js

jquery.event.drag-1.5.min.js

1377 ms

jquery.touchSlider.js

jquery.touchSlider.js

1363 ms

responsive.js

responsive.js

1422 ms

script.js

script.js

1393 ms

search_ver2.js

search_ver2.js

1492 ms

user.js

user.js

1355 ms

jquery.bxslider.js

jquery.bxslider.js

1367 ms

search_ver2_ready.js

search_ver2_ready.js

1340 ms

css

css

18 ms

L10n_KR.js

L10n_KR.js

492 ms

common-function.js

common-function.js

487 ms

popup_17134356899287.png

popup_17134356899287.png

236 ms

btn_tbanner_close.png

btn_tbanner_close.png

242 ms

band_btn_open.png

band_btn_open.png

235 ms

band_btn_open.gif

band_btn_open.gif

235 ms

icon_cart.png

icon_cart.png

234 ms

icon_mypage.png

icon_mypage.png

234 ms

logo.png

logo.png

450 ms

icon_search.png

icon_search.png

429 ms

btn_zoom.png

btn_zoom.png

426 ms

icon_close_gray2.png

icon_close_gray2.png

425 ms

icon_cart.png

icon_cart.png

442 ms

popup_17174645449538.jpg

popup_17174645449538.jpg

662 ms

images_1.jpg

images_1.jpg

810 ms

images_2.png

images_2.png

1003 ms

images_1.jpg

images_1.jpg

821 ms

images_2.jpg

images_2.jpg

859 ms

images_1.png

images_1.png

1102 ms

images_2.png

images_2.png

1740 ms

222_temp_17134171724082view.jpg

222_temp_17134171724082view.jpg

1003 ms

icon_zzim.png

icon_zzim.png

1018 ms

icon_zzim_on.png

icon_zzim_on.png

1070 ms

5.gif

5.gif

1197 ms

10.gif

10.gif

1196 ms

13.gif

13.gif

1214 ms

221_temp_17134185243458view.jpg

221_temp_17134185243458view.jpg

1279 ms

97_temp_17134112408231view.jpg

97_temp_17134112408231view.jpg

1318 ms

96_temp_17134113599338view.jpg

96_temp_17134113599338view.jpg

1579 ms

84_temp_17134098087180view.jpg

84_temp_17134098087180view.jpg

1389 ms

173_temp_17134251476502view.jpg

173_temp_17134251476502view.jpg

1606 ms

172_temp_17134251075111view.jpg

172_temp_17134251075111view.jpg

1490 ms

icon_facebook.png

icon_facebook.png

1535 ms

icon_twitter.png

icon_twitter.png

1582 ms

icon_instagram.png

icon_instagram.png

1700 ms

icon_blog.png

icon_blog.png

1751 ms

icon_kakao.png

icon_kakao.png

1771 ms

icon_youtube.png

icon_youtube.png

1741 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

42 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

42 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

195 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

233 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

203 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzrQySLng9A.ttf

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzrQySLng9A.ttf

234 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuozSLng9A.ttf

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuozSLng9A.ttf

307 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuoySLng9A.ttf

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuoySLng9A.ttf

235 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzztgySLng9A.ttf

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzztgySLng9A.ttf

234 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzg01SLng9A.ttf

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzg01SLng9A.ttf

236 ms

search_recent_auto

search_recent_auto

1613 ms

use_auto_complete

use_auto_complete

1720 ms

img_paying.gif

img_paying.gif

1724 ms

progress_bar.gif

progress_bar.gif

1736 ms

bul_layer_custom.png

bul_layer_custom.png

1726 ms

arrow_right.gif

arrow_right.gif

1730 ms

arrow_left.gif

arrow_left.gif

1618 ms

Accessibility Review

autovis.co.kr accessibility score

79

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

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

autovis.co.kr 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

SEO Factors

autovis.co.kr SEO score

80

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

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Autovis.co.kr 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 Autovis.co.kr 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

autovis.co.kr

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