3.7 sec in total
1.5 sec
1.6 sec
543 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 1.5 sec and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
landmark.com.eg performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value9.1 s
1/100
25%
Value9.9 s
10/100
10%
Value100 ms
98/100
30%
Value0.06
98/100
15%
Value12.6 s
14/100
10%
1527 ms
50 ms
141 ms
70 ms
50 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 93% of them (52 requests) were addressed to the original Landmark.com.eg, 5% (3 requests) were made to S7.addthis.com and 2% (1 request) were made to M.addthis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Landmark.com.eg.
Page size can be reduced by 454.6 kB (22%)
2.1 MB
1.6 MB
In fact, the total size of Landmark.com.eg main page is 2.1 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. 30% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 77.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. 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 77.9 kB or 78% of the original size.
Potential reduce by 8.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. Landmark images are well optimized though.
Potential reduce by 359.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 359.2 kB or 70% of the original size.
Potential reduce by 8.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. Landmark.com.eg needs all CSS files to be minified and compressed as it can save up to 8.7 kB or 81% of the original size.
Number of requests can be reduced by 21 (38%)
55
34
The browser has sent 55 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 and as a result speed up the page load time.
landmark.com.eg
1527 ms
style.css
50 ms
jquery-1.4.2.js
141 ms
logo.jpg
70 ms
l2.jpg
50 ms
l3.jpg
52 ms
l1.jpg
56 ms
icon-flag-ar.jpg
56 ms
arrow.jpg
96 ms
1.jpg
146 ms
2.jpg
159 ms
3.jpg
134 ms
4.jpg
146 ms
5.jpg
175 ms
6.jpg
207 ms
7.jpg
222 ms
8.jpg
251 ms
9.jpg
227 ms
10.jpg
245 ms
11.jpg
277 ms
12.jpg
315 ms
13.jpg
329 ms
symbol-ob.jpg
303 ms
symbol-cp.jpg
301 ms
symbol-io.jpg
328 ms
symbol-lh.jpg
345 ms
lens-left.jpg
348 ms
search.jpg
362 ms
20140904_141906_resize.jpg
472 ms
bullet.jpg
375 ms
watermark.php
150 ms
details.jpg
25 ms
watermark.php
161 ms
watermark.php
172 ms
watermark.php
155 ms
watermark.php
237 ms
watermark.php
269 ms
watermark.php
278 ms
watermark.php
266 ms
watermark.php
281 ms
watermark.php
353 ms
watermark.php
401 ms
watermark.php
394 ms
watermark.php
362 ms
watermark.php
428 ms
watermark.php
477 ms
watermark.php
471 ms
watermark.php
524 ms
watermark.php
561 ms
watermark.php
557 ms
office_building_for_rent2(1).jpg
536 ms
callnow.jpg
57 ms
lg-share-en.gif
6 ms
addthis_widget.js
8 ms
300lo.json
36 ms
sh.7c7179124ea24ac6ba46caac.html
21 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: