12.3 sec in total
3.8 sec
8.3 sec
201 ms
Visit hanilbus.com now to see the best up-to-date Hanilbus content for South Korea and also check out these interesting facts you probably never knew about hanilbus.com
Visit hanilbus.comWe analyzed Hanilbus.com page load time and found that the first response time was 3.8 sec and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
hanilbus.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value20.0 s
0/100
25%
Value14.4 s
1/100
10%
Value14,370 ms
0/100
30%
Value0.005
100/100
15%
Value28.8 s
0/100
10%
3793 ms
397 ms
683 ms
511 ms
403 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that all of those requests were addressed to Hanilbus.com and no external sources were called. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Hanilbus.com.
Page size can be reduced by 71.0 kB (36%)
195.5 kB
124.5 kB
In fact, the total size of Hanilbus.com main page is 195.5 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. 20% of websites need less resources to load. Images take 121.7 kB which makes up the majority of the site volume.
Potential reduce by 51.4 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 16.7 kB, which is 29% 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 51.4 kB or 88% of the original size.
Potential reduce by 8.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. Hanilbus images are well optimized though.
Potential reduce by 7.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 7.8 kB or 71% of the original size.
Potential reduce by 3.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. Hanilbus.com needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 75% of the original size.
Number of requests can be reduced by 44 (39%)
112
68
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hanilbus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
hanilbus.com
3793 ms
comm.js
397 ms
style.css
683 ms
ahahLib.js
511 ms
inside_popup.js
403 ms
hanilutil.js
624 ms
busCode.js
199 ms
tb_join.gif
202 ms
tnb_favorite.gif
229 ms
logo.gif
254 ms
menu_left.gif
313 ms
m00.gif
402 ms
m01.gif
457 ms
m02.gif
1362 ms
m03.gif
506 ms
m04.gif
508 ms
m05.gif
536 ms
m06.gif
599 ms
m07.gif
680 ms
m08.gif
755 ms
m09.gif
702 ms
menu_right.gif
735 ms
login_tit.gif
798 ms
login_id.gif
909 ms
btn_login.gif
897 ms
login_pw.gif
933 ms
btn_id_save.gif
1007 ms
btn_idsearch.gif
996 ms
counsel_img01.gif
1094 ms
counsel_img02.gif
1135 ms
banner01.gif
1332 ms
banner_no.gif
1196 ms
today.gif
1259 ms
1.gif
1289 ms
8.gif
1360 ms
3.gif
1396 ms
total.gif
1514 ms
2.gif
1487 ms
9.gif
1534 ms
now.gif
1606 ms
search_left.gif
1584 ms
search_icon.gif
1489 ms
btn_search.gif
1492 ms
btn_app.gif
1546 ms
search_right.gif
1491 ms
sm_left.gif
1514 ms
last_list.php
1472 ms
buy_last_list.php
1494 ms
sell_last_list.php
1455 ms
board_last_list.php
1456 ms
main_tab_bus.php
2075 ms
sm01.gif
1482 ms
sm02.gif
1453 ms
sm03.gif
1463 ms
sm04.gif
1404 ms
sm05.gif
1425 ms
sm06.gif
1463 ms
sm07.gif
1479 ms
sm_right.gif
1406 ms
tel_img.gif
1740 ms
banner_59.gif
1625 ms
q01.gif
1418 ms
q02.gif
1497 ms
q03.gif
1404 ms
q04.gif
1480 ms
q05.gif
1497 ms
btm_logo.gif
1470 ms
btm01.gif
1468 ms
btm02.gif
1496 ms
btm03.gif
1460 ms
btm04.gif
1538 ms
menu_bg.gif
1493 ms
login_bg.gif
1466 ms
login_dot.gif
1444 ms
bg.jpg
1480 ms
search_bg.gif
1493 ms
sm_bg.gif
1490 ms
bus_top.gif
1544 ms
sm01_on.gif
1499 ms
admin.css
1356 ms
print_embed.js
1411 ms
201508061309530.969401.jpg.thumb_s.jpg
750 ms
201508061302120.376621.jpg.thumb_s.jpg
701 ms
201507231202530.723996.jpeg.thumb_s.jpg
821 ms
201506221602170.12785.jpg.thumb_s.jpg
778 ms
201506221547280.2289.jpg.thumb_s.jpg
1053 ms
201504131512520.689533.jpeg.thumb_s.jpg
833 ms
201503131119410.054545.jpeg.thumb_s.jpg
900 ms
201503131113380.445982.jpeg.thumb_s.jpg
999 ms
201503131101010.906207.jpeg.thumb_s.jpg
978 ms
201503131055010.555336.jpeg.thumb_s.jpg
1071 ms
201503091740000.971113.jpeg.thumb_s.jpg
1032 ms
201503091732380.872608.jpeg.thumb_s.jpg
1095 ms
201503091124330.377823.jpeg.thumb_s.jpg
1176 ms
201503061407290.45124.jpeg.thumb_s.jpg
1250 ms
201502261654200.929655.jpeg.thumb_s.jpg
1232 ms
201502261631570.306229.jpeg.thumb_s.jpg
1279 ms
201502261612180.341481.jpeg.thumb_s.jpg
1321 ms
201502241736200.477625.jpeg.thumb_s.jpg
1286 ms
201502051639590.875086.jpg.thumb_s.jpg
1352 ms
201501212310410.027522.jpeg.thumb_s.jpg
1376 ms
201501200140090.151004.jpeg.thumb_s.jpg
1396 ms
201501200131480.603984.jpeg.thumb_s.jpg
1365 ms
201501200115200.997828.jpeg.thumb_s.jpg
1319 ms
201501231419340.408972.jpg.thumb_s.jpg
1350 ms
201412101441350.087214.jpeg.thumb_s.jpg
1337 ms
201411221519530.710385.jpeg.thumb_s.jpg
1336 ms
201410301738180.206024.jpeg.thumb_s.jpg
1374 ms
201410301731400.404803.jpeg.thumb_s.jpg
1387 ms
bus_btm.gif
1364 ms
board_bg.gif
1193 ms
buy_tit.gif
1144 ms
icon.gif
1205 ms
notice_tit.gif
1245 ms
hanilbus.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
hanilbus.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
Missing source maps for large first-party JavaScript
hanilbus.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
N/A
N/A
UFT-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hanilbus.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Hanilbus.com main page’s claimed encoding is uft-8. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
hanilbus.com
Open Graph description is not detected on the main page of Hanilbus. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: