21.6 sec in total
3.6 sec
17 sec
1.1 sec
Visit fact.org.kh now to see the best up-to-date Fact content and also check out these interesting facts you probably never knew about fact.org.kh
Visit fact.org.khWe analyzed Fact.org.kh page load time and found that the first response time was 3.6 sec and then it took 18.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
fact.org.kh performance score
name
value
score
weighting
Value10.0 s
0/100
10%
Value78.1 s
0/100
25%
Value19.3 s
0/100
10%
Value1,660 ms
11/100
30%
Value1.352
0/100
15%
Value40.5 s
0/100
10%
3558 ms
160 ms
269 ms
156 ms
117 ms
Our browser made a total of 226 requests to load all elements on the main page. We found that 65% of them (147 requests) were addressed to the original Fact.org.kh, 10% (23 requests) were made to Cdn01.boxcdn.net and 9% (20 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (10 sec) belongs to the original domain Fact.org.kh.
Page size can be reduced by 2.3 MB (45%)
5.2 MB
2.9 MB
In fact, the total size of Fact.org.kh main page is 5.2 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. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 102.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. This page needs HTML code to be minified as it can gain 13.4 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 102.9 kB or 86% of the original size.
Potential reduce by 139.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. Fact images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 69% of the original size.
Potential reduce by 938.8 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. Fact.org.kh needs all CSS files to be minified and compressed as it can save up to 938.8 kB or 84% of the original size.
Number of requests can be reduced by 108 (49%)
219
111
The browser has sent 219 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fact. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
fact.org.kh
3558 ms
k2.css
160 ms
bootstrap.css
269 ms
bootstrap-responsive.css
156 ms
template.responsive.css
117 ms
general.css
115 ms
template.css
560 ms
typo.css
206 ms
menu.css
766 ms
default.css
242 ms
css3.css
780 ms
colors_box.css
290 ms
scolors1.css
332 ms
shortcodes.css
1459 ms
zt_visitor_counter.css
1127 ms
default.css
1126 ms
default.css
1270 ms
animate.css
1188 ms
onebyone.css
1166 ms
responsive.css
1427 ms
style.css
1972 ms
mod_jflanguageselection.css
1992 ms
mootools-core.js
1393 ms
core.js
1319 ms
jquery.min.js
32 ms
k2.js
1828 ms
caption.js
1435 ms
mootools-more.js
2709 ms
jquery.min.js
2391 ms
bootstrap.js
2340 ms
jquery.cookies.2.2.0.js
2890 ms
zo2-uncompressed.js
2949 ms
shortcodes.js
3052 ms
crawler.js
2901 ms
jquery-1.7.1.min.js
3002 ms
jquery.onebyone.js
2951 ms
jquery.touchwipe.js
2998 ms
mc-validate.js
22 ms
sp_highlighter.js
3005 ms
mod_horizontal_scrolling_slideshow.js
3102 ms
mod_horizontal_carousel_image_slideshow.js
3040 ms
css
24 ms
header-tr.png
427 ms
header-tl.png
235 ms
logo.png
426 ms
en.gif
236 ms
km.gif
240 ms
input.png
235 ms
button.png
427 ms
mainhome-br.png
428 ms
mainhome-bl.png
426 ms
main-li.gif
427 ms
home.png
443 ms
a-haschild.png
658 ms
search-bg.png
495 ms
search-button.png
495 ms
timthumb.php
4422 ms
timthumb.php
6231 ms
timthumb.php
6291 ms
timthumb.php
4445 ms
timthumb.php
1141 ms
timthumb.php
1092 ms
timthumb.php
1994 ms
timthumb.php
3810 ms
timthumb.php
2901 ms
voacambodia-donsahong-dam.jpg
2979 ms
Peace%20Walk%20against%20DSH%20Dam_1.jpg
3097 ms
news.gif
3266 ms
CEPF(1).jpg
3306 ms
EU-SFiN-NGO.png
3364 ms
MAC.png
3406 ms
daimler.jpg
3466 ms
forum-syd.jpg
3759 ms
iucn.png
3798 ms
marsf.png
3855 ms
mff.jpg
3967 ms
aLNpdAUDq2MZbWz2U1a16g.ttf
12 ms
oxfamautralia.jpg
4092 ms
hvcb8py85cdoqyzej4bz
933 ms
watch
169 ms
placeholder.gif
3945 ms
ms
133 ms
embed
439 ms
Target-Area2016.png
10031 ms
webmail_icon_1.png
4171 ms
www-embed-player-vflfNyN_r.css
19 ms
www-embed-player.js
39 ms
base.js
60 ms
style2.png
4275 ms
body-cr.png
4281 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
45 ms
ad_status.js
52 ms
body-cl.png
4085 ms
body-tr.png
4120 ms
body-tl.png
4304 ms
default-br.gif
4547 ms
default-bl.gif
4545 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
61 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
61 ms
blank-tr.gif
4337 ms
blank-tl.gif
4355 ms
loading.gif
4604 ms
default-tr.gif
4513 ms
default-tl.gif
4353 ms
rs=ABjfnFW3NcDEAUOJhqBLkb_g7tp8huHPRg
49 ms
css
97 ms
js
127 ms
rs=ABjfnFVwLee7ilRNodS4pidryBsEUbxoyw
95 ms
rs=ABjfnFVwLee7ilRNodS4pidryBsEUbxoyw
52 ms
common.js
50 ms
map.js
71 ms
overlay.js
70 ms
22-blue-dot.png&filter=ff&scale=1.0
155 ms
util.js
62 ms
marker.js
121 ms
geocoder.js
114 ms
controls.js
113 ms
places_impl.js
113 ms
selection_2x-000.png
44 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
44 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
95 ms
gen204
104 ms
section_application_files-W41qNj.css
201 ms
section_templ_box_embed_widget-8-KkoB.css
169 ms
section_collab_sharing-gKr_wC.css
167 ms
theme_default_n0BI1hdbd2d5.css
153 ms
Intl.min-OVBm4h.js
182 ms
en-US-lpqaxA.js
183 ms
section_application_static.min-U1nhVk.js
271 ms
section_application_p1.min-ch0mxv.js
350 ms
section_application_postload.min-t38s02.js
184 ms
section_templ_box_embed_widget-l8epW8.js
269 ms
section_templ_partials_embed_widget_embed_widget_shared_folder_view-aK8HDb.js
268 ms
onion.js
76 ms
openhand_8_8.cur
205 ms
ViewportInfoService.GetViewportInfo
68 ms
stats.js
66 ms
transparent.png
234 ms
mapcnt6.png
323 ms
tmapctrl4.png
318 ms
tab-li.gif
3957 ms
vt
186 ms
vt
185 ms
vt
105 ms
vt
105 ms
vt
104 ms
color-br.gif
3925 ms
nav_main_bg-ZqdTJn.png
219 ms
logo-QjuuRH.png
216 ms
nav_main_bg_right-1MOi9t.png
214 ms
sprite_24x24_gears_white-9MY5cb.png
216 ms
animated_cloud_dots-DIJFMv.gif
212 ms
sub_nav_bottom_gradient_1x3-9urlGO.png
215 ms
crawler-__jQMT.gif
216 ms
viewer-icons001.png
552 ms
22-blue-dot.png&scale=1.0
533 ms
AuthenticationService.Authenticate
630 ms
MyMaps_Icons003.png
489 ms
mymaps_32.png
628 ms
v1_4593b7d7.png
630 ms
google-my-maps-logo-small-001.png
629 ms
files-F9w7J8.png
377 ms
sprite-Zoybrn.png
151 ms
color-bl.gif
3161 ms
kh
162 ms
section_files_postload-FKSNYo.css
6 ms
24x24-rx9450.png
55 ms
doc_32-FeftMn.png
55 ms
doc_40-q7Y1mu.png
56 ms
color-tr.gif
2258 ms
color-tl.gif
2176 ms
sing_14.jpg
2108 ms
sing_21.jpg
1952 ms
sing23.jpg
1901 ms
sing_24.jpg
1881 ms
sing_17.jpg
1861 ms
sing_19.jpg
1799 ms
sing_26.jpg
1521 ms
sing_29.jpg
2238 ms
sing_28.jpg
2226 ms
sing_18.jpg
2163 ms
sing_10.jpg
2144 ms
sing_32.jpg
2050 ms
sing_16.jpg
1976 ms
sing_20.jpg
1775 ms
sing_27.jpg
1746 ms
sing_23.jpg
1747 ms
sing_15.jpg
1733 ms
img9.jpg
1862 ms
img6.jpg
1752 ms
img5.jpg
1742 ms
img7.jpg
1644 ms
img10.jpg
1564 ms
img4.jpg
1558 ms
img8.jpg
1688 ms
Img1.jpg
1730 ms
img3.jpg
1401 ms
img2.jpg
1697 ms
default.gif
1378 ms
default.png
1400 ms
other.png
1381 ms
chrome.png
1362 ms
firefox.png
1360 ms
msie.png
1397 ms
opera.png
1373 ms
button-big.png
1401 ms
body-br.png
1398 ms
body-bl.png
1400 ms
footer-br.gif
1385 ms
footer-bl.gif
1418 ms
footer-tr.gif
1412 ms
footer-tl.gif
680 ms
footer-line.gif
690 ms
footer-li.gif
691 ms
box-br.png
651 ms
box-bl.png
649 ms
box-tr.png
609 ms
box-tl.png
597 ms
social-icons.png
604 ms
meta100.png
880 ms
transparent.png
550 ms
circlebutton.png
588 ms
prev.png
564 ms
next.png
548 ms
QuotaService.RecordEvent
15 ms
QuotaService.RecordEvent
15 ms
fact.org.kh 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
ARIA input fields do not have accessible names
ARIA toggle fields do not have accessible names
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
fact.org.kh 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
Image elements do not have [alt] attributes
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 Fact.org.kh 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 Fact.org.kh 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.
fact.org.kh
Open Graph description is not detected on the main page of Fact. 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: