Tools & Wizards About Us
curiosis.co.kr screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

curiosis.co.kr

Curiosis

Page Load Speed

6.2 sec in total

First Response

862 ms

Resources Loaded

5.2 sec

Page Rendered

180 ms

curiosis.co.kr screenshot

About Website

Visit curiosis.co.kr now to see the best up-to-date Curiosis content and also check out these interesting facts you probably never knew about curiosis.co.kr

Visit curiosis.co.kr

Key Findings

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

Performance Metrics

curiosis.co.kr performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value15.4 s

1/100

10%

TBT (Total Blocking Time)

Value4,790 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.101

89/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

curiosis.co.kr

862 ms

www.curiosis.com

1112 ms

gtm.js

101 ms

axj.css

201 ms

AXButton.css

388 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Curiosis.co.kr, 54% (52 requests) were made to Curiosis.com and 25% (24 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Curiosis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 202.5 kB (11%)

Content Size

1.9 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Curiosis.co.kr main page is 1.9 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 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 58.0 kB

  • Original 69.2 kB
  • After minification 60.9 kB
  • After compression 11.1 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 8.3 kB, which is 12% 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 58.0 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 59.7 kB

  • Original 1.6 MB
  • After minification 1.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. Curiosis images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 57.7 kB

  • Original 109.7 kB
  • After minification 109.7 kB
  • After compression 52.0 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 57.7 kB or 53% of the original size.

CSS Optimization

-37%

Potential reduce by 27.1 kB

  • Original 73.2 kB
  • After minification 73.2 kB
  • After compression 46.2 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. Curiosis.co.kr needs all CSS files to be minified and compressed as it can save up to 27.1 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (56%)

Requests Now

68

After Optimization

30

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

curiosis.co.kr

curiosis.co.kr

862 ms

www.curiosis.com

www.curiosis.com

1112 ms

gtm.js

gtm.js

101 ms

axj.css

axj.css

201 ms

AXButton.css

AXButton.css

388 ms

site.css

site.css

564 ms

shop.css

shop.css

765 ms

jquery-ui.css

jquery-ui.css

27 ms

xeicon.min.css

xeicon.min.css

39 ms

jquery.min.js

jquery.min.js

33 ms

jquery-ui.min.js

jquery-ui.min.js

35 ms

common.js

common.js

737 ms

jquery-ui-timepicker-addon.js

jquery-ui-timepicker-addon.js

949 ms

HuskyEZCreator.js

HuskyEZCreator.js

745 ms

style.css

style.css

738 ms

product.css

product.css

810 ms

jquery-latest.js

jquery-latest.js

37 ms

aos.js

aos.js

925 ms

slick.min.js

slick.min.js

927 ms

common2.js

common2.js

929 ms

jquery.fullpage.js

jquery.fullpage.js

1151 ms

jquery.bxslider-rahisified.js

jquery.bxslider-rahisified.js

1027 ms

js

js

72 ms

js

js

131 ms

main.js

main.js

1124 ms

base.css

base.css

187 ms

common.css

common.css

205 ms

jquery.fullpage.css

jquery.fullpage.css

206 ms

aos.css

aos.css

272 ms

slick.css

slick.css

370 ms

main.css

main.css

378 ms

sub.css

sub.css

409 ms

media.css

media.css

395 ms

css

css

34 ms

nanumsquare.css

nanumsquare.css

49 ms

css2

css2

51 ms

css2

css2

52 ms

css2

css2

52 ms

nanumsquare.css

nanumsquare.css

10 ms

js

js

67 ms

gtm.js

gtm.js

91 ms

js

js

90 ms

biz_icon01.png

biz_icon01.png

271 ms

biz_icon02.png

biz_icon02.png

274 ms

biz_icon03.png

biz_icon03.png

272 ms

biz_icon04.png

biz_icon04.png

272 ms

biz_icon05.png

biz_icon05.png

319 ms

Celloger%20Pro%201%EB%B2%88.png

Celloger%20Pro%201%EB%B2%88.png

950 ms

Celloger%20Stack%201%EB%B2%88.png

Celloger%20Stack%201%EB%B2%88.png

1058 ms

Celloger%20Mini%20Plus%201%EB%B2%88.png

Celloger%20Mini%20Plus%201%EB%B2%88.png

1068 ms

Celloger%20Nano%201%EB%B2%88.png

Celloger%20Nano%201%EB%B2%88.png

1065 ms

MSP%20320%201%EB%B2%88.png

MSP%20320%201%EB%B2%88.png

734 ms

172912_548476542.png

172912_548476542.png

1437 ms

x.gif

x.gif

948 ms

logo.svg

logo.svg

1008 ms

mv_bg.png

mv_bg.png

935 ms

biz_bg.jpg

biz_bg.jpg

1306 ms

icon_more_btn.png

icon_more_btn.png

1090 ms

mod_pro_bg01.png

mod_pro_bg01.png

1082 ms

news_bg.jpg

news_bg.jpg

1147 ms

f_logo.svg

f_logo.svg

1133 ms

f_icon01.png

f_icon01.png

1306 ms

f_icon02.png

f_icon02.png

1307 ms

f_icon03.png

f_icon03.png

1375 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzztgySLng9w.woff

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzztgySLng9w.woff

134 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuoySLng9w.woff

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuoySLng9w.woff

548 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzrQySLng9w.woff

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzrQySLng9w.woff

649 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuozSLng9w.woff

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzuozSLng9w.woff

762 ms

font

font

652 ms

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzkM1SLng9w.woff

PbyxFmXiEBPT4ITbgNA5Cgms3VYcOA-vvnIzzkM1SLng9w.woff

813 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

549 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

549 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff

549 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4k.woff

550 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

551 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

552 ms

xeicon.ttf

xeicon.ttf

84 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpfBK.woff

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpfBK.woff

432 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyovBK.woff

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyovBK.woff

433 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsovBK.woff

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsovBK.woff

434 ms

pxiByp8kv8JHgFVrLDz8V1g.woff

pxiByp8kv8JHgFVrLDz8V1g.woff

434 ms

pxiByp8kv8JHgFVrLFj_V1g.woff

pxiByp8kv8JHgFVrLFj_V1g.woff

522 ms

pxiGyp8kv8JHgFVrLPTedA.woff

pxiGyp8kv8JHgFVrLPTedA.woff

523 ms

pxiEyp8kv8JHgFVrFJM.woff

pxiEyp8kv8JHgFVrFJM.woff

523 ms

pxiByp8kv8JHgFVrLGT9V1g.woff

pxiByp8kv8JHgFVrLGT9V1g.woff

523 ms

pxiByp8kv8JHgFVrLEj6V1g.woff

pxiByp8kv8JHgFVrLEj6V1g.woff

524 ms

pxiByp8kv8JHgFVrLCz7V1g.woff

pxiByp8kv8JHgFVrLCz7V1g.woff

525 ms

pxiByp8kv8JHgFVrLDD4V1g.woff

pxiByp8kv8JHgFVrLDD4V1g.woff

525 ms

pxiByp8kv8JHgFVrLBT5V1g.woff

pxiByp8kv8JHgFVrLBT5V1g.woff

527 ms

support01H.png

support01H.png

899 ms

support02H.png

support02H.png

1002 ms

support03H.png

support03H.png

1030 ms

support04H.png

support04H.png

1031 ms

support05H.png

support05H.png

1069 ms

support06H.png

support06H.png

1125 ms

destination

destination

209 ms

Accessibility Review

curiosis.co.kr accessibility score

91

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

curiosis.co.kr best practices score

67

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

curiosis.co.kr SEO score

90

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    KO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Curiosis.co.kr can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Korean language. Our system also found out that Curiosis.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.

Social Sharing Optimization

curiosis.co.kr

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