4.3 sec in total
202 ms
3.6 sec
451 ms
Click here to check amazing Egatha content for Saudi Arabia. Otherwise, check out these important facts you probably never knew about egatha.org
موقع هيئة الإغاثة الإسلامية العالمية
Visit egatha.orgWe analyzed Egatha.org page load time and found that the first response time was 202 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
egatha.org performance score
202 ms
658 ms
667 ms
11 ms
26 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 85% of them (76 requests) were addressed to the original Egatha.org, 4% (4 requests) were made to S.swiftypecdn.com and 2% (2 requests) were made to Cdn.viglink.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Themwl.org.
Page size can be reduced by 506.6 kB (40%)
1.3 MB
763.3 kB
In fact, the total size of Egatha.org main page is 1.3 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. 55% of websites need less resources to load. Images take 584.7 kB which makes up the majority of the site volume.
Potential reduce by 55.0 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.0 kB or 83% of the original size.
Potential reduce by 26.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. Egatha images are well optimized though.
Potential reduce by 345.2 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 345.2 kB or 67% of the original size.
Potential reduce by 79.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. Egatha.org needs all CSS files to be minified and compressed as it can save up to 79.9 kB or 75% of the original size.
Number of requests can be reduced by 43 (51%)
84
41
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Egatha. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
egatha.org
202 ms
portal
658 ms
667 ms
cloudflare.min.js
11 ms
jcemediabox.css
26 ms
style.css
240 ms
htmlmap.css
74 ms
nivo-slider.css
162 ms
default.css
218 ms
slimbox.css
150 ms
mootools.js
25 ms
caption.js
33 ms
jcemediabox.js
66 ms
jquery.min.js
98 ms
jquery.nivo.slider.min.js
73 ms
slimbox_moo11.js
75 ms
system.css
78 ms
general.css
80 ms
template.css
84 ms
jquery.js
87 ms
script.js
94 ms
bag2
234 ms
093t-kFvZ-s
130 ms
GetPicture.aspx
1635 ms
footer_menu_01.png
35 ms
Bottom_texture.jpg
118 ms
page_gl.png
125 ms
sheet_s.png
124 ms
sheet_h.png
119 ms
sheet_v.png
139 ms
header.jpg
76 ms
nav.png
208 ms
top_menu_01.png
131 ms
loading.gif
342 ms
slide01_inauguration_yemen_project.jpg
127 ms
slide_2nd_intl_forum_for_humanitarian_work.jpg
128 ms
slide_ga_2015.jpg
134 ms
slide_unhcr_iiro_training.jpg
134 ms
leaflet_eidgift_1436.jpg
137 ms
leaflet_eyeoperation_1436.jpg
138 ms
leaflet_hajifood_1436.jpg
138 ms
leaflet_heartoperation_1436.jpg
138 ms
leaflet_quran_teaching_1436.jpg
147 ms
leaflet_schoolbag_1436.jpg
147 ms
leaflet_widow.jpg
141 ms
pdf_button.png
146 ms
printButton.png
145 ms
emailButton.png
147 ms
postcategoryicon.png
145 ms
twitter.png
146 ms
youtube.png
149 ms
facebook.png
146 ms
flickr.png
252 ms
google.png
145 ms
instagram.png
145 ms
ad_tender.jpg
149 ms
btn_iirosa_webmail.jpg
148 ms
btn_volunteer_02.jpg
162 ms
btn_consular_meeting.jpg
135 ms
ad_thankyou_letters.jpg
133 ms
piwik.js
225 ms
embed.js
86 ms
footer_menu_03.png
266 ms
bag2
380 ms
btn_awqaf2012.jpg
226 ms
post_s.png
278 ms
post_h.png
406 ms
post_v.png
402 ms
blockheader.png
402 ms
blockcontent_s.png
271 ms
blockcontent_h.png
413 ms
blockcontent_v.png
416 ms
blockcontent_c.png
486 ms
blockcontentbullets.png
510 ms
button.png
511 ms
postbullets.png
510 ms
swiftype_nocode-d8273559be65c04593eb2a85dc0df637.js
45 ms
swiftype_nocode-bcc8d1c39f18a7802a7ee2c6f76577f3.css
25 ms
popup.html
378 ms
tooltip.html
380 ms
overlay_bg-641ab15b9fe7cd9faabf12d0415c92d2.png
15 ms
cc.js
9 ms
cc
72 ms
pixel.gif
28 ms
pixel.gif
24 ms
ping
31 ms
domains
43 ms
arrows.png
122 ms
bullets.png
158 ms
egatha.org SEO score
N/A
AR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Egatha.org 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), while the claimed language is Arabic. Our system also found out that Egatha.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.
egatha.org
Open Graph description is not detected on the main page of Egatha. 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: