13.2 sec in total
1.7 sec
11.3 sec
257 ms
Welcome to giantfishing.co.kr homepage info - get ready to check Giantfishing best content right away, or after learning these important things about giantfishing.co.kr
Visit giantfishing.co.krWe analyzed Giantfishing.co.kr page load time and found that the first response time was 1.7 sec and then it took 11.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.
giantfishing.co.kr performance score
name
value
score
weighting
Value14.6 s
0/100
10%
Value20.3 s
0/100
25%
Value14.6 s
1/100
10%
Value0 ms
100/100
30%
Value0.058
98/100
15%
Value15.2 s
7/100
10%
1686 ms
400 ms
1195 ms
601 ms
402 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 99% of them (79 requests) were addressed to the original Giantfishing.co.kr, 1% (1 request) were made to Webadsky.kr. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Giantfishing.co.kr.
Page size can be reduced by 211.5 kB (11%)
2.0 MB
1.8 MB
In fact, the total size of Giantfishing.co.kr main page is 2.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. 20% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 41.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 9.3 kB, which is 20% 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 41.4 kB or 86% of the original size.
Potential reduce by 98.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. Giantfishing images are well optimized though.
Potential reduce by 70.4 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 70.4 kB or 70% of the original size.
Potential reduce by 1.6 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. Giantfishing.co.kr needs all CSS files to be minified and compressed as it can save up to 1.6 kB or 67% of the original size.
Number of requests can be reduced by 18 (23%)
79
61
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Giantfishing. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
giantfishing.co.kr
1686 ms
style.css
400 ms
jquery-1.4.2.min.js
1195 ms
common.js
601 ms
rolling.js
402 ms
flash.js
426 ms
url.js
804 ms
capslock.js
638 ms
schedule.skin.css
387 ms
schedule.skin.js
420 ms
cp_logo_off.gif
790 ms
logo.jpg
420 ms
t_img01.jpg
602 ms
t_banner.gif
809 ms
t_img03.jpg
421 ms
home.jpg
421 ms
admin.jpg
433 ms
t_img02.jpg
1022 ms
login_tit.jpg
830 ms
join.jpg
846 ms
id_pw.jpg
840 ms
login_bt.jpg
1023 ms
m_img01.gif
1645 ms
m_img02.gif
1249 ms
m_img03.jpg
1648 ms
m_img04.jpg
1685 ms
m_img05_1.jpg
1416 ms
m_img05_2.jpg
1437 ms
m_img05_3.jpg
1645 ms
center.jpg
2665 ms
location.jpg
1859 ms
banner.jpg
2660 ms
main_new.jpg
3494 ms
m_tit01.jpg
2062 ms
latest_icon.gif
2089 ms
icon_hot.gif
2256 ms
m_tit02.jpg
2690 ms
icon_secret.gif
2519 ms
icon_reply.gif
2688 ms
m_tit03.jpg
3123 ms
more.jpg
3063 ms
2949778448_LyezgZ4b_C5A9B1E2BAAFC8AF_DSCF0704.JPG
3517 ms
2949778448_uApCoPFZ_C5A9B1E2BAAFC8AF_DSCF0683.JPG
3500 ms
2949778448_xE1cPfoj_C5A9B1E2BAAFC8AF_DSCF0680.JPG
3541 ms
2949778448_tGrelk4M_C5A9B1E2BAAFC8AF_DSCF0662.JPG
3896 ms
2949778448_gN3vI6T8_C5A9B1E2BAAFC8AF_DSCF0644.JPG
3932 ms
2949778448_zq07AxHL_C5A9B1E2BAAFC8AF_DSCF0626.JPG
4321 ms
2949778448_mL41rs3S_C5A9B1E2BAAFC8AF_DSCF0622.JPG
3914 ms
2949778448_nHhQo10N_C5A9B1E2BAAFC8AF_DSCF0605.JPG
3908 ms
2949778448_trJXgGxI_C5A9B1E2BAAFC8AF_DSCF0598.JPG
3963 ms
2949778448_g8EW3If6_C5A9B1E2BAAFC8AF_DSCF0578.JPG
4111 ms
2949778448_SnYVZb5W_C5A9B1E2BAAFC8AF_DSCF0562.JPG
3937 ms
2949778448_OnE0WXAu_C5A9B1E2BAAFC8AF_DSCF0547.JPG
4360 ms
2949778448_VIodZ1Qz_C5A9B1E2BAAFC8AF_DSCF0542.JPG
4374 ms
2949778448_QFVjYylb_C5A9B1E2BAAFC8AF_DSCF0509.JPG
4359 ms
2949778448_kDna8GIb_C5A9B1E2BAAFC8AF_DSCF0520.JPG
4356 ms
m_tit04.jpg
4113 ms
m_tit05.jpg
4147 ms
m_tit06.jpg
4317 ms
b_01.jpg
4381 ms
b_02.jpg
4168 ms
b_03.jpg
4163 ms
b_04.jpg
4397 ms
d_tit.jpg
3983 ms
b_prev.gif
4317 ms
b_next.gif
4142 ms
i_sunday.gif
3966 ms
i_monday.gif
4128 ms
i_tuesday.gif
3980 ms
i_wednesday.gif
3890 ms
i_thursday.gif
3766 ms
i_friday.gif
3775 ms
i_saturday.gif
3778 ms
copy.jpg
4358 ms
top_bg.gif
3585 ms
capslock.gif
3688 ms
598266502_Ft2UOJXl_P4140024.JPG
5055 ms
2949778448_ATP9ewuN_C5A9B1E2BAAFC8AF_C8B8C0FC_DSCF7209.JPG
5294 ms
1982172641_nrSeGx2u_C5A9B1E2BAAFC8AF_C5A9B1E2BAAFC8AF_C8B8C0FC_a_048.jpg
5138 ms
left.gif
3502 ms
giantfishing.co.kr 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-*] attributes do not match their roles
ARIA progressbar elements do not have accessible names.
giantfishing.co.kr 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
Issues were logged in the Issues panel in Chrome Devtools
giantfishing.co.kr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Giantfishing.co.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Giantfishing.co.kr main page’s claimed encoding is euc-kr. 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.
giantfishing.co.kr
Open Graph description is not detected on the main page of Giantfishing. 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: