56.4 sec in total
1.4 sec
54.1 sec
909 ms
Visit fangday.com now to see the best up-to-date Fangday content and also check out these interesting facts you probably never knew about fangday.com
Visit fangday.comWe analyzed Fangday.com page load time and found that the first response time was 1.4 sec and then it took 55 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
fangday.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value4.6 s
34/100
25%
Value4.2 s
78/100
10%
Value800 ms
37/100
30%
Value0.081
94/100
15%
Value6.9 s
54/100
10%
1449 ms
407 ms
413 ms
389 ms
418 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 71% of them (92 requests) were addressed to the original Fangday.com, 12% (15 requests) were made to Naverbam.com and 3% (4 requests) were made to Kissinfo.co.kr. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Kissinfo.co.kr.
Page size can be reduced by 608.9 kB (15%)
4.1 MB
3.5 MB
In fact, the total size of Fangday.com main page is 4.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. 45% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 108.5 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.0 kB, which is 12% 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 108.5 kB or 82% of the original size.
Potential reduce by 257.9 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. Fangday images are well optimized though.
Potential reduce by 71.9 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 71.9 kB or 67% of the original size.
Potential reduce by 170.7 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. Fangday.com needs all CSS files to be minified and compressed as it can save up to 170.7 kB or 81% of the original size.
Number of requests can be reduced by 52 (48%)
108
56
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fangday. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
fangday.com
1449 ms
407 ms
jquery.fancybox.css
413 ms
tooltipster.css
389 ms
amina.css
418 ms
layout-pc.css
528 ms
suggest.css
735 ms
suggest.css
876 ms
heart_gift.css
745 ms
default_minifier.css
753 ms
font-awesome.min.css
93 ms
jquery.min.js
216 ms
696 ms
739 ms
867 ms
1173 ms
941 ms
webfont.js
239 ms
1154 ms
1162 ms
jquery.fancybox.js
1246 ms
1256 ms
1226 ms
1381 ms
1384 ms
1450 ms
1293 ms
all.js
130 ms
1135 ms
1147 ms
modern-ticker.css
1397 ms
theme.css
1396 ms
jquery.nivo.slider.js
1560 ms
nivo.slider.css
1464 ms
latest.list.css
1505 ms
latest.head.css
1634 ms
latest.list.css
1945 ms
latest.head.css
1863 ms
1635 ms
1687 ms
latest.list.css
1881 ms
jquery.ticker.js
1993 ms
1738 ms
latest-pc.css
1881 ms
suggest.js.php
1851 ms
1757 ms
follower.js
1734 ms
analytics.js
114 ms
2049101430_1459841010_EB8C80EBACB8+copy.jpg
19873 ms
0RdGsPcERK
1438 ms
34c92dcf8d0d469cf8a459197f95012f_1459249857_97.jpg
843 ms
b8yOzgC.gif
302 ms
26hv07n9s8
1944 ms
01_%EB%A9%94%EC%9D%B8%EC%9E%90%EB%A5%B8%EA%B1%B01.gif
3277 ms
%ED%83%A0%EC%8A%A4%ED%8C%8C.jpg
646 ms
3331271681_1454298755.0749.gif
4081 ms
2049863754_1455723065_ECA3BCEB8C95EC9DB4.PNG
19862 ms
kkW2j44.jpg
292 ms
greyzz.png
1510 ms
parallax_abs.png
1538 ms
naverbam_logo1.png
1603 ms
user.png
1595 ms
password.png
1603 ms
face.png
1447 ms
Twitter.png
1928 ms
googleplus.png
2053 ms
d0360e644ca3a040529c37b71be140e0_1459474602_15.gif
915 ms
fd85b3d68295aa91be8388002df59979_1457663124_82.jpg
918 ms
3076780105_lEr1MSmn_imagesQXJDMU8J.jpg
2243 ms
2040886604_3eCBYSx6_f2199a9be640324e92b9c2c1c3741c3144ad1841.jpg
2181 ms
3547328547_OkcyvzWY_cdf0c998f235c802a971db7c4dcb00e31a47212f.jpg
2075 ms
blank.gif
1940 ms
collect
64 ms
128312_0_%25EA%25B0%2580%25ED%259D%25AC.jpg
2167 ms
3745434708_gC65f7oX_a4d34e9f391a9653867aea9cd614cbbc76a763b3.jpg
2345 ms
ico16_fb.png
2193 ms
fontawesome-webfont.woff
103 ms
ico16_twt.png
2282 ms
ico16_google.png
2314 ms
9015.gif
2198 ms
192 ms
xd_arbiter.php
129 ms
xd_arbiter.php
184 ms
rss.php
481 ms
ad150-crop-120x120.png
2227 ms
2737.gif
2264 ms
104.gif
2331 ms
color.gif
2430 ms
xpxp.gif
2757 ms
110.gif
2135 ms
201h.gif
2381 ms
117.gif
2389 ms
twitter-bird-sprite-e0FhFKaXRI.png
2303 ms
sp_mn20140408.png
2312 ms
nb_sprite.png
2570 ms
fd85b3d68295aa91be8388002df59979_1457663124_82.jpg
328 ms
bullet-over.png
2365 ms
pause.png
2373 ms
arrow-prev.png
2224 ms
play.png
2262 ms
arrow-next.png
2707 ms
preloader.gif
2496 ms
loading.gif
2690 ms
ping
83 ms
latest.php
2398 ms
ico_comm_v113.png
2271 ms
bullet.png
2528 ms
1.gif
2613 ms
blank.gif
2534 ms
2.gif
2582 ms
no-img.png
2165 ms
3.gif
2298 ms
gray_bg.png
2348 ms
nb_login_nw2.png
2460 ms
enter_kind_main.png
2253 ms
1728759242_9P8OI5BS_948d9bffa9fbe3abb8a508053519eac545c5a032.jpg
224 ms
tumblr_nwnkqjZXjR1usqv2io1_1280.jpg
135 ms
147c5a22a35d7cc9b8ae86d6b1a6d12a_1460085364_04.jpg
216 ms
3553674809_8s7vjA4K_b6ba4952e3b0d5d7635c618572f0fe4dd153fbcf.jpg
860 ms
2049101430_1459841010_EB8C80EBACB8+copy.jpg
19970 ms
arrows.png
406 ms
34c92dcf8d0d469cf8a459197f95012f_1459249857_97.jpg
1712 ms
34c92dcf8d0d469cf8a459197f95012f_1459249857_97.jpg
276 ms
34c92dcf8d0d469cf8a459197f95012f_1459249857_97.jpg
269 ms
2049101430_1459841010_EB8C80EBACB8+copy.jpg
19854 ms
34c92dcf8d0d469cf8a459197f95012f_1459249857_97.jpg
519 ms
34c92dcf8d0d469cf8a459197f95012f_1459249857_97.jpg
190 ms
34c92dcf8d0d469cf8a459197f95012f_1459249857_97.jpg
227 ms
34c92dcf8d0d469cf8a459197f95012f_1459249857_97.jpg
732 ms
34c92dcf8d0d469cf8a459197f95012f_1459249857_97.jpg
239 ms
fangday.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
fangday.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
Uses deprecated APIs
Browser errors were logged to the console
fangday.com SEO score
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
KO
KO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fangday.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Fangday.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.
fangday.com
Open Graph data is detected on the main page of Fangday. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: