27.1 sec in total
2.5 sec
23.6 sec
1.1 sec
Visit yesarang.tistory.com now to see the best up-to-date Yesarang Tistory content for South Korea and also check out these interesting facts you probably never knew about yesarang.tistory.com
이상계는 이쪽에 속해있지 않고 저쪽에 속해 있다. 이쪽에 사는 우리는 이쪽에 머무르지 않고 저쪽을 꿈꾸며 살아야 한다. 여기 오는 모든이들이 저쪽의 충만함을 이쪽에서의 매일의 삶에 경험할 수 있기를... E-mail: (yesarang) at (yahoo.co.kr)
Visit yesarang.tistory.comWe analyzed Yesarang.tistory.com page load time and found that the first response time was 2.5 sec and then it took 24.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
yesarang.tistory.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value6.5 s
9/100
25%
Value5.5 s
55/100
10%
Value50 ms
100/100
30%
Value0.028
100/100
15%
Value6.1 s
64/100
10%
2480 ms
973 ms
731 ms
749 ms
756 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Yesarang.tistory.com, 38% (33 requests) were made to S1.daumcdn.net and 8% (7 requests) were made to 101.livere.co.kr. The less responsive or slowest element that took the longest time to load (19.5 sec) relates to the external source Static.hanrss.com.
Page size can be reduced by 296.6 kB (68%)
435.7 kB
139.1 kB
In fact, the total size of Yesarang.tistory.com main page is 435.7 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 240.8 kB which makes up the majority of the site volume.
Potential reduce by 44.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 6.6 kB, which is 11% 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 44.9 kB or 75% of the original size.
Potential reduce by 4.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, Yesarang Tistory needs image optimization as it can save up to 4.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 163.8 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 163.8 kB or 68% of the original size.
Potential reduce by 83.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. Yesarang.tistory.com needs all CSS files to be minified and compressed as it can save up to 83.6 kB or 88% of the original size.
Number of requests can be reduced by 60 (71%)
84
24
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yesarang 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.
yesarang.tistory.com
2480 ms
style.css
973 ms
shareEntryWithSNS.css
731 ms
shareEntryWithSNS.js
749 ms
style.css
756 ms
profile.js
757 ms
t_livere_lib.js
2876 ms
t_livere.js
2888 ms
livere_tistory.js
2865 ms
jigu-latest.min.js
1329 ms
T.js
980 ms
EAF2.js
1255 ms
common.js
1612 ms
gallery.js
1055 ms
flash.js
1212 ms
PHON.js
1225 ms
sha256.js
1328 ms
md5.min.js
1455 ms
swfobject.js
1483 ms
dialog.css
1513 ms
menubar.css
2991 ms
plusone.js
200 ms
jquery.min.js
136 ms
show_ads.js
99 ms
cb=gapi.loaded_0
37 ms
friendconnect.js
144 ms
roosevelt_dk_bt.js
113 ms
check.php
434 ms
ccl_black01.png
73 ms
242BB54351DACAEC276009
1815 ms
add_to_hanrss5.gif
19535 ms
count_subscribers.qst
1810 ms
yoonsookim
340 ms
count.php
567 ms
ccl_black02.png
66 ms
ccl_black03.png
63 ms
btn_track_white.gif
63 ms
bg.gif
398 ms
bt_rss.gif
605 ms
bg_wrapper.gif
398 ms
zrt_lookup.html
347 ms
show_ads_impl.js
93 ms
ads
402 ms
osd.js
363 ms
ads
352 ms
socialShare_big2.png
125 ms
smartlogin
947 ms
icon_tag.gif
430 ms
hd_comment.gif
431 ms
hd_trackback.gif
404 ms
blog_icon.gif
429 ms
bg_button.gif
429 ms
116425384F73A3F8352B00
1392 ms
bg_search.gif
437 ms
bg_sidebarH3.gif
675 ms
icon_folder.gif
750 ms
icon_latest.gif
676 ms
icon_comment.gif
751 ms
icon_trackback.gif
750 ms
icon_send.gif
722 ms
icon_rss.gif
855 ms
ifr
465 ms
ga.js
744 ms
m_js_controller.js
456 ms
abg.js
514 ms
like.php
424 ms
Sh_BYjerrZ8.js
732 ms
LVx-xkvaJ0b.png
751 ms
favicon
311 ms
favicon
291 ms
googlelogo_color_112x36dp.png
282 ms
nessie_icon_thin_arrow_big_white.png
128 ms
x_button_blue2.png
129 ms
s
106 ms
td.min.js
842 ms
box_w01_logout.png
74 ms
__utm.gif
66 ms
livereDataLoad
219 ms
Livere_Ready
295 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
29 ms
default.css
1613 ms
rep.php
541 ms
livere_tistory.css
41 ms
footsteps
2214 ms
touch
4618 ms
logo_lr.png
50 ms
icon.gif
45 ms
guest.gif
44 ms
yesarang.tistory.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
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
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
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
yesarang.tistory.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
yesarang.tistory.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
KO
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yesarang.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 Yesarang.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.
yesarang.tistory.com
Open Graph data is detected on the main page of Yesarang Tistory. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: