Tools & Wizards About Us
uhaus.co.kr screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

uhaus.co.kr

여러분의 방문을 환영합니다.

Page Load Speed

3.8 sec in total

First Response

648 ms

Resources Loaded

3 sec

Page Rendered

160 ms

uhaus.co.kr screenshot

About Website

Click here to check amazing Uhaus content. Otherwise, check out these important facts you probably never knew about uhaus.co.kr

gabia,가비아,도메인,domain,도메인등록

Visit uhaus.co.kr

Key Findings

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

Performance Metrics

uhaus.co.kr performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

99/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value0.9 s

100/100

10%

Network Requests Diagram

uhaus.co.kr

648 ms

main_page_01.png

201 ms

main_page_02.png

398 ms

main_page_03.png

399 ms

main_page_04.png

406 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that all of those requests were addressed to Uhaus.co.kr and no external sources were called. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Uhaus.co.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 28.9 kB (3%)

Content Size

918.6 kB

After Optimization

889.7 kB

  • HTML
  • Images

In fact, the total size of Uhaus.co.kr main page is 918.6 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. 20% of websites need less resources to load. Images take 914.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 3.2 kB

  • Original 4.0 kB
  • After minification 3.8 kB
  • After compression 888 B

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 3.2 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 25.7 kB

  • Original 914.5 kB
  • After minification 888.8 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. Uhaus images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

21

After Optimization

21

  • Images

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uhaus. According to our analytics all requests are already optimized.

Network Requests Diagram

uhaus.co.kr

uhaus.co.kr

648 ms

main_page_01.png

main_page_01.png

201 ms

main_page_02.png

main_page_02.png

398 ms

main_page_03.png

main_page_03.png

399 ms

main_page_04.png

main_page_04.png

406 ms

main_page_05.png

main_page_05.png

418 ms

main_page_06.png

main_page_06.png

419 ms

main_page_07.png

main_page_07.png

422 ms

main_page_08.png

main_page_08.png

595 ms

main_page_09.png

main_page_09.png

597 ms

main_page_09_1.png

main_page_09_1.png

608 ms

main_page_10.png

main_page_10.png

624 ms

main_page_11.png

main_page_11.png

627 ms

main_page_12.png

main_page_12.png

2310 ms

main_page_13.png

main_page_13.png

792 ms

main_page_14.png

main_page_14.png

794 ms

main_page_15.png

main_page_15.png

812 ms

main_page_16.png

main_page_16.png

1038 ms

main_page_17.png

main_page_17.png

1043 ms

main_page_18.png

main_page_18.png

990 ms

main_page_19.png

main_page_19.png

992 ms

main_page_20.png

main_page_20.png

1215 ms

spacer.gif

spacer.gif

1188 ms

Accessibility Review

uhaus.co.kr accessibility score

100

Accessibility Issues

Best Practices

uhaus.co.kr best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

uhaus.co.kr SEO score

75

Search Engine Optimization Advices

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

uhaus.co.kr

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