Tools & Wizards About Us
mls.eg screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

mls.eg

Page Load Speed

2.9 sec in total

First Response

211 ms

Resources Loaded

2.4 sec

Page Rendered

320 ms

mls.eg screenshot

About Website

Visit mls.eg now to see the best up-to-date Mls content for Egypt and also check out these interesting facts you probably never knew about mls.eg

Visit mls.eg

Key Findings

We analyzed Mls.eg page load time and found that the first response time was 211 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

mls.eg performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

43/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

mls.eg

211 ms

mls.eg

536 ms

en.css

208 ms

jquery.min.js

23 ms

function.js

432 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 52% of them (26 requests) were addressed to the original Mls.eg, 44% (22 requests) were made to 4image.net and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (775 ms) relates to the external source 4image.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 238.8 kB (77%)

Content Size

308.5 kB

After Optimization

69.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mls.eg main page is 308.5 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. 35% of websites need less resources to load. HTML takes 174.3 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 155.7 kB

  • Original 174.3 kB
  • After minification 167.4 kB
  • After compression 18.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. 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 155.7 kB or 89% of the original size.

Image Optimization

-15%

Potential reduce by 604 B

  • Original 3.9 kB
  • After minification 3.3 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, Mls needs image optimization as it can save up to 604 B or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 33.4 kB
  • After minification 33.4 kB
  • After compression 33.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

-85%

Potential reduce by 82.5 kB

  • Original 96.8 kB
  • After minification 89.9 kB
  • After compression 14.3 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. Mls.eg needs all CSS files to be minified and compressed as it can save up to 82.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (38%)

Requests Now

47

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mls.eg

mls.eg

211 ms

mls.eg

mls.eg

536 ms

en.css

en.css

208 ms

jquery.min.js

jquery.min.js

23 ms

function.js

function.js

432 ms

js

js

69 ms

autocomplete.css

autocomplete.css

557 ms

autocomplete.js

autocomplete.js

562 ms

autocomplete-multi.js

autocomplete-multi.js

462 ms

location.js

location.js

770 ms

ajax.js

ajax.js

474 ms

fancybox.js

fancybox.js

637 ms

fancybox.css

fancybox.css

566 ms

logo.svg

logo.svg

103 ms

600x400-adc4cb6b480672519f7f39c9975176e6.webp

600x400-adc4cb6b480672519f7f39c9975176e6.webp

506 ms

map.svg

map.svg

143 ms

search.png

search.png

247 ms

call.png

call.png

329 ms

search-bg.jpg

search-bg.jpg

331 ms

find.png

find.png

320 ms

left.svg

left.svg

334 ms

right.svg

right.svg

349 ms

phone.png

phone.png

429 ms

bed.svg

bed.svg

432 ms

bath.svg

bath.svg

434 ms

area.svg

area.svg

444 ms

floor.svg

floor.svg

454 ms

whatsapp.png

whatsapp.png

533 ms

building.svg

building.svg

534 ms

600x400-4c71b20d09ea2f9540563985e4e27004.webp

600x400-4c71b20d09ea2f9540563985e4e27004.webp

398 ms

600x400-4160a66984f4e7f8847453c4460357a2.webp

600x400-4160a66984f4e7f8847453c4460357a2.webp

398 ms

600x400-5d2df3dcb814c37c73ec89048d0280e0.webp

600x400-5d2df3dcb814c37c73ec89048d0280e0.webp

498 ms

600x400-1a0a0dc416acc2094829e1d47beceac4.webp

600x400-1a0a0dc416acc2094829e1d47beceac4.webp

499 ms

600x400-c2753bcc768d17466b7321ea15f958b8.webp

600x400-c2753bcc768d17466b7321ea15f958b8.webp

500 ms

600x400-434a9d9e637f2218142c4dbfe9ecc7ef.webp

600x400-434a9d9e637f2218142c4dbfe9ecc7ef.webp

489 ms

600x400-9545693a16888c11e5fa3fad99af6a65.webp

600x400-9545693a16888c11e5fa3fad99af6a65.webp

580 ms

600x400-454fdb18a31c951a0865966ad5078785.webp

600x400-454fdb18a31c951a0865966ad5078785.webp

549 ms

600x400-c6b175d3bdab9cf83f7baf2f1dd328d4.webp

600x400-c6b175d3bdab9cf83f7baf2f1dd328d4.webp

581 ms

600x400-6b62306829ad3addf706cc32891afdf3.webp

600x400-6b62306829ad3addf706cc32891afdf3.webp

590 ms

600x400-74629309c814befbd04515f880119dc9.webp

600x400-74629309c814befbd04515f880119dc9.webp

592 ms

600x400-7664360fb81feca916cfc075876d3314.webp

600x400-7664360fb81feca916cfc075876d3314.webp

683 ms

600x400-9e1d46b5a9cc80b7d0c8b1ff61948c06.webp

600x400-9e1d46b5a9cc80b7d0c8b1ff61948c06.webp

640 ms

600x400-00888a994fae38e23df8cc16579386f3.webp

600x400-00888a994fae38e23df8cc16579386f3.webp

673 ms

600x400-c69ab7157b9ec8115f4f160155a800c1.webp

600x400-c69ab7157b9ec8115f4f160155a800c1.webp

672 ms

600x400-680c093c3de27c73c4dcf360d0f9e936.webp

600x400-680c093c3de27c73c4dcf360d0f9e936.webp

682 ms

600x400-f6716420bf0d422bfa059a51646fbf35.webp

600x400-f6716420bf0d422bfa059a51646fbf35.webp

683 ms

600x400-00690bdb8aa73a61f3cc3c26594dc67e.webp

600x400-00690bdb8aa73a61f3cc3c26594dc67e.webp

732 ms

600x400-19f6d612cb37d94b17d45bf11091f7c6.webp

600x400-19f6d612cb37d94b17d45bf11091f7c6.webp

765 ms

600x400-82a3f74fabb8b3dcad7323e0474277dd.webp

600x400-82a3f74fabb8b3dcad7323e0474277dd.webp

764 ms

600x400-4644a99e2f98e0d520531333db163026.webp

600x400-4644a99e2f98e0d520531333db163026.webp

775 ms

Accessibility Review

mls.eg accessibility score

72

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

Document doesn't have a <title> element

High

Form elements do not have associated labels

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

mls.eg SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mls.eg can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Mls.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

mls.eg

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