Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

hohoo.co.kr

호후 - 스마트폰, 테블릿PC 액세서리 멀티샵

Page Load Speed

10.3 sec in total

First Response

1 sec

Resources Loaded

8.2 sec

Page Rendered

1.1 sec

hohoo.co.kr screenshot

About Website

Click here to check amazing Hohoo content for South Korea. Otherwise, check out these important facts you probably never knew about hohoo.co.kr

Visit hohoo.co.kr

Key Findings

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

Performance Metrics

hohoo.co.kr performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.387

27/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

hohoo.co.kr

1007 ms

common.css

787 ms

wcslog.js

7 ms

jquery-1.7.2.min.js

1216 ms

flash.js

814 ms

Our browser made a total of 182 requests to load all elements on the main page. We found that 86% of them (157 requests) were addressed to the original Hohoo.co.kr, 4% (7 requests) were made to Facebook.com and 2% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Hohoo.co.kr.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (20%)

Content Size

6.0 MB

After Optimization

4.8 MB

In fact, the total size of Hohoo.co.kr main page is 6.0 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. Images take 5.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 89.4 kB

  • Original 104.0 kB
  • After minification 80.1 kB
  • After compression 14.7 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 24.0 kB, which is 23% 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 89.4 kB or 86% of the original size.

Image Optimization

-11%

Potential reduce by 550.4 kB

  • Original 5.2 MB
  • After minification 4.6 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, Hohoo needs image optimization as it can save up to 550.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 314.2 kB

  • Original 458.8 kB
  • After minification 432.4 kB
  • After compression 144.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 314.2 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 236.1 kB

  • Original 284.7 kB
  • After minification 275.0 kB
  • After compression 48.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. Hohoo.co.kr needs all CSS files to be minified and compressed as it can save up to 236.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 91 (51%)

Requests Now

179

After Optimization

88

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

Accessibility Review

hohoo.co.kr accessibility score

51

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

hohoo.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

High

Page has valid source maps

SEO Factors

hohoo.co.kr SEO score

75

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

    N/A

  • Encoding

    EUC-KR

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

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