Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

eeaa.gov.eg

وزارة البيئة | الرئيسية

Page Load Speed

23.4 sec in total

First Response

351 ms

Resources Loaded

22.1 sec

Page Rendered

921 ms

eeaa.gov.eg screenshot

About Website

Click here to check amazing Eeaa content for Egypt. Otherwise, check out these important facts you probably never knew about eeaa.gov.eg

تقدم وزارة البيئة عدد من الخدمات للمواطنين والمستثمرين أخر الاخبار متابعة أحدث أخبار الوزارة مشاهدة المزيد من المشروعات تقوم الوزارة بتنفيذ عدد من المشروعات بالتعاون مع شركاء التنمية مشروع الإبلاغ الو...

Visit eeaa.gov.eg

Key Findings

We analyzed Eeaa.gov.eg page load time and found that the first response time was 351 ms and then it took 23 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

eeaa.gov.eg performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value35.1 s

0/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value1.012

2/100

15%

TTI (Time to Interactive)

Value20.9 s

2/100

10%

Network Requests Diagram

eeaa.gov.eg

351 ms

eeaa.gov.eg

966 ms

css2

35 ms

font-awesome-all.css

806 ms

flaticon.css

688 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 84% of them (61 requests) were addressed to the original Eeaa.gov.eg, 10% (7 requests) were made to Gstatic.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (19.7 sec) belongs to the original domain Eeaa.gov.eg.

Page Optimization Overview & Recommendations

Page size can be reduced by 139.3 kB (27%)

Content Size

507.3 kB

After Optimization

368.1 kB

In fact, the total size of Eeaa.gov.eg main page is 507.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Javascripts take 357.1 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 134.7 kB

  • Original 146.6 kB
  • After minification 61.6 kB
  • After compression 11.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 85.0 kB, which is 58% 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 134.7 kB or 92% of the original size.

JavaScript Optimization

-1%

Potential reduce by 2.7 kB

  • Original 357.1 kB
  • After minification 357.1 kB
  • After compression 354.4 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. This website has mostly compressed JavaScripts.

CSS Optimization

-50%

Potential reduce by 1.9 kB

  • Original 3.7 kB
  • After minification 3.7 kB
  • After compression 1.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. Eeaa.gov.eg needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 50% of the original size.

Requests Breakdown

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

Requests Now

65

After Optimization

28

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eeaa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

eeaa.gov.eg accessibility score

79

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

eeaa.gov.eg best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

eeaa.gov.eg SEO score

77

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

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 Eeaa.gov.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 Eeaa.gov.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 Eeaa. 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: