Report Summary

  • 59

    Performance

    Renders faster than
    75% 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

hippochart.tistory.com

히포차트 스토리 :: 히포차트 스토리

Page Load Speed

7.4 sec in total

First Response

1.1 sec

Resources Loaded

6 sec

Page Rendered

322 ms

About Website

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

닷넷 차트 컨트롤 히포차트의 개발 방법과 다양한 사용 예를 알아봅니다. 문의 사항은 hippochart@gmail.com

Visit hippochart.tistory.com

Key Findings

We analyzed Hippochart.tistory.com page load time and found that the first response time was 1.1 sec and then it took 6.3 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

hippochart.tistory.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

hippochart.tistory.com

1102 ms

style.css

1591 ms

shareEntryWithSNS.css

1341 ms

shareEntryWithSNS.js

1344 ms

lightbox.min.css

1349 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Hippochart.tistory.com, 59% (58 requests) were made to S1.daumcdn.net and 11% (11 requests) were made to I1.daumcdn.net. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source S1.daumcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 487.7 kB (53%)

Content Size

925.9 kB

After Optimization

438.2 kB

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

HTML Optimization

-82%

Potential reduce by 82.3 kB

  • Original 99.8 kB
  • After minification 91.7 kB
  • After compression 17.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. 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 82.3 kB or 82% of the original size.

Image Optimization

-10%

Potential reduce by 27.9 kB

  • Original 275.7 kB
  • After minification 247.8 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. Hippochart Tistory images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 319.2 kB

  • Original 479.9 kB
  • After minification 454.6 kB
  • After compression 160.7 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 319.2 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 58.3 kB

  • Original 70.6 kB
  • After minification 62.6 kB
  • After compression 12.3 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. Hippochart.tistory.com needs all CSS files to be minified and compressed as it can save up to 58.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 75 (77%)

Requests Now

97

After Optimization

22

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

Accessibility Review

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

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

hippochart.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 Hippochart.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 Hippochart.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

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