Access jhr6911.tistory.com. 4차 재난지원금 신청 소상공인 4차 지원금 버팀목 자금 플러스 :: 4차 재난지원금 신청 소상공인 4차 지원금 버팀목 자금 플러스

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value600 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0.212

59/100

15%

TTI (Time to Interactive)

Value15.2 s

7/100

10%

jhr6911.tistory.com

1542 ms

style.css

986 ms

style.css

995 ms

script.js

1032 ms

jquery-3.5.1.min.js

76 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Jhr6911.tistory.com, 67% (84 requests) were made to T1.daumcdn.net and 21% (26 requests) were made to Tistory1.daumcdn.net. The less responsive or slowest element that took the longest time to load (14.6 sec) relates to the external source T1.daumcdn.net.

Content Size

5.7 MB

After Optimization

5.4 MB

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

HTML Optimization

-88%

Potential reduce by 203.9 kB

Original 231.7 kB
After minification 212.7 kB
After compression 27.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 203.9 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 518 B

Original 4.9 MB
After minification 4.9 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. Jhr 6911 Tistory images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 109.1 kB

Original 586.0 kB
After minification 586.0 kB
After compression 476.9 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 109.1 kB or 19% of the original size.

CSS Optimization

-22%

Potential reduce by 8.9 kB

Original 40.9 kB
After minification 40.5 kB
After compression 32.0 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. Jhr6911.tistory.com needs all CSS files to be minified and compressed as it can save up to 8.9 kB or 22% of the original size.

Requests Now

114

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

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

High

Heading elements are not in a sequentially-descending order

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.

High

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

High

Image elements do not have [alt] attributes

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

jhr6911.tistory.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

4차 재난지원금 신청 소상공인 4차 지원금 버팀목 자금 플러스 :: 4차 재난지원금 신청 소상공인 4차 지원금 버팀목 자금 플러스

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

jhr6911.tistory.com

style.css

style.css

script.js

jquery-3.5.1.min.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

jhr6911.tistory.com

style.css

style.css

script.js

jquery-3.5.1.min.js

tiara.min.js

font.css

content.css

uselessPMargin.css

base.js

kakao.min.js

css

style.css

bootstrap.css

yzproj.css

revenue.css

dialog.css

font.css

postBtn.css

comment.css

tistory.css

common.js

comment.js

adsbygoogle.js

search_dragselection.min.js

script.js

shortcut.js

roosevelt_dk_bt.js

index.js

polyfills-legacy.js

index-legacy.js

jquery.min.1.8.3.js

jquery-ui.min.1.10.1.js

jquery.slimscroll.min.js

yzproj.min.js

jquery.masonry.min.js

ygaln.js

kakao.min.js

2416C53E58080FB537

240EAB46580810B41D

257F9246580810B428

247F7246580810B528

260EB346580810B61D