19.8 sec in total
875 ms
18.6 sec
311 ms
Visit goodmobile.kr now to see the best up-to-date Goodmobile content and also check out these interesting facts you probably never knew about goodmobile.kr
Visit goodmobile.krWe analyzed Goodmobile.kr page load time and found that the first response time was 875 ms and then it took 18.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
goodmobile.kr performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value1.284
1/100
15%
Value0
0/100
10%
875 ms
1012 ms
615 ms
1003 ms
1402 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 88% of them (66 requests) were addressed to the original Goodmobile.kr, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Wcs.naver.net. The less responsive or slowest element that took the longest time to load (15.7 sec) relates to the external source Img1.kbstar.com.
Page size can be reduced by 594.7 kB (59%)
1.0 MB
413.1 kB
In fact, the total size of Goodmobile.kr main page is 1.0 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. Javascripts take 464.5 kB which makes up the majority of the site volume.
Potential reduce by 30.7 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 30.7 kB or 79% of the original size.
Potential reduce by 74.1 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, Goodmobile needs image optimization as it can save up to 74.1 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 313.3 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 313.3 kB or 67% of the original size.
Potential reduce by 176.5 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. Goodmobile.kr needs all CSS files to be minified and compressed as it can save up to 176.5 kB or 87% of the original size.
Number of requests can be reduced by 12 (17%)
72
60
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Goodmobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
main.jsp
875 ms
style.css
1012 ms
jquery-ui-1.9.2.min.css
615 ms
jquery-1.9.0.min.js
1003 ms
jquery-ui-1.9.2.min.js
1402 ms
common.js
611 ms
wcslog.js
5 ms
main.css
616 ms
banner.js
815 ms
custom.js
817 ms
conversion.js
16 ms
m
403 ms
analytics.js
15 ms
header_bg.png
203 ms
logo.png
221 ms
top_banner_app.jpg
424 ms
tmn_bd.png
228 ms
gnb.png
229 ms
gnb_all.png
220 ms
header_detailbg.png
396 ms
header_txt_openmarket.png
433 ms
header_split.png
435 ms
header_txt_offline.png
435 ms
header_txt_compare.png
438 ms
header_txt_chart.png
599 ms
header_txt_used.png
623 ms
header_txt_usim.png
648 ms
header_txt_qna.png
647 ms
header_txt_wishlist.png
645 ms
header_txt_mylist.png
647 ms
header_txt_market.png
800 ms
escrowcmark.gif
15671 ms
popular_h1.png
820 ms
1.jpg
1035 ms
1.jpg
1040 ms
1.jpg
1823 ms
1.jpg
1632 ms
good_deal.jpg
1590 ms
counseling_h2.png
1029 ms
bestseller_h2.png
1230 ms
economic_h2.png
1234 ms
qna_h2.png
1240 ms
market_h2.png
1430 ms
news_h2.png
1439 ms
footer_menu1.png
1442 ms
footer_menu_line.png
1631 ms
footer_menu2.png
1643 ms
footer_menu3.png
1644 ms
footer_menu4.png
1789 ms
footer_menu5.png
1833 ms
collect
40 ms
57 ms
collect
77 ms
40 ms
mainPhoneSelect
1715 ms
logo2.png
1643 ms
footer_cs.png
1643 ms
btn_sliding.png
1783 ms
btn_prev_next.png
1803 ms
btn_updown.png
1651 ms
btn_go.png
1644 ms
btn_more.png
1636 ms
bbs_bg.png
1673 ms
footer_bg.png
1775 ms
1.jpg
306 ms
1.jpg
323 ms
1_170.jpg
537 ms
%EC%82%BC%EC%84%B1%EC%A0%84%EC%9E%90.png
341 ms
SKT.png
382 ms
1_170.jpg
486 ms
%EC%95%A0%ED%94%8C.png
501 ms
1_170.jpg
519 ms
1_170.jpg
538 ms
device_bg.png
581 ms
bg_color.png
686 ms
goodmobile.kr 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
<frame> or <iframe> elements do not have a title
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
goodmobile.kr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
goodmobile.kr SEO score
N/A
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Goodmobile.kr 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), while the claimed language is Korean. Our system also found out that Goodmobile.kr 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.
goodmobile.kr
Open Graph description is not detected on the main page of Goodmobile. 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: