9.1 sec in total
1.4 sec
6.4 sec
1.3 sec
Click here to check amazing Renn Tistory content for South Korea. Otherwise, check out these important facts you probably never knew about renn.tistory.com
스카이림 모드 한글화 블로그
Visit renn.tistory.comWe analyzed Renn.tistory.com page load time and found that the first response time was 1.4 sec and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
renn.tistory.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value9.3 s
1/100
25%
Value9.8 s
10/100
10%
Value180 ms
92/100
30%
Value0
100/100
15%
Value15.4 s
7/100
10%
1420 ms
1484 ms
1281 ms
1083 ms
1083 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 7% of them (4 requests) were addressed to the original Renn.tistory.com, 63% (35 requests) were made to S1.daumcdn.net and 7% (4 requests) were made to I1.daumcdn.net. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Cfile5.uf.tistory.com.
Page size can be reduced by 463.1 kB (21%)
2.2 MB
1.8 MB
In fact, the total size of Renn.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. 30% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 46.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. 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 46.8 kB or 75% of the original size.
Potential reduce by 23.5 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. Renn Tistory images are well optimized though.
Potential reduce by 297.5 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 297.5 kB or 69% of the original size.
Potential reduce by 95.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. Renn.tistory.com needs all CSS files to be minified and compressed as it can save up to 95.3 kB or 81% of the original size.
Number of requests can be reduced by 34 (62%)
55
21
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Renn 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 7 to 1 for CSS and as a result speed up the page load time.
renn.tistory.com
1420 ms
bootstrap.css
1484 ms
style.css
1281 ms
lightbox.min.css
1083 ms
style.css
1083 ms
profile.js
1387 ms
jigu-latest.min.js
1631 ms
T.js
1282 ms
EAF2.js
1479 ms
common.js
1876 ms
gallery.js
1479 ms
flash.js
1621 ms
PHON.js
1677 ms
sha256.js
1708 ms
md5.min.js
1675 ms
swfobject.js
1855 ms
dialog.css
1862 ms
menubar.css
1881 ms
jquery-1.9.1.min.js
2490 ms
tabmenu-min.js
1909 ms
thumnail-gallery-min.js
1628 ms
thumnail-list-min.js
1637 ms
ygal-min.js
1636 ms
lightbox.min.js
1604 ms
td.min.js
2106 ms
roosevelt_dk_bt.js
431 ms
check.php
278 ms
unknown.gif
882 ms
215FF63556C10B65146546
2954 ms
27608B3556C10B66140F80
3542 ms
2343983556C10B681D5AC9
3130 ms
2467113556C10B6911D642
3244 ms
26305C3556C10B6A2374E1
3405 ms
favicon.ico
109 ms
bg.png
1812 ms
close.png
373 ms
loading.gif
677 ms
prev.png
405 ms
next.png
443 ms
icon-search.png
581 ms
text_track_white.gif
879 ms
2527FD36535F447E353C79
1191 ms
245 ms
icon-admin.png
199 ms
icon-write.png
204 ms
icon-bookmark.png
205 ms
comment-icon.svg
238 ms
ico_profile.png
204 ms
rss
1956 ms
footsteps
1458 ms
jquery-1.11.0.min.js
600 ms
uoclike.min.js
202 ms
uoclike.min-20150408-2.css
10 ms
680726_618.json
700 ms
img_empathy_141113.png
4 ms
680726_618.json
519 ms
renn.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
renn.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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
renn.tistory.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Renn.tistory.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Renn.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.
renn.tistory.com
Open Graph data is detected on the main page of Renn Tistory. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: