Access boen.co.kr. B o e n

boen.co.kr screenshot

2

Performance

Renders faster than
19% of other websites
47

Accessibility

Visual factors better than
that of 20% of websites
75

Best Practices

More advanced features
available than in
36% of websites
68

SEO

Google-friendlier than
28% of websites

First Response

4.2 sec

Resources Loaded

168.1 sec

Page Rendered

9 sec

boen.co.kr screenshot

About Website

Visit boen.co.kr now to see the best up-to-date B O E N content for Vietnam and also check out these interesting facts you probably never knew about boen.co.kr

B o e n

Visit boen.co.kr

Key Findings

We analyzed Boen.co.kr page load time and found that the first response time was 4.2 sec and then it took 177.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 106 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value23.7 s

0/100

25%

SI (Speed Index)

Value23.4 s

0/100

10%

TBT (Total Blocking Time)

Value3,780 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.633

9/100

15%

TTI (Time to Interactive)

Value23.6 s

1/100

10%

boen.co.kr

4166 ms

lib.js

797 ms

detailpage.js

1087 ms

prototype.js

1519 ms

product_list.js

780 ms

Our browser made a total of 449 requests to load all elements on the main page. We found that 82% of them (367 requests) were addressed to the original Boen.co.kr, 12% (52 requests) were made to Img.boen.co.kr and 1% (4 requests) were made to Web2.logcounter.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Boen.co.kr.

Content Size

24.5 MB

After Optimization

7.6 MB

In fact, the total size of Boen.co.kr main page is 24.5 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. 75% 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 23.5 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 530.3 kB

Original 576.7 kB
After minification 535.0 kB
After compression 46.5 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 530.3 kB or 92% of the original size.

Image Optimization

-69%

Potential reduce by 16.2 MB

Original 23.5 MB
After minification 7.4 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, B O E N needs image optimization as it can save up to 16.2 MB or 69% 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 292.9 kB

Original 428.7 kB
After minification 380.7 kB
After compression 135.8 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 292.9 kB or 68% of the original size.

Requests Now

339

After Optimization

303

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

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

High

Definition list items are not wrapped in <dl> elements

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.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

High

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

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

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

boen.co.kr

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