11.9 sec in total
952 ms
10.8 sec
173 ms
Visit habio.co.kr now to see the best up-to-date Habio content for South Korea and also check out these interesting facts you probably never knew about habio.co.kr
생활편의시설 풍부한 복합공간, 송파 파크하비오 1600-0666
Visit habio.co.krWe analyzed Habio.co.kr page load time and found that the first response time was 952 ms and then it took 10.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
habio.co.kr performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value8.0 s
2/100
25%
Value8.7 s
16/100
10%
Value480 ms
60/100
30%
Value0.622
10/100
15%
Value13.0 s
13/100
10%
952 ms
1247 ms
621 ms
467 ms
466 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 71% of them (49 requests) were addressed to the original Habio.co.kr, 6% (4 requests) were made to F.vimeocdn.com and 4% (3 requests) were made to Gtp6.acecounter.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Habio.co.kr.
Page size can be reduced by 688.9 kB (65%)
1.1 MB
376.3 kB
In fact, the total size of Habio.co.kr main page is 1.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 529.2 kB which makes up the majority of the site volume.
Potential reduce by 10.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 10.3 kB or 68% of the original size.
Potential reduce by 212.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. Obviously, Habio needs image optimization as it can save up to 212.5 kB or 54% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 356.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 356.3 kB or 67% of the original size.
Potential reduce by 109.7 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. Habio.co.kr needs all CSS files to be minified and compressed as it can save up to 109.7 kB or 88% of the original size.
Number of requests can be reduced by 25 (42%)
59
34
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Habio. 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 as a result speed up the page load time.
habio.co.kr
952 ms
index.html
1247 ms
index.css
621 ms
main.js
467 ms
site.js
466 ms
jquery-1.7.2.min.js
4621 ms
jquery-1.4.min.js
470 ms
jquery-ui-1.7.2.custom.min.js
477 ms
jquery.Popup.js
694 ms
nanumgothic.css
25 ms
acecounter_V70.js
476 ms
gtp6.acecounter.com
606 ms
gtp6.acecounter.com
478 ms
photo.jpg
265 ms
popup03_bg.gif
265 ms
popup03.gif
1648 ms
tel.gif
263 ms
btn_project.gif
1033 ms
btn_info.gif
265 ms
btn_kbank.gif
466 ms
btnAddress.gif
477 ms
btn_register.gif
1443 ms
txtAddress.gif
479 ms
txtPolicy.gif
699 ms
txtCopy.gif
2853 ms
t01.png
717 ms
m01.jpg
929 ms
m01.gif
956 ms
t02.png
1162 ms
m02.jpg
1197 ms
m02.gif
1238 ms
t03.png
1393 ms
m03.jpg
1435 ms
m03.gif
1444 ms
t04.png
1625 ms
m04.jpg
1676 ms
m04.gif
1674 ms
t05.png
1649 ms
m05.jpg
1858 ms
m05.gif
1881 ms
movie.gif
1862 ms
happycity.html
1905 ms
mainBg.gif
1908 ms
logo.gif
2082 ms
menu02Off.png
2063 ms
menu03Off.png
2109 ms
menu04Off.png
2134 ms
menu05Off.png
2149 ms
menu06Off.png
2271 ms
NanumGothic-Regular.woff
33 ms
NanumGothic-Bold.woff
52 ms
NanumGothic-ExtraBold.woff
73 ms
analytics.js
7 ms
main_bbs.asp
526 ms
collect
47 ms
80061686
73 ms
gtp6.acecounter.com
405 ms
player.js
99 ms
player.css
81 ms
ga.js
45 ms
vuid.min.js
90 ms
__utm.gif
21 ms
proxy.html
26 ms
mainBg.jpg
2064 ms
visual.jpg
3039 ms
default-red_60x60.png
19 ms
dot.gif
1825 ms
swfobject_modified.js
1738 ms
get_flash_player.gif
11 ms
habio.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
habio.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
General
Impact
Issue
Detected JavaScript libraries
habio.co.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
KO
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Habio.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Habio.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.
habio.co.kr
Open Graph description is not detected on the main page of Habio. 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: