3.4 sec in total
641 ms
2.3 sec
467 ms
Welcome to landmark.com.eg homepage info - get ready to check Landmark best content for Egypt right away, or after learning these important things about landmark.com.eg
Home - Real Estate in Egypt, Maadi Real Estate, RENT, BUY and SELL, Property Management, Real Estate Appraisal
Visit landmark.com.egWe analyzed Landmark.com.eg page load time and found that the first response time was 641 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
landmark.com.eg performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value7.5 s
4/100
25%
Value8.7 s
17/100
10%
Value50 ms
100/100
30%
Value0.06
98/100
15%
Value12.2 s
15/100
10%
641 ms
184 ms
451 ms
275 ms
738 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 96% of them (74 requests) were addressed to the original Landmark.com.eg, 4% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (882 ms) belongs to the original domain Landmark.com.eg.
Page size can be reduced by 65.2 kB (69%)
93.9 kB
28.7 kB
In fact, the total size of Landmark.com.eg main page is 93.9 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. 45% of websites need less resources to load. HTML takes 71.0 kB which makes up the majority of the site volume.
Potential reduce by 62.9 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 9.3 kB, which is 13% 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 62.9 kB or 89% of the original size.
Potential reduce by 0 B
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. Landmark images are well optimized though.
Potential reduce by 984 B
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 984 B or 26% of the original size.
Potential reduce by 1.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. Landmark.com.eg needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 29% of the original size.
Number of requests can be reduced by 24 (33%)
72
48
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Landmark. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
landmark.com.eg
641 ms
style.css
184 ms
bootstrap.min.css
451 ms
font-awesome.min.css
275 ms
jquery-1.11.1.js
738 ms
bootstrap.min.js
279 ms
superfish.js
272 ms
easyaspie.min.js
274 ms
main.css
365 ms
animate.css
542 ms
wow.min.js
366 ms
top.css
371 ms
top.js
460 ms
skdslider.js
460 ms
skdslider.css
465 ms
owl.carousel.css
538 ms
owl.theme.css
550 ms
owl.carousel.js
551 ms
default111.css
558 ms
component.css
631 ms
modernizr.custom.js
631 ms
toucheffects.js
640 ms
viewbox.css
644 ms
jquery.viewbox.min.js
651 ms
prettyPhoto.css
721 ms
jquery.prettyPhoto.js
721 ms
owl.carousel.css
731 ms
owl.theme.css
784 ms
addthis_widget.js
133 ms
logo.jpg
105 ms
l2.jpg
105 ms
l3.jpg
103 ms
l1.jpg
104 ms
icon-flag-ar.jpg
103 ms
a7.jpg
105 ms
1.jpg
185 ms
2.jpg
185 ms
3.jpg
185 ms
4.jpg
188 ms
5.jpg
188 ms
6.jpg
189 ms
7.jpg
275 ms
8.jpg
275 ms
9.jpg
275 ms
10.jpg
281 ms
11.jpg
282 ms
12.jpg
281 ms
13.jpg
366 ms
symbol-ob.jpg
366 ms
symbol-cp.jpg
367 ms
symbol-io.jpg
374 ms
symbol-lh.jpg
374 ms
lens-left.jpg
375 ms
search.jpg
457 ms
modern_flat_for_rent_in_maadi_1.jpg
635 ms
lg-share-en.gif
35 ms
8f6614e6-17df-40a5-96d5-3778441e3b6a.jpg
614 ms
callnow.jpg
441 ms
watermark.php
521 ms
details.jpg
444 ms
watermark.php
682 ms
watermark.php
662 ms
watermark.php
586 ms
watermark.php
702 ms
watermark.php
835 ms
watermark.php
739 ms
lg-share-en.gif
19 ms
watermark.php
692 ms
watermark.php
799 ms
watermark.php
758 ms
watermark.php
768 ms
watermark.php
805 ms
watermark.php
831 ms
watermark.php
882 ms
watermark.php
825 ms
watermark.php
815 ms
watermark.php
854 ms
landmark.com.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
Links do not have a discernible name
landmark.com.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
landmark.com.eg SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Landmark.com.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 Landmark.com.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.
landmark.com.eg
Open Graph description is not detected on the main page of Landmark. 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: