18.6 sec in total
2.4 sec
15.8 sec
410 ms
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.krWe analyzed Autovis.co.kr page load time and found that the first response time was 2.4 sec and then it took 16.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
autovis.co.kr performance score
name
value
score
weighting
Value9.8 s
0/100
10%
Value16.5 s
0/100
25%
Value17.3 s
0/100
10%
Value300 ms
79/100
30%
Value0.583
11/100
15%
Value16.4 s
5/100
10%
2395 ms
659 ms
441 ms
663 ms
669 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Autovis.co.kr, 3% (2 requests) were made to Gtp15.acecounter.com and 3% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source M.autovis.co.kr.
Page size can be reduced by 1.0 MB (34%)
3.1 MB
2.0 MB
In fact, the total size of Autovis.co.kr main page is 3.1 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. 40% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 40.3 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 40.3 kB or 77% of the original size.
Potential reduce by 64.5 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. Autovis images are well optimized though.
Potential reduce by 805.6 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 805.6 kB or 75% of the original size.
Potential reduce by 138.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. Autovis.co.kr needs all CSS files to be minified and compressed as it can save up to 138.1 kB or 86% of the original size.
Number of requests can be reduced by 36 (60%)
60
24
The browser has sent 60 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 24 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
index
2395 ms
common.css
659 ms
buttons.css
441 ms
jquery-ui-1.8.16.custom.css
663 ms
editor.css
669 ms
jquery.min.js
1132 ms
jquery-ui.min.js
1331 ms
jquery.poshytip.min.js
659 ms
jquery.activity-indicator-1.0.0.min.js
877 ms
jquery.cookie.js
878 ms
jquery.slides.min.js
882 ms
custom-select-box.js
887 ms
editor_loader.js
1096 ms
daum_editor_loader.js
1098 ms
jquery.validate.js
1326 ms
dev-tools.js
1109 ms
design.js
1318 ms
common.js
1317 ms
common-mobile.js
1350 ms
front-layout.js
1360 ms
base64.js
1536 ms
jquery.ui.touch-punch.min.js
1327 ms
jquery.anibanner.js
1338 ms
anibanner.css
1338 ms
wcslog.js
6 ms
editor.js
1124 ms
common-function.js
662 ms
echo.js
227 ms
sdk.js
270 ms
logonew3.png
529 ms
header_gnb_bar.gif
223 ms
btn_header_search_cancel.gif
222 ms
btn_header_search.gif
222 ms
btn_quick_open.png
223 ms
cscenter_btn_more.gif
228 ms
icon_hot.gif
434 ms
11150313list2.jpg
658 ms
201210171511340.gif
442 ms
4.gif
440 ms
13.gif
442 ms
14.gif
454 ms
11150154list2.jpg
652 ms
05103239list2.jpg
902 ms
26111944list2.jpg
1099 ms
201210171520003.gif
660 ms
gtp15.acecounter.com
658 ms
AceCounter_AW.js
832 ms
61 ms
xd_arbiter.php
216 ms
xd_arbiter.php
421 ms
gtp15.acecounter.com
481 ms
sendid
787 ms
m
390 ms
index.php
221 ms
ping
40 ms
images_1.jpg
3733 ms
images_2.jpg
3312 ms
images_3.jpg
2203 ms
images_4.jpg
1975 ms
navi_squ_on.png
223 ms
navi_squ.png
227 ms
444 ms
403.html
440 ms
autovis.co.kr accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
autovis.co.kr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
autovis.co.kr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
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
Document uses legible font sizes
Tap targets are not sized appropriately
KO
KO
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.
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: