8.7 sec in total
2.1 sec
6.4 sec
218 ms
Click here to check amazing Fbml content for South Korea. Otherwise, check out these important facts you probably never knew about fbml.co.kr
실용적인 마케팅 활용 가이드 및 리소스 제공 블로그
Visit fbml.co.krWe analyzed Fbml.co.kr page load time and found that the first response time was 2.1 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fbml.co.kr performance score
name
value
score
weighting
Value5.8 s
5/100
10%
Value6.6 s
8/100
25%
Value18.1 s
0/100
10%
Value19,470 ms
0/100
30%
Value0.057
98/100
15%
Value32.6 s
0/100
10%
2076 ms
13 ms
430 ms
478 ms
478 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 19% of them (22 requests) were addressed to the original Fbml.co.kr, 10% (12 requests) were made to Sumome.com and 10% (12 requests) were made to Sumome-140a.kxcdn.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Fbml.co.kr.
Page size can be reduced by 1.2 MB (72%)
1.7 MB
483.2 kB
In fact, the total size of Fbml.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. 85% 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. CSS take 925.3 kB which makes up the majority of the site volume.
Potential reduce by 47.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 47.9 kB or 75% of the original size.
Potential reduce by 45.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. Obviously, Fbml needs image optimization as it can save up to 45.9 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 259.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 259.6 kB or 60% of the original size.
Potential reduce by 861.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. Fbml.co.kr needs all CSS files to be minified and compressed as it can save up to 861.6 kB or 93% of the original size.
Number of requests can be reduced by 59 (54%)
109
50
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fbml. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.fbml.co.kr
2076 ms
wcslog.js
13 ms
style.css
430 ms
widget.css
478 ms
style.css
478 ms
styles.css
479 ms
gallery.min.css
480 ms
lightbox.min.css
488 ms
jquery.js
1289 ms
jquery-migrate.min.js
905 ms
smoothscroll.js
950 ms
load.sumome.com
344 ms
adsbygoogle.js
19 ms
widget.js
61 ms
jquery.form.min.js
959 ms
scripts.js
971 ms
jquery.touchwipe.min.js
1009 ms
jquery.lightbox.min.js
1457 ms
pop.js
16 ms
m
508 ms
nanumgothic.css
25 ms
css
15 ms
wp-emoji-release.min.js
940 ms
ga.js
11 ms
__utm.gif
36 ms
collect
53 ms
logo.png
298 ms
main.jpg
1473 ms
instagram-accounts-150x150.jpg
732 ms
sns-150x150.jpg
738 ms
featured-image-150x150.jpg
809 ms
Untitled-21-150x150.jpg
771 ms
Untitled-2-150x150.jpg
1232 ms
NanumGothic-Regular.woff
33 ms
NanumGothic-Bold.woff
67 ms
NanumGothic-ExtraBold.woff
67 ms
cj2hUnSRBhwmSPr9kS589-LrC4Du4e_yfTJ8Ol60xk0.ttf
28 ms
c92rD_x0V1LslSFt3-QEpmsGzsqhEorxQDpu60nfWEc.ttf
29 ms
QQt14e8dY39u-eYBZmppwZ_TkvowlIOtbR7ePgFOpF4.ttf
28 ms
ca-pub-0305070047925346.js
149 ms
zrt_lookup.html
158 ms
show_ads_impl.js
113 ms
widgets.js
117 ms
all.js
69 ms
379 ms
ads
312 ms
osd.js
14 ms
ads
224 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
125 ms
73 ms
xd_arbiter.php
46 ms
xd_arbiter.php
53 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
44 ms
info.json
106 ms
abg.js
31 ms
m_js_controller.js
6 ms
favicon
79 ms
s
23 ms
googlelogo_color_112x36dp.png
64 ms
nessie_icon_tiamat_white.png
17 ms
x_button_blue2.png
21 ms
service.js
44 ms
service.js
44 ms
service.js
17 ms
load
250 ms
sumome-image-sharer.css
10 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
3 ms
sumome-share-client.css
20 ms
sumome-scrollbox-popup.css
15 ms
jot
84 ms
css
28 ms
load
227 ms
load
224 ms
facebook-white-60.png
30 ms
shares.json
73 ms
links.getStats
42 ms
links.getStats
64 ms
count.json
80 ms
button_info.json
35 ms
yum-count
174 ms
pinterest-white-60.png
11 ms
googleplus-white-60.png
19 ms
twitter-white-60.png
9 ms
email-white-60.png
17 ms
sumome-white-60.png
28 ms
share
55 ms
jsonpcallback
245 ms
jsonpcallback
182 ms
rpc
133 ms
jsonpcallback
181 ms
jsonpcallback
229 ms
jsonpcallback
260 ms
jsonpcallback
295 ms
jsonpcallback
227 ms
jsonpcallback
223 ms
ui
64 ms
graph.facebook.com
85 ms
xd_arbiter.php
31 ms
like_box.php
70 ms
xYm_UD1pmAz.css
31 ms
TGpOWuX6Pv8.css
27 ms
_rx8naC75Dy.js
32 ms
x5F9OMjKyLw.js
43 ms
ICDbTSzjQEg.js
29 ms
TTCre3391I0.js
26 ms
1012291_646561802045637_976170397_n.jpg
40 ms
1920346_646562645378886_665697393_n.jpg
11 ms
12662426_1039699522766524_2342954478185585946_n.jpg
12 ms
11692786_461317997381132_4985835106196792583_n.jpg
14 ms
10262123_918554268239919_1887761630682731939_n.jpg
15 ms
11781897_1506609322963038_2319674952718045334_n.jpg
13 ms
1525279_882198905229236_3952720761004775772_n.jpg
12 ms
1488272_332407400300558_7456255231360422508_n.jpg
14 ms
999447_521860677896523_1063722676_n.jpg
15 ms
wL6VQj7Ab77.png
9 ms
s7jcwEQH7Sx.png
10 ms
I6-MnjEovm5.js
3 ms
vlXaquuXMrr.js
4 ms
fbml.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Form elements do not have associated labels
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.
fbml.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
fbml.co.kr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fbml.co.kr can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it does not match the claimed English language. Our system also found out that Fbml.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.
fbml.co.kr
Open Graph data is detected on the main page of Fbml. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: