7.7 sec in total
679 ms
6.8 sec
221 ms
Click here to check amazing Strongfe content. Otherwise, check out these important facts you probably never knew about strongfe.com
Visit strongfe.comWe analyzed Strongfe.com page load time and found that the first response time was 679 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
strongfe.com performance score
name
value
score
weighting
Value2.7 s
60/100
10%
Value6.2 s
11/100
25%
Value4.5 s
73/100
10%
Value750 ms
39/100
30%
Value0.147
77/100
15%
Value7.1 s
52/100
10%
679 ms
274 ms
10 ms
660 ms
249 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Strongfe.com, 36% (50 requests) were made to Blogthumb2.naver.net and 23% (32 requests) were made to Blogimgs.naver.net. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Blogthumb2.naver.net.
Page size can be reduced by 984.2 kB (56%)
1.8 MB
781.7 kB
In fact, the total size of Strongfe.com main page is 1.8 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. 65% of websites need less resources to load. Javascripts take 980.3 kB which makes up the majority of the site volume.
Potential reduce by 391 B
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 391 B or 44% of the original size.
Potential reduce by 61.6 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, Strongfe needs image optimization as it can save up to 61.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 722.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 722.6 kB or 74% of the original size.
Potential reduce by 199.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. Strongfe.com needs all CSS files to be minified and compressed as it can save up to 199.6 kB or 85% of the original size.
Number of requests can be reduced by 54 (39%)
137
83
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Strongfe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
strongfe.com
679 ms
good2114
274 ms
Frameset-981964519.js
10 ms
PrologueList.nhn
660 ms
NBlogHidden.nhn
249 ms
Hidden-597428542.js
5 ms
MusicPlayer-449972894.js
14 ms
LayoutTopCommon-484882993.css
7 ms
player-846d457.css
13 ms
RemoveSubDomain-dea9950.js
12 ms
Jindo152-363950062.js
13 ms
LayoutTopCommon-730083628.js
18 ms
JindoComponent-318925938.js
21 ms
PrologueWebzine-71207160.css
20 ms
gnb_quirks_euckr.nhn
253 ms
allowSwfForChrome-7dd9772.js
19 ms
LayoutBottomCommon-902441421.js
44 ms
spc.gif
19 ms
1007_login.png
22 ms
SAM_2001.JPG
768 ms
2ede2546067d1af1f762f74226d051228a01_ugcvideo_270P_01_16x9_logo.jpg
1322 ms
btn_confirm2.gif
21 ms
profileimage.jpg
731 ms
blank.gif
18 ms
btn_confirm.gif
17 ms
btn_cancel.gif
16 ms
btn_close.gif
17 ms
btn_thin_close.gif
17 ms
btn_close8.gif
18 ms
ico_file.gif
19 ms
btn_download2.gif
19 ms
btn_cancel3.gif
21 ms
btn_close3.gif
19 ms
btn_close5.gif
20 ms
btn_confirm.gif
21 ms
btn_cancel.gif
21 ms
btn_close_1.gif
20 ms
btn_viewexif.gif
21 ms
btn_originaldn.gif
22 ms
spc.gif
22 ms
tit_viewexif.gif
21 ms
ico_notice2.gif
22 ms
btn_close.gif
23 ms
btn_close3.gif
22 ms
btn_close.gif
22 ms
btn_ok.gif
23 ms
btn_close2.gif
23 ms
btn_confirm_pop2.gif
24 ms
btn_cancel_pop2.gif
24 ms
ico_help.gif
17 ms
SAM_1945.JPG
986 ms
SAM_1877.JPG
770 ms
SAM_1754.JPG
771 ms
SAM_1615.JPG
779 ms
SAM_1601.JPG
795 ms
SAM_9872.JPG
1225 ms
%C4%AB%C7%AA%C4%A1%B3%EB.PNG
1262 ms
20160311_122247.jpg
1276 ms
SAM_1496.JPG
1859 ms
SAM_1478.JPG
1392 ms
SAM_1417.JPG
1547 ms
SAM_1344.JPG
1769 ms
SAM_2001.JPG
1910 ms
SAM_1308.JPG
1805 ms
SAM_1275.JPG
1903 ms
SAM_1171.JPG
2059 ms
SAM_1070.JPG
2300 ms
20160301_154343.jpg
2322 ms
SAM_8575.JPG
2337 ms
SAM_1007.JPG
2401 ms
SAM_0962.JPG
2435 ms
SAM_0907.JPG
2568 ms
20151013_192134.jpg
2862 ms
SAM_0825.JPG
2818 ms
20160223_154803.jpg
2872 ms
SAM_0701.JPG
2903 ms
SAM_0601.JPG
2986 ms
SAM_0571.JPG
3099 ms
SAM_0478.JPG
3403 ms
SAM_0447.JPG
3389 ms
SAM_0385.JPG
3418 ms
3.gif
3471 ms
SAM_0130.JPG
3490 ms
SAM_0072.JPG
3640 ms
SAM_9703.JPG
3926 ms
promo_npay.png
43 ms
0119_h982_1.gif
33 ms
KakaoTalk_20151108_210611852.jpg
1003 ms
ic_play.png
24 ms
btn_blogsearch.gif
32 ms
shadow.png
32 ms
shadow02.png
34 ms
bg_not_available_word.gif
33 ms
0119_b982.gif
209 ms
0144_966.gif
33 ms
0101_back.gif
291 ms
0140_head.gif
77 ms
0140_body.gif
34 ms
0140_footer.gif
35 ms
0104_image_1.gif
32 ms
0119_f982_1.gif
33 ms
WidgetListAsync.nhn
328 ms
m
632 ms
1005_head.gif
12 ms
profileimage.jpg
486 ms
1005_body.gif
8 ms
0000_icon.gif
9 ms
1005_footer.gif
8 ms
SAM_9979.JPG
3178 ms
SAM_9925.JPG
3261 ms
SAM_9890.JPG
3244 ms
SAM_9843.JPG
3213 ms
1444098490800.jpeg
3359 ms
ExternalWidgetRender.nhn
1442 ms
ExternalWidgetRender.nhn
1487 ms
ExternalWidgetRender.nhn
1497 ms
ExternalWidgetRender.nhn
1536 ms
ExternalWidgetRender.nhn
1573 ms
1.gif
3451 ms
SAM_9788.JPG
3271 ms
SAM_9739.JPG
3210 ms
SAM_9669.JPG
3224 ms
SAM_9579.JPG
3154 ms
20160125_115852.jpg
3130 ms
getLoginStatus.nhn
735 ms
SAM_9542.JPG
3256 ms
SAM_9482.JPG
3182 ms
%B8%F0%C4%AB%C6%F7%C6%AE.jpg
3237 ms
%BA%ED%B7%CE%B9%CC%C0%A7%C1%AC%C5%BA%BB%FD.png
1346 ms
%C0%A7%C1%AC.jpg
721 ms
%C0%A7%C1%AC1.PNG
682 ms
img.php
933 ms
%BD%C3%BF%F8%BA%E4_%C0%A7%C1%AC.png
355 ms
promo_npay_1603.png
8 ms
clickcrD.js
8 ms
1007_menu.png
8 ms
sp_gnb_v10.png
5 ms
img.php
312 ms
strongfe.com 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 input fields do not have accessible names
ARIA toggle fields do not have accessible names
ARIA IDs are not unique
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
strongfe.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
strongfe.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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Strongfe.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Strongfe.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.
strongfe.com
Open Graph description is not detected on the main page of Strongfe. 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: