13.3 sec in total
885 ms
12.3 sec
144 ms
Click here to check amazing Fc content. Otherwise, check out these important facts you probably never knew about fc.co.kr
♡포춘쿠키
Visit fc.co.krWe analyzed Fc.co.kr page load time and found that the first response time was 885 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.
fc.co.kr performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value23.7 s
0/100
25%
Value12.7 s
3/100
10%
Value140 ms
95/100
30%
Value0.582
11/100
15%
Value9.2 s
32/100
10%
885 ms
976 ms
596 ms
453 ms
456 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that all of those requests were addressed to Fc.co.kr and no external sources were called. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Fc.co.kr.
Page size can be reduced by 434.6 kB (26%)
1.7 MB
1.2 MB
In fact, the total size of Fc.co.kr main page is 1.7 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. 25% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 26.9 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 26.9 kB or 87% of the original size.
Potential reduce by 343.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. Obviously, Fc needs image optimization as it can save up to 343.7 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 57.6 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 57.6 kB or 78% of the original size.
Potential reduce by 6.4 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. Fc.co.kr needs all CSS files to be minified and compressed as it can save up to 6.4 kB or 78% of the original size.
We found no issues to fix!
71
71
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fc. According to our analytics all requests are already optimized.
index.php
885 ms
common.js
976 ms
godo.cart_tab.js
596 ms
style.css
453 ms
style.css
456 ms
style_horizontal.css
397 ms
close.gif
453 ms
btn_mypage_go.gif
455 ms
header_login.jpg
937 ms
index.php
863 ms
main.jpg
1612 ms
logo_text.jpg
681 ms
bottom_company.gif
498 ms
bottom_private.gif
510 ms
bottom_agreed.gif
882 ms
bottom_center.gif
893 ms
bottom_guide.gif
937 ms
bottom_idpw.gif
1134 ms
bottom_side.gif
1318 ms
btn_c_view.gif
1295 ms
bottom_cs.gif
1344 ms
blank.php
1390 ms
rolling56.jpg
1736 ms
rolling57.jpg
2049 ms
rolling58.jpg
1880 ms
rolling60.jpg
2111 ms
rolling61.jpg
2289 ms
rolling62.jpg
2364 ms
rolling17.jpg
2515 ms
rolling42.jpg
2660 ms
rolling46.jpg
2832 ms
rolling35.jpg
3009 ms
rolling13.jpg
3052 ms
rolling14.jpg
3262 ms
rolling15.jpg
3300 ms
rolling16.jpg
3566 ms
rolling18.jpg
3783 ms
rolling19.jpg
3828 ms
rolling20.jpg
3851 ms
rolling21.jpg
4068 ms
rolling22.jpg
4228 ms
rolling23.jpg
4457 ms
rolling24.jpg
4543 ms
rolling25.jpg
4676 ms
rolling26.jpg
4268 ms
rolling27.jpg
4501 ms
rolling28.jpg
4613 ms
rolling29.jpg
4598 ms
rolling30.jpg
4841 ms
rolling31.jpg
4760 ms
rolling32.jpg
4652 ms
rolling33.jpg
4838 ms
rolling34.jpg
4782 ms
rolling36.jpg
4885 ms
rolling37.jpg
5111 ms
rolling38.jpg
5210 ms
rolling39.jpg
5064 ms
rolling40.jpg
5076 ms
rolling41.jpg
4955 ms
rolling43.jpg
5072 ms
rolling44.jpg
5183 ms
rolling45.jpg
5231 ms
rolling47.jpg
5174 ms
rolling48.jpg
5103 ms
rolling49.jpg
4872 ms
rolling50.jpg
4887 ms
rolling51.jpg
5086 ms
rolling52.jpg
5000 ms
rolling53.jpg
5011 ms
rolling54.jpg
4811 ms
rolling55.jpg
4862 ms
rolling59.jpg
4745 ms
fc.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 input fields do not have accessible names
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
Buttons do not have an accessible name
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
fc.co.kr 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fc.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
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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 doesn't use legible font sizes
KO
N/A
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fc.co.kr 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 Fc.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.
fc.co.kr
Open Graph description is not detected on the main page of Fc. 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: