11.6 sec in total
1.1 sec
10.2 sec
370 ms
Click here to check amazing Homoludentic Tistory content for South Korea. Otherwise, check out these important facts you probably never knew about homoludentic.tistory.com
인간은 무의미한 일에서 생명을 얻고 의미있는 일을 하면서 탈진한다.
Visit homoludentic.tistory.comWe analyzed Homoludentic.tistory.com page load time and found that the first response time was 1.1 sec and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
homoludentic.tistory.com performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value6.4 s
10/100
25%
Value5.8 s
50/100
10%
Value150 ms
95/100
30%
Value0.024
100/100
15%
Value7.7 s
46/100
10%
1062 ms
1452 ms
30 ms
1157 ms
1383 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Homoludentic.tistory.com, 20% (18 requests) were made to S1.daumcdn.net and 9% (8 requests) were made to Ad.about.co.kr. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source S1.daumcdn.net.
Page size can be reduced by 1.1 MB (51%)
2.2 MB
1.1 MB
In fact, the total size of Homoludentic.tistory.com main page is 2.2 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 738.2 kB which makes up the majority of the site volume.
Potential reduce by 69.8 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 10.6 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 69.8 kB or 80% of the original size.
Potential reduce by 77.7 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, Homoludentic Tistory needs image optimization as it can save up to 77.7 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 406.1 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 406.1 kB or 57% of the original size.
Potential reduce by 560.4 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. Homoludentic.tistory.com needs all CSS files to be minified and compressed as it can save up to 560.4 kB or 90% of the original size.
Number of requests can be reduced by 52 (58%)
89
37
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Homoludentic 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.
homoludentic.tistory.com
1062 ms
style.css
1452 ms
jquery.min.js
30 ms
style.css
1157 ms
profile.js
1383 ms
t_livere_lib.js
1874 ms
t_livere.js
1877 ms
livere_tistory.js
1873 ms
jigu-latest.min.js
1619 ms
T.js
1176 ms
EAF2.js
1418 ms
common.js
1657 ms
gallery.js
1378 ms
flash.js
1410 ms
PHON.js
1601 ms
swfobject.js
1604 ms
dialog.css
1643 ms
reset.css
1653 ms
tabloid.css
2309 ms
items.css
2050 ms
util.css
1844 ms
tistory-grid-min.css
2582 ms
items.js
1889 ms
menubar.css
1890 ms
adsbygoogle.js
11 ms
blogrankey_js.asp
1766 ms
td.min.js
1126 ms
roosevelt_dk_bt.js
674 ms
ga.js
47 ms
gpt.js
4 ms
pubads_impl_81.js
6 ms
container.html
28 ms
__utm.gif
25 ms
check.php
275 ms
logo_top.gif
232 ms
216A77355210B1092ABF35
1899 ms
2217474851D3EA172BD65D
1788 ms
2607714051FB553427747A
1708 ms
265E4A4A51D811C2239436
1818 ms
2553543451D2DC9C1C5941
1784 ms
275E8638547993AD027674
1616 ms
210A9D39547992B002CFB2
1937 ms
bnr_newsite.jpg
1712 ms
240E82455479920715C5C2
1592 ms
2114A73D51CCF6C3277BB3
1967 ms
banner_ohfun2.gif
751 ms
logo_bottom.gif
684 ms
btn_search.gif
510 ms
line_top_menu.gif
471 ms
ca-pub-6397630929813918.js
89 ms
zrt_lookup.html
101 ms
show_ads_impl.js
49 ms
bg_conts.gif
442 ms
line_dot.gif
485 ms
count.asp
763 ms
jquery.min.js
98 ms
m_main.css
2295 ms
ads
294 ms
home.png
1989 ms
2320 ms
osd.js
16 ms
ads
288 ms
9419568983273039342
50 ms
abg.js
26 ms
m_js_controller.js
49 ms
googlelogo_color_112x36dp.png
90 ms
12407081288401183656
60 ms
s
32 ms
x_button_blue2.png
34 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
4 ms
1935 ms
stats.gif
249 ms
activeview
13 ms
activeview
16 ms
0266_thumb.gif
238 ms
progress-back.png
460 ms
footsteps
898 ms
banner_200_vs.asp
401 ms
adbn
596 ms
jquery-1.9.1.min.js
35 ms
view
866 ms
adBanner
598 ms
middle_right
608 ms
jquery-1.8.2.min.js
394 ms
jquery.base64.js
413 ms
adbay.controller.v1.10.js
413 ms
base.css
412 ms
slide.css
414 ms
slide.common.js
415 ms
slide.200x200.controller.js
588 ms
middle_right
612 ms
homoludentic.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.
homoludentic.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
homoludentic.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 Homoludentic.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 Homoludentic.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.
homoludentic.tistory.com
Open Graph data is detected on the main page of Homoludentic Tistory. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: