Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

mapping.properties

Mapping Properties | Egypt First Real estate Interactive Map

Page Load Speed

3.5 sec in total

First Response

36 ms

Resources Loaded

2.6 sec

Page Rendered

818 ms

About Website

Welcome to mapping.properties homepage info - get ready to check Mapping best content right away, or after learning these important things about mapping.properties

Mapping.Properties is the first platform in Egypt that enables you to locate all Real estate developments and explore their context on an Interactive Map.

Visit mapping.properties

Key Findings

We analyzed Mapping.properties page load time and found that the first response time was 36 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

mapping.properties performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value810 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value25.8 s

0/100

10%

Network Requests Diagram

mapping.properties

36 ms

mapping.properties

558 ms

flick.css

38 ms

mapping.properties

389 ms

style.min.css

163 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 69% of them (73 requests) were addressed to the original Mapping.properties, 10% (11 requests) were made to C0.wp.com and 8% (8 requests) were made to I0.wp.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source I0.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 508.8 kB (12%)

Content Size

4.2 MB

After Optimization

3.7 MB

In fact, the total size of Mapping.properties main page is 4.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 74.6 kB

  • Original 94.2 kB
  • After minification 91.5 kB
  • After compression 19.5 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 74.6 kB or 79% of the original size.

Image Optimization

-13%

Potential reduce by 416.8 kB

  • Original 3.2 MB
  • After minification 2.8 MB

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, Mapping needs image optimization as it can save up to 416.8 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 7.6 kB

  • Original 707.0 kB
  • After minification 707.0 kB
  • After compression 699.5 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

-6%

Potential reduce by 9.7 kB

  • Original 168.0 kB
  • After minification 168.0 kB
  • After compression 158.2 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. Mapping.properties has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 88 (86%)

Requests Now

102

After Optimization

14

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

Accessibility Review

mapping.properties accessibility score

89

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

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.

Best Practices

mapping.properties 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

Page has valid source maps

SEO Factors

mapping.properties SEO score

83

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

High

robots.txt is not valid

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mapping.properties can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Mapping.properties 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 data is detected on the main page of Mapping. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: