13.3 sec in total
818 ms
11.8 sec
650 ms
Welcome to busan.com homepage info - get ready to check Busan best content for South Korea right away, or after learning these important things about busan.com
부산일보
Visit busan.comWe analyzed Busan.com page load time and found that the first response time was 818 ms and then it took 12.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
busan.com performance score
name
value
score
weighting
Value18.2 s
0/100
10%
Value32.0 s
0/100
25%
Value25.8 s
0/100
10%
Value14,010 ms
0/100
30%
Value0.027
100/100
15%
Value46.9 s
0/100
10%
818 ms
2588 ms
456 ms
1209 ms
1006 ms
Our browser made a total of 196 requests to load all elements on the main page. We found that 43% of them (84 requests) were addressed to the original Busan.com, 27% (53 requests) were made to News20.busan.com and 13% (25 requests) were made to Doctorq2.busan.com. The less responsive or slowest element that took the longest time to load (5.6 sec) relates to the external source News20.busan.com.
Page size can be reduced by 1.3 MB (26%)
5.1 MB
3.8 MB
In fact, the total size of Busan.com main page is 5.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.4 MB which makes up the majority of the site volume.
Potential reduce by 107.3 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.8 kB, which is 13% 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 107.3 kB or 82% of the original size.
Potential reduce by 864.8 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, Busan needs image optimization as it can save up to 864.8 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 297.7 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.7 kB or 58% of the original size.
Potential reduce by 38.9 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. Busan.com needs all CSS files to be minified and compressed as it can save up to 38.9 kB or 82% of the original size.
Number of requests can be reduced by 23 (12%)
191
168
The browser has sent 191 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Busan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
busan.com
818 ms
www.busan.com
2588 ms
base2015.css
456 ms
layout2015.css
1209 ms
news_slides.js
1006 ms
jquery-1.10.2.min.js
2766 ms
jquery.slides.js
1789 ms
slides.min.jquery.js
1332 ms
jquery.rolling.js
1571 ms
topmenu2.js
1101 ms
flash.js
473 ms
base.css
239 ms
BIZSPRING_INSIGHT_BASIC_SCRIPT_V2.0_BUSAN-1.JS
1275 ms
InsightClickZone.js
455 ms
ga.js
53 ms
face.gif
302 ms
15360_24014_5148.jpg
2002 ms
tweeter.gif
299 ms
star.gif
301 ms
line.gif
234 ms
logo.gif
450 ms
s_btn.gif
461 ms
bstoday100.jpg
476 ms
icon_01.jpg
474 ms
election_bar1.jpg
953 ms
section_title.jpg
739 ms
btube_title.jpg
684 ms
btn_001.jpg
689 ms
btn_002.jpg
708 ms
btn_003.jpg
716 ms
15banner_01.jpg
1369 ms
15banner_02.jpg
1153 ms
banner_01.jpg
1205 ms
banner_02.jpg
954 ms
btn_01.jpg
1519 ms
btn_02.jpg
1205 ms
btn_03.jpg
1206 ms
btn_04.jpg
1385 ms
btn_05.jpg
1416 ms
btn_06.jpg
1426 ms
btn_07.jpg
1432 ms
btn_08.jpg
1596 ms
btn_09.jpg
1614 ms
btn_10.jpg
1660 ms
btn_11.jpg
1669 ms
btn_12.jpg
1674 ms
btn_13.jpg
1762 ms
btn_14.jpg
1828 ms
btn_15.jpg
1842 ms
culture_bar.jpg
2604 ms
health_bar1.jpg
1900 ms
health_bar2.jpg
1912 ms
20160408000333_cutTitle.jpg
456 ms
20160408000185_t.jpg
769 ms
20160407000163_t.jpg
709 ms
20160408000173_t.jpg
716 ms
20160408000113_t.jpg
714 ms
20160403000079_t.jpg
1891 ms
20160407000279_t.jpg
689 ms
20160403000086_t.jpg
1610 ms
20160403000060_t.jpg
1445 ms
20160403000053_t.jpg
1426 ms
20160404000203_t.jpg
1976 ms
20160404000212_t.jpg
1529 ms
20160404000208_t.jpg
2130 ms
20160404000219_t.jpg
2153 ms
20160405000228_t.jpg
2505 ms
20160405000212_t.jpg
2060 ms
20160405000224_t.jpg
2589 ms
20160405000249_t.jpg
2687 ms
20160406000232_t.jpg
3702 ms
20160406000197_t.jpg
3071 ms
20160406000200_t.jpg
2855 ms
20160406000254_t.jpg
3508 ms
20160407000190_t.jpg
4454 ms
20160407000178_t.jpg
3405 ms
20160407000184_t.jpg
3603 ms
20160407000191_t.jpg
3790 ms
20160407000323_t.jpg
3644 ms
20160407000306_t.jpg
3752 ms
20160408000163_t.jpg
4305 ms
20160407000212_t.jpg
4361 ms
20160407000202_t.jpg
4442 ms
20160407000249_t.jpg
3995 ms
20160407000246_t.jpg
4024 ms
20160407000242_t.jpg
4258 ms
bn_new.html
3000 ms
20160407000196_t.jpg
4961 ms
20160407000302_t.jpg
5217 ms
__utm.gif
20 ms
doctorq.html
962 ms
hanbang.html
1017 ms
side_content.html
1474 ms
2012_right_main.html
1723 ms
guoffice_bar.jpg
1764 ms
land_bar.jpg
2007 ms
tracker.do
244 ms
kami300.jpg
2042 ms
ban_oceanceo1.jpg
1709 ms
wof300.jpg
2056 ms
popUnder1.jsp
4105 ms
ban_oceanceo.jpg
2065 ms
pre.jpg
1926 ms
next.jpg
1852 ms
plus.jpg
1932 ms
20160407000206_t.jpg
4642 ms
gimhae.gif
1934 ms
booble1.jpg
2073 ms
20160407000295_t.jpg
4651 ms
20160407000152_t.jpg
4742 ms
20160408000189_t.jpg
4092 ms
ban_sinmun1.jpg
2052 ms
20160408000105_t.jpg
4276 ms
ban_03.jpg
1837 ms
ban_33.jpg
1888 ms
drq_bar.jpg
690 ms
2.jpg
1305 ms
1.jpg
1369 ms
3.jpg
1385 ms
fb_01.jpg
1701 ms
hanbang_bar.jpg
1141 ms
h1.jpg
1381 ms
h11.jpg
1355 ms
h16.jpg
1872 ms
h14.jpg
1781 ms
h18.jpg
1784 ms
h3.jpg
1804 ms
h17.jpg
1828 ms
h12.jpg
1870 ms
h15.jpg
2031 ms
h13.jpg
2010 ms
h4.jpg
2032 ms
h7.jpg
2057 ms
h9.jpg
2326 ms
h2.jpg
2338 ms
h5.jpg
2234 ms
h6.jpg
2278 ms
h8.jpg
2257 ms
h10.jpg
2286 ms
fb_02.jpg
1675 ms
fb_03.jpg
1830 ms
fb_04.jpg
1825 ms
ff_01.jpg
1671 ms
ff_02.jpg
1694 ms
ff_03.jpg
1672 ms
ff_04.jpg
1690 ms
ff_05.jpg
1823 ms
20160401000149_t.jpg
3812 ms
20160408000162_t.jpg
3838 ms
ff_06.jpg
1762 ms
20160405000190_p.jpg
5350 ms
ff_07.jpg
1671 ms
fb_08.jpg
1699 ms
20160405000192_p.jpg
5575 ms
copy_logo.jpg
1663 ms
base.css
467 ms
layout.css
766 ms
thumb-2944214018_hXpiTmCP_c450x_125x95.jpg
515 ms
thumb-2944214018_V7mlcz3E_440x_125x95.jpg
521 ms
close_bt_en.jpg
1685 ms
arrow_off.png
1805 ms
bul_01.gif
1731 ms
bul_02.gif
1695 ms
bul_03.gif
1705 ms
20160405000189_p.jpg
5034 ms
all_bg.jpg
1658 ms
var.jpg
1679 ms
ajs.php
309 ms
4.jpg
1691 ms
3.jpg
1667 ms
2.jpg
1872 ms
1.jpg
1500 ms
adsbygoogle.js
45 ms
analytics.js
24 ms
collect
28 ms
ca-pub-5572554041307890.js
62 ms
zrt_lookup.html
121 ms
show_ads_impl.js
63 ms
pagination.png
1420 ms
collect
113 ms
here_top.jpg
1435 ms
line2.gif
465 ms
ads
140 ms
osd.js
13 ms
mb_style.css
762 ms
9701035545753369649
67 ms
abg.js
93 ms
m_js_controller.js
109 ms
googlelogo_color_112x36dp.png
43 ms
s
34 ms
x_button_blue2.png
33 ms
Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js
4 ms
activeview
20 ms
iadbn
1898 ms
jquery-1.6.2.min.js
86 ms
jquery-1.9.1.min.js
100 ms
busan.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
ARIA toggle fields do not have accessible names
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
Form elements do not have associated labels
Links do not have a discernible name
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.
busan.com 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
busan.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 Busan.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 Busan.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.
busan.com
Open Graph description is not detected on the main page of Busan. 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: