Tools & Wizards About Us
nilex.egyptse.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

nilex.egyptse.com

NILEX - بورصة النيل

Page Load Speed

6.6 sec in total

First Response

524 ms

Resources Loaded

5.8 sec

Page Rendered

180 ms

nilex.egyptse.com screenshot

About Website

Welcome to nilex.egyptse.com homepage info - get ready to check NILEX Egyptse best content for Egypt right away, or after learning these important things about nilex.egyptse.com

Visit nilex.egyptse.com

Key Findings

We analyzed Nilex.egyptse.com page load time and found that the first response time was 524 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

nilex.egyptse.com performance score

0

Network Requests Diagram

nilex.egyptse.com

524 ms

2056 ms

Nilex.css

333 ms

jquery.min.js

75 ms

slides.min.jquery.js

320 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 96% of them (23 requests) were addressed to the original Nilex.egyptse.com, 4% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Nilex.egyptse.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.3 kB (31%)

Content Size

221.7 kB

After Optimization

153.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nilex.egyptse.com main page is 221.7 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. Only 10% of websites need less resources to load. Images take 131.1 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 35.5 kB

  • Original 42.1 kB
  • After minification 26.9 kB
  • After compression 6.6 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 15.2 kB, which is 36% 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 35.5 kB or 84% of the original size.

Image Optimization

-16%

Potential reduce by 21.3 kB

  • Original 131.1 kB
  • After minification 109.8 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. Obviously, NILEX Egyptse needs image optimization as it can save up to 21.3 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-12%

Potential reduce by 4.9 kB

  • Original 40.1 kB
  • After minification 39.4 kB
  • After compression 35.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 4.9 kB or 12% of the original size.

CSS Optimization

-79%

Potential reduce by 6.7 kB

  • Original 8.4 kB
  • After minification 5.6 kB
  • After compression 1.7 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. Nilex.egyptse.com needs all CSS files to be minified and compressed as it can save up to 6.7 kB or 79% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

13

After Optimization

13

  • Images
  • JavaScript
  • CSS

The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NILEX Egyptse. According to our analytics all requests are already optimized.

Network Requests Diagram

nilex.egyptse.com

nilex.egyptse.com

524 ms

2056 ms

Nilex.css

Nilex.css

333 ms

jquery.min.js

jquery.min.js

75 ms

slides.min.jquery.js

slides.min.jquery.js

320 ms

Header_a.jpg

Header_a.jpg

359 ms

MenuBar_Back.jpg

MenuBar_Back.jpg

192 ms

English_but.jpg

English_but.jpg

303 ms

NilexIndicesAr.jpg

NilexIndicesAr.jpg

539 ms

NewsletterAr.JPG

NewsletterAr.JPG

695 ms

PhoneBanner_Ar.jpg

PhoneBanner_Ar.jpg

890 ms

getImage.ashx

getImage.ashx

1026 ms

getImage.ashx

getImage.ashx

1253 ms

getImage.ashx

getImage.ashx

597 ms

getImage.ashx

getImage.ashx

1333 ms

getImage.ashx

getImage.ashx

1065 ms

getImage.ashx

getImage.ashx

2273 ms

getImage.ashx

getImage.ashx

1474 ms

getImage.ashx

getImage.ashx

3222 ms

getImage.ashx

getImage.ashx

1861 ms

bar.jpg

bar.jpg

1418 ms

Left_baner_Img.jpg

Left_baner_Img.jpg

1317 ms

TableHeader.jpg

TableHeader.jpg

1407 ms

pagination.png

pagination.png

1473 ms

SEO Factors

nilex.egyptse.com SEO score

0

Language and Encoding

  • Language Detected

    AR

  • Language Claimed

    AR

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nilex.egyptse.com can be misinterpreted by Google and other search engines. Our service has detected that Arabic is used on the page, and it matches the claimed language. Our system also found out that Nilex.egyptse.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

nilex.egyptse.com

Open Graph description is not detected on the main page of NILEX Egyptse. 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: