Tools & Wizards About Us
liesm.tistory.com screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    81% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

liesm.tistory.com

새로운 시작 :: 새로운 시작

Page Load Speed

5.4 sec in total

First Response

1.4 sec

Resources Loaded

3.6 sec

Page Rendered

433 ms

liesm.tistory.com screenshot

About Website

Visit liesm.tistory.com now to see the best up-to-date Liesm Tistory content for South Korea and also check out these interesting facts you probably never knew about liesm.tistory.com

새로운 시작

Visit liesm.tistory.com

Key Findings

We analyzed Liesm.tistory.com page load time and found that the first response time was 1.4 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster. This domain responded with an error, which can significantly jeopardize Liesm.tistory.com rating and web reputation

Performance Metrics

liesm.tistory.com performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value6.3 s

61/100

10%

Network Requests Diagram

liesm.tistory.com

1390 ms

style.css

609 ms

style.css

406 ms

profile.js

403 ms

jigu-latest.min.js

811 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Liesm.tistory.com, 67% (51 requests) were made to S1.daumcdn.net and 20% (15 requests) were made to I1.daumcdn.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Liesm.tistory.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 295.0 kB (72%)

Content Size

409.3 kB

After Optimization

114.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Liesm.tistory.com main page is 409.3 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. 25% of websites need less resources to load. Javascripts take 213.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 90.9 kB

  • Original 107.1 kB
  • After minification 96.6 kB
  • After compression 16.2 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 90.9 kB or 85% of the original size.

Image Optimization

-13%

Potential reduce by 4.3 kB

  • Original 33.7 kB
  • After minification 29.4 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. Obviously, Liesm Tistory needs image optimization as it can save up to 4.3 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 154.1 kB

  • Original 213.6 kB
  • After minification 194.9 kB
  • After compression 59.5 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 154.1 kB or 72% of the original size.

CSS Optimization

-83%

Potential reduce by 45.7 kB

  • Original 54.9 kB
  • After minification 47.8 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. Liesm.tistory.com needs all CSS files to be minified and compressed as it can save up to 45.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 64 (89%)

Requests Now

72

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Liesm 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

liesm.tistory.com

liesm.tistory.com

1390 ms

style.css

style.css

609 ms

style.css

style.css

406 ms

profile.js

profile.js

403 ms

jigu-latest.min.js

jigu-latest.min.js

811 ms

T.js

T.js

453 ms

EAF2.js

EAF2.js

694 ms

common.js

common.js

1001 ms

gallery.js

gallery.js

607 ms

flash.js

flash.js

680 ms

PHON.js

PHON.js

801 ms

sha256.js

sha256.js

821 ms

md5.min.js

md5.min.js

906 ms

swfobject.js

swfobject.js

923 ms

dialog.css

dialog.css

997 ms

menubar.css

menubar.css

1011 ms

functions.js

functions.js

591 ms

td.min.js

td.min.js

275 ms

roosevelt_dk_bt.js

roosevelt_dk_bt.js

6 ms

check.php

check.php

273 ms

1400858957_%C0%CC%B9%CC%C1%F6_3.png

1400858957_%C0%CC%B9%CC%C1%F6_3.png

414 ms

exe.gif

exe.gif

32 ms

1400858920_%C0%CC%B9%CC%C1%F6_2.png

1400858920_%C0%CC%B9%CC%C1%F6_2.png

460 ms

count.php

count.php

554 ms

ccl_black01.png

ccl_black01.png

32 ms

ccl_black02.png

ccl_black02.png

30 ms

ccl_black03.png

ccl_black03.png

32 ms

btn_track_white.gif

btn_track_white.gif

30 ms

dll.gif

dll.gif

37 ms

unknown.gif

unknown.gif

33 ms

spacer.gif

spacer.gif

32 ms

tab_top.gif

tab_top.gif

33 ms

tab_isleaf.gif

tab_isleaf.gif

32 ms

tab_closed.gif

tab_closed.gif

34 ms

navi_back_active.gif

navi_back_active.gif

34 ms

tab_treed.gif

tab_treed.gif

34 ms

tab_treed_end.gif

tab_treed_end.gif

34 ms

navi_back_active_end.gif

navi_back_active_end.gif

34 ms

bg_top.gif

bg_top.gif

214 ms

menu_div.gif

menu_div.gif

240 ms

searchbar_left.png

searchbar_left.png

244 ms

searchbar_mid.png

searchbar_mid.png

212 ms

txt_search.gif

txt_search.gif

222 ms

btn_search.gif

btn_search.gif

215 ms

txt_total.gif

txt_total.gif

479 ms

txt_today.gif

txt_today.gif

429 ms

txt_yesterday.gif

txt_yesterday.gif

428 ms

searchbar_right.png

searchbar_right.png

427 ms

icon_category.gif

icon_category.gif

468 ms

icon_date.gif

icon_date.gif

480 ms

box_tl.png

box_tl.png

739 ms

box_t.gif

box_t.gif

636 ms

box_tr.png

box_tr.png

639 ms

icon_trackback.gif

icon_trackback.gif

682 ms

icon_comment.gif

icon_comment.gif

667 ms

box_bl.png

box_bl.png

680 ms

box_b.gif

box_b.gif

808 ms

box_br.png

box_br.png

915 ms

ico_prev_no.gif

ico_prev_no.gif

839 ms

ico_next.gif

ico_next.gif

872 ms

rss.gif

rss.gif

915 ms

stitle_category.gif

stitle_category.gif

900 ms

stitle_notice.gif

stitle_notice.gif

972 ms

stitle_tag.gif

stitle_tag.gif

1038 ms

stitle_recentpost.gif

stitle_recentpost.gif

1097 ms

stitle_recentcomment.gif

stitle_recentcomment.gif

1078 ms

stitle_recenttrackback.gif

stitle_recenttrackback.gif

1098 ms

stitle_archive.gif

stitle_archive.gif

1148 ms

btn_prevmonth.gif

btn_prevmonth.gif

1187 ms

btn_nextmonth.gif

btn_nextmonth.gif

1254 ms

stitle_mylink.gif

stitle_mylink.gif

1285 ms

tistory.png

tistory.png

1328 ms

footsteps

footsteps

1178 ms

ppomppu_403.jpg

ppomppu_403.jpg

772 ms

ppomppu_403.jpg

ppomppu_403.jpg

757 ms

print.css

print.css

212 ms

Accessibility Review

liesm.tistory.com accessibility score

65

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.

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

Image elements do not have [alt] attributes

Tables and lists

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

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

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

Low

Detected JavaScript libraries

SEO Factors

liesm.tistory.com SEO score

86

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

Image elements do not have [alt] attributes

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

    KO

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

liesm.tistory.com

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