16.7 sec in total
735 ms
15.6 sec
346 ms
Visit fomos.co.kr now to see the best up-to-date Fomos content for United States and also check out these interesting facts you probably never knew about fomos.co.kr
e스포츠, 게임기사 제공,포토,연예,스포츠 ,TALK,커뮤니티
Visit fomos.co.krWe analyzed Fomos.co.kr page load time and found that the first response time was 735 ms and then it took 16 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fomos.co.kr performance score
name
value
score
weighting
Value7.4 s
1/100
10%
Value9.6 s
0/100
25%
Value15.1 s
1/100
10%
Value190 ms
91/100
30%
Value0.002
100/100
15%
Value13.0 s
13/100
10%
735 ms
1028 ms
464 ms
1147 ms
5 ms
Our browser made a total of 164 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fomos.co.kr, 45% (74 requests) were made to Fomos.kr and 5% (9 requests) were made to Ad.about.co.kr. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Fomos.kr.
Page size can be reduced by 648.3 kB (26%)
2.4 MB
1.8 MB
In fact, the total size of Fomos.co.kr main page is 2.4 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 1.9 MB which makes up the majority of the site volume.
Potential reduce by 83.1 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 11.5 kB, which is 11% 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 83.1 kB or 81% of the original size.
Potential reduce by 230.2 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, Fomos needs image optimization as it can save up to 230.2 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 256.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 256.7 kB or 72% of the original size.
Potential reduce by 78.3 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. Fomos.co.kr needs all CSS files to be minified and compressed as it can save up to 78.3 kB or 79% of the original size.
Number of requests can be reduced by 43 (28%)
155
112
The browser has sent 155 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fomos. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
fomos.co.kr
735 ms
www.fomos.kr
1028 ms
fomos.css
464 ms
jquery-1.11.3.min.js
1147 ms
adsbygoogle.js
5 ms
ad.js
762 ms
ad_fixedad.js
456 ms
ad.min.js
1359 ms
fomos.js
513 ms
logo.png
248 ms
top_favorite.png
255 ms
top_facebook.png
254 ms
g_community.png
477 ms
gicon01.png
486 ms
gnb01_off.png
491 ms
gnb02_off.png
489 ms
gnb03_off.png
483 ms
gnb07_off.png
503 ms
gnb04_off.png
689 ms
gnb05_off.png
712 ms
btn_sch.png
720 ms
btn_close2.png
728 ms
maintab01_off.png
725 ms
maintab02_off.png
748 ms
maintab03_off.png
941 ms
maintab04_off.png
956 ms
1458460454248240.jpg
1909 ms
1458056521559023.jpg
1905 ms
1458397868768689.jpg
2020 ms
1458411087275722.jpg
2690 ms
1458411454331269.jpg
2370 ms
1458292727066708.jpg
2187 ms
1458292727310652.jpg
2142 ms
1458292727271882.jpg
2376 ms
1458292727758611.jpg
2379 ms
1458292728859275.jpg
2686 ms
1458285231305685.jpg
2479 ms
1458100058407039.jpg
2606 ms
1458100058240237.jpg
2612 ms
1458100058227480.jpg
2708 ms
1458100058818091.jpg
2856 ms
1458476696654621.jpg
2937 ms
1458355137309232.jpg
2942 ms
1458354895906574.jpg
2937 ms
analytics.js
39 ms
1458357552629610.jpg
3047 ms
ca-pub-6693051407927457.js
138 ms
zrt_lookup.html
166 ms
show_ads_impl.js
85 ms
sdk.js
136 ms
collect
88 ms
ad_live.html
694 ms
wfr.php
2440 ms
ads
168 ms
rta.js
34 ms
ad_fixedad.php
475 ms
osd.js
31 ms
rtbpam
344 ms
121 ms
xd_arbiter.php
38 ms
xd_arbiter.php
50 ms
1458357552132994.jpg
2852 ms
1458359882381057.jpg
3344 ms
1458315408005164.jpg
3941 ms
603386124807336077
34 ms
abg.js
38 ms
m_js_controller.js
50 ms
googlelogo_color_112x36dp.png
49 ms
s
27 ms
x_button_blue2.png
26 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
3 ms
imp
1333 ms
imp
1327 ms
imp
1334 ms
1458293028316490.jpg
3151 ms
1458293028420948.jpg
2715 ms
1458448032558674.jpg
2795 ms
1458448066049392.jpg
2850 ms
1458448172294002.jpg
2960 ms
1458448246119969.jpg
2999 ms
like.php
67 ms
like.php
78 ms
wy1X4hBW7e7.js
35 ms
LVx-xkvaJ0b.png
25 ms
1458443371794569.jpg
2892 ms
1458443068547427.jpg
2988 ms
1458271925463850.jpg
3225 ms
1458271925257764.jpg
3578 ms
1458271925193381.jpg
3378 ms
1458462419074590.jpg
3124 ms
ad.css
228 ms
1458442205946796.jpg
3249 ms
1458443134837468.jpg
3212 ms
afr.php
39 ms
ad_asyn_ct_passback.html
230 ms
lg.php
21 ms
match.aspx
20 ms
banner120600N.php
434 ms
ad_live.html
241 ms
activeview
12 ms
RollingCtrl.js
436 ms
show_ads.js
3 ms
ads
72 ms
googleReturn.php
231 ms
vimp
639 ms
vimp
646 ms
vimp
692 ms
552B9595027B950001
530 ms
roosevelt_sher.js
686 ms
d_i.gif
676 ms
b4499738de2fdc05857a2b9567604a56
566 ms
ad_live.html
236 ms
1458448603632274.jpg
2441 ms
1458447961907867.jpg
2671 ms
wfr.php
1463 ms
count.php
493 ms
soea_xCntM.php
427 ms
arrow_left.png
2411 ms
wfr.php
444 ms
arrow_right.png
2296 ms
call_banner.png
2653 ms
btn_top.png
2271 ms
bg_header.png
2300 ms
btn_mini.png
2409 ms
soea_xCntV.php
468 ms
s.gif
661 ms
s.gif
643 ms
bg_poplay.png
2338 ms
s.gif
599 ms
ad_live.html
237 ms
imp
697 ms
bg_two.png
2271 ms
bg_redone.png
2309 ms
bul01.png
2241 ms
bg_tab.png
2349 ms
bg_bottom.png
2346 ms
middle_middle
609 ms
foot_logo.png
2227 ms
bg_span01.png
2175 ms
maintab02_on.png
2230 ms
552B9594020C470001
69 ms
jquery-1.8.2.min.js
421 ms
jquery.base64.js
409 ms
adbay.controller.v1.10.js
410 ms
base.css
414 ms
slide.css
413 ms
slide.common.js
440 ms
slide.300x250.controller.js
617 ms
connect.php
458 ms
middle_middle
635 ms
_pb_semantic_info.php
1007 ms
middle_middle
203 ms
adbayReturn.php
249 ms
ad_live.html
268 ms
_n2s_nbz_ads_info.php
1128 ms
count.php
480 ms
aecad42329922dfc97eee948606e1f8e
1141 ms
jquery.min.js
6 ms
_n2s_nbz_banner_common_0602.js
2814 ms
btn_logo_off.png
330 ms
4a04cbb40100b2424c90ad99d3828dba.jpg
2753 ms
white_2.png
695 ms
_n2s_normal_ad_view.php
891 ms
ui
25 ms
fomos.co.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
Links do not have a discernible name
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
fomos.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
fomos.co.kr SEO score
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 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 Fomos.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 Fomos.co.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.
fomos.co.kr
Open Graph description is not detected on the main page of Fomos. 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: