Tools & Wizards About Us
tistory.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

tistory.com

TISTORY

Page Load Speed

10.2 sec in total

First Response

428 ms

Resources Loaded

7.9 sec

Page Rendered

1.9 sec

tistory.com screenshot

About Website

Welcome to tistory.com homepage info - get ready to check TISTORY best content for South Korea right away, or after learning these important things about tistory.com

좀 아는 블로거들의 유용한 이야기, 티스토리. 블로그, 포트폴리오, 웹사이트까지 티스토리에서 나를 표현해 보세요.

Visit tistory.com

Key Findings

We analyzed Tistory.com page load time and found that the first response time was 428 ms and then it took 9.8 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

tistory.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.24

52/100

15%

TTI (Time to Interactive)

Value10.0 s

27/100

10%

Network Requests Diagram

www.tistory.com

428 ms

swiper.min.css

235 ms

font.css

228 ms

gnb.min.css

371 ms

top.css

305 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Tistory.com, 66% (46 requests) were made to T1.daumcdn.net and 26% (18 requests) were made to Img1.daumcdn.net. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Img1.daumcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 612.6 kB (9%)

Content Size

6.5 MB

After Optimization

5.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tistory.com main page is 6.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. 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 6.3 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 25.9 kB

  • Original 32.8 kB
  • After minification 30.5 kB
  • After compression 6.9 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 25.9 kB or 79% of the original size.

Image Optimization

-8%

Potential reduce by 484.6 kB

  • Original 6.3 MB
  • After minification 5.8 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. TISTORY images are well optimized though.

JavaScript Optimization

-33%

Potential reduce by 30.0 kB

  • Original 90.4 kB
  • After minification 90.4 kB
  • After compression 60.4 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 30.0 kB or 33% of the original size.

CSS Optimization

-75%

Potential reduce by 72.1 kB

  • Original 95.7 kB
  • After minification 95.4 kB
  • After compression 23.6 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. Tistory.com needs all CSS files to be minified and compressed as it can save up to 72.1 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (24%)

Requests Now

66

After Optimization

50

  • Images
  • JavaScript
  • CSS

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TISTORY. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.tistory.com

www.tistory.com

428 ms

swiper.min.css

swiper.min.css

235 ms

font.css

font.css

228 ms

gnb.min.css

gnb.min.css

371 ms

top.css

top.css

305 ms

kakao.min.js

kakao.min.js

91 ms

jquery-3.1.0.min.js

jquery-3.1.0.min.js

290 ms

fingerprint2-1.4.2.min.js

fingerprint2-1.4.2.min.js

353 ms

jquery.cookie-1.4.0.min.js

jquery.cookie-1.4.0.min.js

1028 ms

userAgent-1.0.14.min.js

userAgent-1.0.14.min.js

1044 ms

underscore-1.9.0.min.js

underscore-1.9.0.min.js

92 ms

swiper.min.js

swiper.min.js

270 ms

T.js

T.js

154 ms

T.util.js

T.util.js

163 ms

T.auth.js

T.auth.js

232 ms

T.p.top.js

T.p.top.js

244 ms

tiara.min.js

tiara.min.js

230 ms

gnb.min.js

gnb.min.js

231 ms

T.p.top.home.js

T.p.top.home.js

343 ms

img_common_tistory_230106.png

img_common_tistory_230106.png

303 ms

408 ms

img_top_200910.png

img_top_200910.png

277 ms

img_light.png

img_light.png

170 ms

txt_da.png

txt_da.png

187 ms

img_square.png

img_square.png

187 ms

icon_normal.png

icon_normal.png

186 ms

thumb_skin1_1.jpg

thumb_skin1_1.jpg

588 ms

thumb_skin1_2.jpg

thumb_skin1_2.jpg

276 ms

thumb_skin1_3.jpg

thumb_skin1_3.jpg

279 ms

skin_header.jpg

skin_header.jpg

352 ms

thumb_skin2_1.jpg

thumb_skin2_1.jpg

402 ms

thumb_skin2_2.jpg

thumb_skin2_2.jpg

276 ms

thumb_skin2_3.jpg

thumb_skin2_3.jpg

353 ms

photo_skin01.jpg

photo_skin01.jpg

355 ms

photo_skin03.jpg

photo_skin03.jpg

505 ms

photo_skin01_sm.jpg

photo_skin01_sm.jpg

364 ms

photo_skin03_sm.jpg

photo_skin03_sm.jpg

390 ms

photo_skin_txt02.png

photo_skin_txt02.png

421 ms

photo_skin_txt04.png

photo_skin_txt04.png

405 ms

photo_skin02.jpg

photo_skin02.jpg

422 ms

photo_skin04.jpg

photo_skin04.jpg

716 ms

photo_skin_txt01.png

photo_skin_txt01.png

459 ms

photo_skin_txt03.png

photo_skin_txt03.png

490 ms

photo_skin02_sm.jpg

photo_skin02_sm.jpg

663 ms

photo_skin04_sm.jpg

photo_skin04_sm.jpg

639 ms

magazin_01.jpg

magazin_01.jpg

564 ms

magazin_02.jpg

magazin_02.jpg

783 ms

magazine_sm.jpg

magazine_sm.jpg

659 ms

580 ms

587 ms

765 ms

599 ms

589 ms

785 ms

1580 ms

786 ms

1591 ms

791 ms

966 ms

998 ms

984 ms

995 ms

1167 ms

1190 ms

1183 ms

NotoSansCJKkr-DemiLight.woff

NotoSansCJKkr-DemiLight.woff

499 ms

NotoSansCJKkr-Medium.woff

NotoSansCJKkr-Medium.woff

550 ms

NotoSansCJKkr-Light.woff

NotoSansCJKkr-Light.woff

550 ms

sync

sync

1008 ms

track

track

1014 ms

Accessibility Review

tistory.com accessibility score

83

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

tistory.com 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

High

Missing source maps for large first-party JavaScript

SEO Factors

tistory.com SEO score

91

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

    KO

  • Language Claimed

    KO

  • Encoding

    UTF-8

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

tistory.com

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