7.3 sec in total
1.2 sec
5.9 sec
174 ms
Click here to check amazing Greentransport content. Otherwise, check out these important facts you probably never knew about greentransport.org
움직이는 소나무님 환영합니다!
Visit greentransport.orgWe analyzed Greentransport.org page load time and found that the first response time was 1.2 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
greentransport.org performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value19.1 s
0/100
25%
Value10.5 s
7/100
10%
Value420 ms
66/100
30%
Value0.017
100/100
15%
Value15.0 s
7/100
10%
1168 ms
992 ms
16 ms
206 ms
665 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Greentransport.org, 32% (24 requests) were made to S1.daumcdn.net and 20% (15 requests) were made to Cfs.tistory.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Cfile9.uf.tistory.com.
Page size can be reduced by 905.6 kB (53%)
1.7 MB
790.6 kB
In fact, the total size of Greentransport.org main page is 1.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. 50% of websites need less resources to load. Images take 652.8 kB which makes up the majority of the site volume.
Potential reduce by 71.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 71.8 kB or 84% of the original size.
Potential reduce by 33.0 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. Greentransport images are well optimized though.
Potential reduce by 284.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 284.6 kB or 73% of the original size.
Potential reduce by 516.1 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. Greentransport.org needs all CSS files to be minified and compressed as it can save up to 516.1 kB or 91% of the original size.
Number of requests can be reduced by 42 (57%)
74
32
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greentransport. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
greentransport.org
1168 ms
style.css
992 ms
jquery.js
16 ms
jquery.hoverIntent.minified.js
206 ms
shareEntryWithSNS.css
665 ms
shareEntryWithSNS.js
662 ms
style.css
666 ms
profile.js
897 ms
t_livere_lib.js
673 ms
t_livere.js
675 ms
livere_tistory.js
671 ms
jigu-latest.min.js
1127 ms
T.js
887 ms
EAF2.js
1108 ms
common.js
1385 ms
gallery.js
1113 ms
flash.js
1124 ms
PHON.js
1202 ms
sha256.js
1333 ms
md5.min.js
1336 ms
swfobject.js
1351 ms
dialog.css
1353 ms
reset.css
1674 ms
tabloid.css
2004 ms
items.css
1783 ms
util.css
1577 ms
tistory-grid-min.css
1921 ms
items.js
1694 ms
menubar.css
1804 ms
rainbow.js
1891 ms
641 ms
wcslog.js
7 ms
td.min.js
1458 ms
roosevelt_dk_bt.js
649 ms
check.php
311 ms
new_ico_5.gif
248 ms
26664D3B56C2B0671C5E3C
2927 ms
224B463556A5A3452BD363
2926 ms
25570C4756BC48BB0F03B5
1881 ms
270EB64955B718F5324337
2248 ms
2442C63456EBA94C0864E0
1950 ms
236FE94C56EA49951EC416
1235 ms
276CF44A56E26E14032553
2018 ms
25429E3D56E275D214FB61
1652 ms
2559E834554AF98F1ADB20
1953 ms
2749914B56DE573F165600
1515 ms
banner1.png
667 ms
tab_top.gif
247 ms
tab_closed.gif
249 ms
navi_back_active.gif
246 ms
tab_treed.gif
250 ms
tab_treed_end.gif
248 ms
navi_back_active_end.gif
249 ms
banner2.png
671 ms
banner3.png
672 ms
banner4.png
678 ms
222BC64256E91B1514370A
1749 ms
23251F4956DA6B2B18C1EC
1459 ms
2739E04156DE8EF518175A
1937 ms
brand.png
675 ms
ico-search.png
674 ms
bg-canvas.png
889 ms
ico-pager.png
895 ms
ico-title.png
879 ms
ico-fb.png
862 ms
ico-twt.png
859 ms
ico-rss.png
864 ms
ico-title2.png
1073 ms
ico-title3.png
1085 ms
brand-footer.png
1082 ms
m
485 ms
analytics.js
12 ms
box_d01_logout.png
183 ms
footsteps
1112 ms
collect
12 ms
collect
58 ms
greentransport.org accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
greentransport.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
greentransport.org 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greentransport.org 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 Greentransport.org 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.
greentransport.org
Open Graph data is detected on the main page of Greentransport. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: