14.9 sec in total
5.1 sec
9.5 sec
257 ms
Click here to check amazing STDF content for Egypt. Otherwise, check out these important facts you probably never knew about stdf.org.eg
STDF | Science and Technology Development Fund.
Visit stdf.org.egWe analyzed Stdf.org.eg page load time and found that the first response time was 5.1 sec and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
stdf.org.eg performance score
name
value
score
weighting
Value17.0 s
0/100
10%
Value94.5 s
0/100
25%
Value42.7 s
0/100
10%
Value3,890 ms
1/100
30%
Value0.16
73/100
15%
Value49.8 s
0/100
10%
5141 ms
312 ms
281 ms
310 ms
313 ms
Our browser made a total of 155 requests to load all elements on the main page. We found that 65% of them (100 requests) were addressed to the original Stdf.org.eg, 13% (20 requests) were made to Maps.googleapis.com and 6% (9 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Stdf.org.eg.
Page size can be reduced by 1.1 MB (43%)
2.6 MB
1.5 MB
In fact, the total size of Stdf.org.eg main page is 2.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. 70% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 100.5 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 21.4 kB, which is 18% 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 100.5 kB or 86% of the original size.
Potential reduce by 116.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. STDF images are well optimized though.
Potential reduce by 915.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 915.7 kB or 69% of the original size.
Number of requests can be reduced by 85 (57%)
148
63
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of STDF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
stdf.org.eg
5141 ms
jcemediabox.css
312 ms
style.css
281 ms
system.css
310 ms
general.css
313 ms
base.css
449 ms
template.css
700 ms
typography.css
594 ms
megamenu.css
453 ms
blue-arrows.css
551 ms
style2.css
590 ms
style.css
593 ms
settings.css
741 ms
captions.css
691 ms
style.css
735 ms
general.css
734 ms
mootools-core.js
1071 ms
core.js
774 ms
caption.js
773 ms
jcemediabox.js
1115 ms
mootools-more.js
1498 ms
yt-script.js
752 ms
showbox.js
894 ms
jquery-1.5.min.js
1201 ms
jsmart.noconflict.js
912 ms
megalib.js
1178 ms
newscalendar.js
1052 ms
jsmart_extraslider.js
1197 ms
jquery.min.js
26 ms
jquery.themepunch.plugins.min.js
1214 ms
jquery.themepunch.revolution.min.js
1400 ms
stickytooltip.js
1322 ms
slider.js
1341 ms
audio-player.js
1345 ms
modernizr.js
1359 ms
srizonjq1.8.min.js
2037 ms
srizontb.css
1340 ms
mag-popup.css
1318 ms
elastislide.css
1330 ms
style.css
1367 ms
system.css
1353 ms
srizonjq.easing.1.3.min.js
1318 ms
srizontb2.js
1329 ms
menustyle.css
1333 ms
jshover.css
1269 ms
megamenu-components.css
1314 ms
mag-popup.js
1390 ms
elastislide.js
1391 ms
jusertubeslider.js
1293 ms
head.png
561 ms
logo.png
145 ms
menu-bg.gif
147 ms
home.png
149 ms
menuwrap-li1.gif
148 ms
menuwrap-sub-bg.png
146 ms
tick.png
361 ms
ext_mod.png
360 ms
ext_com.png
362 ms
menuwrap-li-sub-bg.gif
361 ms
medo111.jpg
569 ms
login.png
427 ms
s1.png
427 ms
check.png
430 ms
publications.jpg
570 ms
s7.jpg
1300 ms
bf6fdc404adb8f05e5e7f0ed4ed7c43f.jpeg
980 ms
1bbc8c3da058fd7ac9c4a62a48cbca22.jpeg
928 ms
PROF_MAHMOUD_ZAWRAH2.jpg
977 ms
e3a.jpg
928 ms
attention.gif
928 ms
TheCFC%20BuildingConstructionSystem.jpg
1183 ms
change.jpg
1184 ms
Code%20_f_Ethics.jpg
1184 ms
open111.jpg
2544 ms
nnn2.JPG
1409 ms
opacity.png
1300 ms
next-so-article-t6.png
1279 ms
pre-so-article-t6.png
1279 ms
_menu-l1.png
1390 ms
style2.png
1408 ms
ms
204 ms
imageNavLeft.png
1385 ms
imageNavRight.png
1384 ms
cir_blu_v2.png
1570 ms
cir_v2.png
1569 ms
bullet.gif
1576 ms
popup.html
1490 ms
tooltip.html
1486 ms
arrows-blue.png
1547 ms
back-totop.png
1552 ms
li-sitemap.gif
1627 ms
embed
765 ms
widget_v2.134.js
8 ms
das-line-bg.gif
1416 ms
icon_computer_hover.png
1415 ms
icon_mobile.png
1473 ms
g30.png
1610 ms
timer.png
1491 ms
loader.gif
1488 ms
shadow2.png
1488 ms
zoom-link.gif
1417 ms
loadingAnimation.gif
1490 ms
avatar_simple_visitor.png
63 ms
aL63HcygAAVYuCCsAAA==
1 ms
rs=ABjfnFW3mr6czvuPoW8a89_7fltBLUcjKA
23 ms
css
62 ms
js
91 ms
rs=ABjfnFWmvH_XHjXPlHaKulkC-8Yn_1W7WQ
40 ms
rs=ABjfnFWmvH_XHjXPlHaKulkC-8Yn_1W7WQ
39 ms
common.js
32 ms
map.js
50 ms
overlay.js
96 ms
22-blue-dot.png&filter=ff&scale=1.0
134 ms
util.js
102 ms
marker.js
90 ms
geocoder.js
91 ms
controls.js
84 ms
places_impl.js
129 ms
selection_2x-000.png
16 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
126 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
130 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
205 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
205 ms
gen204
75 ms
onion.js
79 ms
openhand_8_8.cur
172 ms
ViewportInfoService.GetViewportInfo
137 ms
stats.js
61 ms
kh
197 ms
kh
198 ms
kh
259 ms
kh
260 ms
kh
257 ms
kh
260 ms
transparent.png
161 ms
large_left.png
690 ms
large_right.png
689 ms
mapcnt6.png
52 ms
tmapctrl4.png
42 ms
vt
79 ms
vt
66 ms
vt
63 ms
vt
82 ms
vt
64 ms
vt
74 ms
vt
122 ms
viewer-icons001.png
83 ms
star4.png
88 ms
22-blue-dot.png&scale=1.0
74 ms
gen204
89 ms
AuthenticationService.Authenticate
48 ms
MyMaps_Icons003.png
26 ms
mymaps_32.png
28 ms
v1_4593b7d7.png
29 ms
google-my-maps-logo-small-001.png
27 ms
stdf.org.eg 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
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
stdf.org.eg 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
Missing source maps for large first-party JavaScript
stdf.org.eg SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
AR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stdf.org.eg can be misinterpreted by Google and other search engines. Our service has detected that Arabic is used on the page, and it does not match the claimed English language. Our system also found out that Stdf.org.eg 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.
stdf.org.eg
Open Graph description is not detected on the main page of STDF. 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: