10.1 sec in total
2.1 sec
7.8 sec
139 ms
Welcome to funasia.co homepage info - get ready to check Funasia best content right away, or after learning these important things about funasia.co
Visit funasia.coWe analyzed Funasia.co page load time and found that the first response time was 2.1 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
funasia.co performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value3.2 s
73/100
25%
Value2.4 s
98/100
10%
Value70 ms
99/100
30%
Value0.014
100/100
15%
Value3.4 s
93/100
10%
2115 ms
596 ms
398 ms
1175 ms
795 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 55% of them (48 requests) were addressed to the original Funasia.co, 9% (8 requests) were made to Pagead2.googlesyndication.com and 7% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Funasia.co.
Page size can be reduced by 265.2 kB (31%)
860.0 kB
594.9 kB
In fact, the total size of Funasia.co main page is 860.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% 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 526.8 kB which makes up the majority of the site volume.
Potential reduce by 55.4 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 55.4 kB or 81% of the original size.
Potential reduce by 68.1 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, Funasia needs image optimization as it can save up to 68.1 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 131.8 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 131.8 kB or 52% of the original size.
Potential reduce by 9.9 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. Funasia.co needs all CSS files to be minified and compressed as it can save up to 9.9 kB or 77% of the original size.
Number of requests can be reduced by 24 (29%)
82
58
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funasia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
funasia.co
2115 ms
zenaplus.css
596 ms
zenashopplus.css
398 ms
jquery-1.4.2.min.js
1175 ms
common.js
795 ms
ajax2.js
404 ms
adsbygoogle.js
6 ms
sideview.js
609 ms
slideshow_buttontitle.css
404 ms
jquery-1.3.2.min.js
1252 ms
slideshow_buttontitle.js
598 ms
style.css
204 ms
wrest.js
417 ms
denied.htm
391 ms
1924300205_8ab8bae5_main_07.jpg
599 ms
main_03.jpg
229 ms
eng.jpg
407 ms
jap.jpg
410 ms
chi.jpg
393 ms
kor.jpg
408 ms
top_menuline1.gif
397 ms
19.png
589 ms
search_03.gif
593 ms
908.jpg
1189 ms
907.jpg
803 ms
906.jpg
1049 ms
52
1174 ms
252.jpg
790 ms
401.jpg
793 ms
7530.jpg
989 ms
8756.jpg
992 ms
8045.jpg
1003 ms
1299.jpg
1422 ms
7239.jpg
1192 ms
8158.jpg
1204 ms
7640.jpg
1252 ms
267.jpg
1369 ms
361.jpg
1385 ms
340.jpg
1589 ms
339.jpg
1405 ms
349.jpg
1455 ms
1842.jpg
1564 ms
1601.jpg
1780 ms
1444.jpg
1807 ms
1535.jpg
1817 ms
btn_login.jpg
1657 ms
register.jpg
1760 ms
idpw.gif
1787 ms
1298.jpg
2064 ms
751.jpg
2150 ms
ca-pub-2598198298718872.js
70 ms
zrt_lookup.html
38 ms
show_ads_impl.js
65 ms
nanumgothic.css
32 ms
wp_ad_728.php
708 ms
ads
233 ms
NanumGothic-Bold.woff
38 ms
NanumGothic-ExtraBold.woff
88 ms
NanumGothic-Regular.woff
91 ms
osd.js
21 ms
ads
252 ms
wp_ad.php
693 ms
ads
169 ms
8455837122921508163
43 ms
abg.js
46 ms
m_js_controller.js
53 ms
googlelogo_color_112x36dp.png
28 ms
x_button_blue2.png
60 ms
s
58 ms
favicon
74 ms
nessie_icon_tiamat_white.png
28 ms
imgad
29 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
13 ms
wfr.php
730 ms
wfr.php
667 ms
731 ms
728.php
760 ms
activeview
13 ms
activeview
16 ms
activeview
18 ms
rta.js
19 ms
pop_ad.php
859 ms
210.png
460 ms
rta.js
10 ms
pop_ad.php
858 ms
CM_B_1023296.jpg
935 ms
CM_B_1023302.jpg
934 ms
funasia.co 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.
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
funasia.co best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
funasia.co 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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funasia.co can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Funasia.co 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.
funasia.co
Open Graph description is not detected on the main page of Funasia. 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: