Tools & Wizards About Us
oddlyenough.kr screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

oddlyenough.kr

Oddly Enough - 신기하고 재미있는 이야기

Page Load Speed

18.6 sec in total

First Response

2.5 sec

Resources Loaded

10.2 sec

Page Rendered

5.9 sec

oddlyenough.kr screenshot

About Website

Welcome to oddlyenough.kr homepage info - get ready to check Oddly Enough best content right away, or after learning these important things about oddlyenough.kr

세상의 신기하고 재미있는 이야기, 문화, 트렌드를 소개합니다.

Visit oddlyenough.kr

Key Findings

We analyzed Oddlyenough.kr page load time and found that the first response time was 2.5 sec and then it took 16.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

oddlyenough.kr performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

57/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

oddlyenough.kr

2519 ms

style.css

1604 ms

style.css

1594 ms

profile.js

1832 ms

jigu-latest.min.js

2074 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Oddlyenough.kr, 71% (40 requests) were made to S1.daumcdn.net and 2% (1 request) were made to Tistory.com. The less responsive or slowest element that took the longest time to load (6.4 sec) relates to the external source Cfile3.uf.tistory.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 575.6 kB (30%)

Content Size

1.9 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oddlyenough.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. 25% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 309.8 kB

  • Original 354.3 kB
  • After minification 309.1 kB
  • After compression 44.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. This page needs HTML code to be minified as it can gain 45.1 kB, which is 13% 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 309.8 kB or 87% of the original size.

Image Optimization

-5%

Potential reduce by 71.5 kB

  • Original 1.3 MB
  • After minification 1.2 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. Oddly Enough images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 151.2 kB

  • Original 209.4 kB
  • After minification 191.2 kB
  • After compression 58.2 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 151.2 kB or 72% of the original size.

CSS Optimization

-82%

Potential reduce by 43.0 kB

  • Original 52.3 kB
  • After minification 43.1 kB
  • After compression 9.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. Oddlyenough.kr needs all CSS files to be minified and compressed as it can save up to 43.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (50%)

Requests Now

54

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oddlyenough.kr

oddlyenough.kr

2519 ms

style.css

style.css

1604 ms

style.css

style.css

1594 ms

profile.js

profile.js

1832 ms

jigu-latest.min.js

jigu-latest.min.js

2074 ms

T.js

T.js

1597 ms

EAF2.js

EAF2.js

1852 ms

common.js

common.js

2348 ms

gallery.js

gallery.js

1837 ms

flash.js

flash.js

2068 ms

PHON.js

PHON.js

2070 ms

sha256.js

sha256.js

2078 ms

md5.min.js

md5.min.js

2096 ms

swfobject.js

swfobject.js

2302 ms

dialog.css

dialog.css

2310 ms

menubar.css

menubar.css

2311 ms

674 ms

td.min.js

td.min.js

1018 ms

roosevelt_dk_bt.js

roosevelt_dk_bt.js

49 ms

reset.css

reset.css

781 ms

text.css

text.css

793 ms

grid.css

grid.css

946 ms

layout.css

layout.css

958 ms

nav.css

nav.css

977 ms

check.php

check.php

331 ms

126C180D4B8770044737B5

126C180D4B8770044737B5

4042 ms

1363430D4B87700851F62A

1363430D4B87700851F62A

3139 ms

205D6F0D4B87700C3F0458

205D6F0D4B87700C3F0458

2617 ms

135E500D4B877010803E43

135E500D4B877010803E43

6441 ms

btn_track_white.gif

btn_track_white.gif

946 ms

index.gif

index.gif

443 ms

index.gif

index.gif

2485 ms

index.gif

index.gif

1413 ms

oddly-enough

oddly-enough

192 ms

somerights20.png

somerights20.png

22 ms

bg.png

bg.png

316 ms

logo.png

logo.png

1061 ms

rss_article.png

rss_article.png

316 ms

twitter-post.gif

twitter-post.gif

317 ms

icon_cc.png

icon_cc.png

316 ms

rss_feed.png

rss_feed.png

313 ms

rss_google.png

rss_google.png

500 ms

rss_han.png

rss_han.png

489 ms

twitter-sidebar.gif

twitter-sidebar.gif

502 ms

icon_mail.png

icon_mail.png

607 ms

bg-header.png

bg-header.png

590 ms

icon_date.png

icon_date.png

716 ms

bg-rp.gif

bg-rp.gif

735 ms

icon_right.png

icon_right.png

748 ms

hr-line.gif

hr-line.gif

819 ms

icon_tags.png

icon_tags.png

832 ms

icon_comment.png

icon_comment.png

998 ms

bg-h21.gif

bg-h21.gif

673 ms

icon_info.png

icon_info.png

699 ms

category1.gif

category1.gif

757 ms

footsteps

footsteps

1642 ms

Accessibility Review

oddlyenough.kr accessibility score

86

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

Document doesn't have a <title> element

High

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

Best Practices

oddlyenough.kr best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

oddlyenough.kr SEO score

75

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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

oddlyenough.kr

Open Graph data is detected on the main page of Oddly Enough. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: