11.3 sec in total
611 ms
9.8 sec
862 ms
Click here to check amazing FEALAC content. Otherwise, check out these important facts you probably never knew about fealac.org
동아시아-라틴아메리카 협력포럼, 설립목적, 회원국 안내, 회의 소식 제공 등
Visit fealac.orgWe analyzed Fealac.org page load time and found that the first response time was 611 ms and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fealac.org performance score
name
value
score
weighting
Value12.2 s
0/100
10%
Value19.0 s
0/100
25%
Value34.4 s
0/100
10%
Value7,090 ms
0/100
30%
Value0.026
100/100
15%
Value52.6 s
0/100
10%
611 ms
1785 ms
35 ms
54 ms
58 ms
Our browser made a total of 159 requests to load all elements on the main page. We found that 60% of them (96 requests) were addressed to the original Fealac.org, 18% (29 requests) were made to Youtube.com and 9% (14 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain Fealac.org.
Page size can be reduced by 630.7 kB (39%)
1.6 MB
969.1 kB
In fact, the total size of Fealac.org main page is 1.6 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. Only a small number of websites need less resources to load. Javascripts take 784.5 kB which makes up the majority of the site volume.
Potential reduce by 117.8 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 18.7 kB, which is 13% 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 117.8 kB or 82% of the original size.
Potential reduce by 5.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. FEALAC images are well optimized though.
Potential reduce by 339.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 339.7 kB or 43% of the original size.
Potential reduce by 168.0 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. Fealac.org needs all CSS files to be minified and compressed as it can save up to 168.0 kB or 51% of the original size.
Number of requests can be reduced by 35 (30%)
118
83
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FEALAC. 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 from 7 to 1 for CSS and as a result speed up the page load time.
fealac.org
611 ms
index.do
1785 ms
css
35 ms
css
54 ms
css
58 ms
common.css
1126 ms
global.css
1513 ms
jquery.min.js
2173 ms
global.js
999 ms
main-bg.png
1256 ms
screen-plus.gif
190 ms
screen-ori.gif
208 ms
screen-minus.gif
209 ms
filedown.do
1045 ms
filedown.do
1464 ms
filedown.do
1988 ms
filedown.do
1396 ms
filedown.do
1256 ms
filedown.do
2195 ms
filedown.do
1985 ms
filedown.do
1464 ms
filedown.do
2396 ms
filedown.do
1988 ms
filedown.do
2194 ms
filedown.do
2600 ms
filedown.do
3057 ms
filedown.do
2494 ms
filedown.do
2959 ms
filedown.do
2394 ms
filedown.do
3794 ms
filedown.do
4402 ms
flag-australia.png
2600 ms
flag-brunei.png
2802 ms
flag-cambodia.png
2802 ms
flag-china.png
2957 ms
flag-indonesia.png
3055 ms
flag-japan.png
3156 ms
flag-korea.png
3157 ms
flag-lao.png
3158 ms
flag-malaysia.png
3249 ms
flag-mongolia.png
3304 ms
flag-myanmar.png
3330 ms
flag-newzealand.png
3340 ms
flag-philippines.png
3371 ms
flag-singapore.png
3478 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
23 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
45 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
68 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
70 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
70 ms
sdk.js
64 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
10 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
60 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
59 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
60 ms
0khV2ZdJOAs
28 ms
65RLe1bxn_M
27 ms
GHIBJXZwyNM
27 ms
7YhR2_FufYg
26 ms
V2KphMYt4Uw
25 ms
DfqIlBvcsVU
26 ms
M6mEwEpI7J0
25 ms
0khV2ZdJOAs
134 ms
65RLe1bxn_M
152 ms
GHIBJXZwyNM
163 ms
7YhR2_FufYg
159 ms
V2KphMYt4Uw
149 ms
DfqIlBvcsVU
157 ms
M6mEwEpI7J0
469 ms
sdk.js
24 ms
145 ms
DroidSerif-Regular.woff
3540 ms
DroidSerif-Bold.woff
3513 ms
axicon.woff
3935 ms
www-player.css
39 ms
www-embed-player.js
32 ms
base.js
169 ms
www-player.css
87 ms
www-embed-player.js
116 ms
base.js
323 ms
ad_status.js
753 ms
aDz_T_gaBrysQcZbaYaX8h92PYnkBHHJotKz2yKPZZ4.js
475 ms
embed.js
278 ms
main_ajax.do
3252 ms
embed.js
70 ms
flag-thailand.png
2649 ms
id
137 ms
flag-viet.png
2666 ms
flag-argentina.png
2531 ms
flag-bolivia.png
2680 ms
Create
535 ms
Create
538 ms
Create
608 ms
Create
605 ms
Create
540 ms
flag-brazil.png
2680 ms
Create
710 ms
Create
645 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
390 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
389 ms
flag-chile.png
2211 ms
flag-colombia.png
2290 ms
flag-costarica.png
2324 ms
flag-cuba.png
2140 ms
flag-dominicanrepublic.png
2082 ms
flag-ecuador.png
2070 ms
flag-elsalvador.png
2016 ms
flag-guatemala.png
1929 ms
flag-honduras.png
1926 ms
GenerateIT
349 ms
GenerateIT
351 ms
flag-mexico.png
1878 ms
GenerateIT
253 ms
flag-nicaragua.png
1798 ms
GenerateIT
200 ms
flag-panama.png
1695 ms
flag-paraguay.png
1747 ms
GenerateIT
197 ms
flag-peru.png
1662 ms
flag-suriname.png
1663 ms
GenerateIT
134 ms
flag-uruguay.png
1624 ms
flag-venezuela.png
1641 ms
logo_2024.png
1680 ms
GenerateIT
51 ms
25_logo1.png
1651 ms
head-search.png
1621 ms
head-sns.gif
1607 ms
head-login.png
1647 ms
log-edge.png
1655 ms
nav-mem.png
1655 ms
ico-quick-onoff.png
1605 ms
log_event
32 ms
log_event
28 ms
board-more.gif
1371 ms
two-bg.png
1359 ms
thr-bg.gif
1380 ms
thr-edge.gif
1291 ms
fou-bg.png
1477 ms
ico-fou1.png
1294 ms
ico-fou2.png
1149 ms
ico-fou3.png
1153 ms
ico-fou4.png
1212 ms
fiv-sns1.png
1184 ms
ico-down-bot.png
1198 ms
gotop.png
1176 ms
ico-foot1.png
1157 ms
sel-arr.gif
1257 ms
ico-foot2.png
1231 ms
ico-foot3.png
1203 ms
vis-prev.png
1203 ms
vis-next.png
1176 ms
thr-prev.gif
1158 ms
thr-next.gif
1243 ms
log_event
40 ms
log_event
30 ms
log_event
21 ms
log_event
22 ms
log_event
16 ms
fealac.org 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-hidden="true"] elements contain focusable descendents
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
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
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.
fealac.org 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
fealac.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fealac.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Fealac.org 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.
fealac.org
Open Graph data is detected on the main page of FEALAC. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: