Report Summary

  • 65

    Performance

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

neoskin.tistory.com

네오다모아 - 네오다모아

Page Load Speed

10.1 sec in total

First Response

1.4 sec

Resources Loaded

7.9 sec

Page Rendered

719 ms

neoskin.tistory.com screenshot

About Website

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

AI인공지능과 실생활에 유용한 프로그램에 대해 소개하는 블로그입니다.

Visit neoskin.tistory.com

Key Findings

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

neoskin.tistory.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value6.5 s

58/100

10%

Network Requests Diagram

neoskin.tistory.com

1436 ms

style.css

1532 ms

shareEntryWithSNS.css

1307 ms

shareEntryWithSNS.js

1316 ms

lightbox.min.css

1324 ms

Our browser made a total of 184 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Neoskin.tistory.com, 22% (40 requests) were made to S1.daumcdn.net and 10% (18 requests) were made to Um.simpli.fi. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Cfs15.tistory.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (30%)

Content Size

4.0 MB

After Optimization

2.8 MB

In fact, the total size of Neoskin.tistory.com main page is 4.0 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. 60% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 108.3 kB

  • Original 129.2 kB
  • After minification 113.4 kB
  • After compression 20.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. This page needs HTML code to be minified as it can gain 15.9 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 108.3 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 186.1 kB

  • Original 2.8 MB
  • After minification 2.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. Neoskin Tistory images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 349.2 kB

  • Original 528.8 kB
  • After minification 505.9 kB
  • After compression 179.6 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 349.2 kB or 66% of the original size.

CSS Optimization

-91%

Potential reduce by 557.1 kB

  • Original 614.0 kB
  • After minification 585.8 kB
  • After compression 56.8 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. Neoskin.tistory.com needs all CSS files to be minified and compressed as it can save up to 557.1 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 83 (51%)

Requests Now

162

After Optimization

79

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

Accessibility Review

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

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

neoskin.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 Neoskin.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 Neoskin.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 Neoskin Tistory. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: