Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

stdf.org.eg

STDF - Sience and Technology Development Fund

Page Load Speed

14.9 sec in total

First Response

5.1 sec

Resources Loaded

9.5 sec

Page Rendered

257 ms

stdf.org.eg screenshot

About Website

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.eg

Key Findings

We 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.

Performance Metrics

stdf.org.eg performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value17.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value94.5 s

0/100

25%

SI (Speed Index)

Value42.7 s

0/100

10%

TBT (Total Blocking Time)

Value3,890 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.16

73/100

15%

TTI (Time to Interactive)

Value49.8 s

0/100

10%

Network Requests Diagram

stdf.org.eg

5141 ms

jcemediabox.css

312 ms

style.css

281 ms

system.css

310 ms

general.css

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 Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (43%)

Content Size

2.6 MB

After Optimization

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.

HTML Optimization

-86%

Potential reduce by 100.5 kB

  • Original 116.9 kB
  • After minification 95.5 kB
  • After compression 16.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. 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.

Image Optimization

-10%

Potential reduce by 116.1 kB

  • Original 1.2 MB
  • After minification 1.1 MB

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.

JavaScript Optimization

-69%

Potential reduce by 915.7 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 405.6 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.

Requests Breakdown

Number of requests can be reduced by 85 (57%)

Requests Now

148

After Optimization

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.

Accessibility Review

stdf.org.eg accessibility score

66

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

stdf.org.eg best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

stdf.org.eg SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    AR

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: