Tools & Wizards About Us
obzen.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

obzen.com

Page Load Speed

7.8 sec in total

First Response

711 ms

Resources Loaded

6.9 sec

Page Rendered

235 ms

obzen.com screenshot

About Website

Click here to check amazing Obzen content. Otherwise, check out these important facts you probably never knew about obzen.com

Visit obzen.com

Key Findings

We analyzed Obzen.com page load time and found that the first response time was 711 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

obzen.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value5,310 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

obzen.com

711 ms

00_main.html

949 ms

common.css

445 ms

main.css

460 ms

flip.css

461 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 97% of them (34 requests) were addressed to the original Obzen.com, 3% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Obzen.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 239.2 kB (39%)

Content Size

613.7 kB

After Optimization

374.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Obzen.com main page is 613.7 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 333.6 kB which makes up the majority of the site volume.

HTML Optimization

-33%

Potential reduce by 214 B

  • Original 652 B
  • After minification 625 B
  • After compression 438 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 214 B or 33% of the original size.

Image Optimization

-8%

Potential reduce by 27.4 kB

  • Original 333.6 kB
  • After minification 306.2 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. Obzen images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 96.1 kB

  • Original 141.1 kB
  • After minification 137.4 kB
  • After compression 44.9 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 96.1 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 115.5 kB

  • Original 138.4 kB
  • After minification 133.6 kB
  • After compression 22.9 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. Obzen.com needs all CSS files to be minified and compressed as it can save up to 115.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (21%)

Requests Now

33

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

obzen.com

obzen.com

711 ms

00_main.html

00_main.html

949 ms

common.css

common.css

445 ms

main.css

main.css

460 ms

flip.css

flip.css

461 ms

bootstrap.min.css

bootstrap.min.css

1379 ms

full-slider.css

full-slider.css

485 ms

jquery-1.4.4.min.js

jquery-1.4.4.min.js

7 ms

jquery.smooth-scroll.js

jquery.smooth-scroll.js

906 ms

jquery.js

jquery.js

1632 ms

bootstrap.min.js

bootstrap.min.js

1166 ms

logo.png

logo.png

300 ms

img_01.png

img_01.png

1565 ms

service_cms_off.png

service_cms_off.png

462 ms

service_rebm_off.png

service_rebm_off.png

474 ms

service_dp_off.png

service_dp_off.png

486 ms

service_d3f_off.png

service_d3f_off.png

673 ms

btn_left.png

btn_left.png

701 ms

btn_right.png

btn_right.png

904 ms

kookmin_bank.png

kookmin_bank.png

957 ms

CJ_korea_express.png

CJ_korea_express.png

945 ms

SK_telecom.png

SK_telecom.png

1133 ms

ibk_bank.png

ibk_bank.png

1164 ms

NH_life.png

NH_life.png

1363 ms

shinhan_bank.png

shinhan_bank.png

1400 ms

ING_life.png

ING_life.png

1419 ms

woori_card.png

woori_card.png

1605 ms

hana_group.png

hana_group.png

1637 ms

hana_secutiry.png

hana_secutiry.png

1821 ms

NH_bank.png

NH_bank.png

1876 ms

shinhan_card.png

shinhan_card.png

1891 ms

Eland.png

Eland.png

2022 ms

footer_logo.png

footer_logo.png

2049 ms

NanumGothic.woff

NanumGothic.woff

4201 ms

service_R_bg.png

service_R_bg.png

1983 ms

Accessibility Review

obzen.com accessibility score

98

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.

Best Practices

obzen.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

obzen.com SEO score

81

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Obzen.com 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 Obzen.com main page’s claimed encoding is . 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

obzen.com

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