Tools & Wizards About Us
eazi.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 42

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 74

    SEO

    Google-friendlier than
    31% of websites

eazi.com

Eazi - Simply a Better Way to Sell Your Home. Buy or Sell Property Quickly, Securely and Cost Effectively

Page Load Speed

2.7 sec in total

First Response

289 ms

Resources Loaded

2.2 sec

Page Rendered

175 ms

eazi.com screenshot

About Website

Welcome to eazi.com homepage info - get ready to check Eazi best content for South Africa right away, or after learning these important things about eazi.com

The smarter way to sell property. Eazi sells properties for a flat fee from only R 33,000 all in - including advertising, showings, electronic offer management and much more!

Visit eazi.com

Key Findings

We analyzed Eazi.com page load time and found that the first response time was 289 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

eazi.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value5.4 s

57/100

10%

TBT (Total Blocking Time)

Value1,730 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value17.1 s

4/100

10%

Network Requests Diagram

www.eazi.com

289 ms

styles.css

72 ms

addons.css

143 ms

jquery-1.11.3.min.js

287 ms

all.js

207 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 21% of them (11 requests) were addressed to the original Eazi.com, 29% (15 requests) were made to Dh3yk7bgkxpyv.cloudfront.net and 15% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Dh3yk7bgkxpyv.cloudfront.net.

Page Optimization Overview & Recommendations

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

Content Size

1.0 MB

After Optimization

691.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eazi.com main page is 1.0 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. Javascripts take 660.8 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 25.6 kB

  • Original 34.1 kB
  • After minification 31.0 kB
  • After compression 8.4 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 25.6 kB or 75% of the original size.

Image Optimization

-7%

Potential reduce by 16.6 kB

  • Original 221.5 kB
  • After minification 204.9 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. Eazi images are well optimized though.

JavaScript Optimization

-41%

Potential reduce by 270.0 kB

  • Original 660.8 kB
  • After minification 660.6 kB
  • After compression 390.8 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 270.0 kB or 41% of the original size.

CSS Optimization

-3%

Potential reduce by 2.8 kB

  • Original 90.1 kB
  • After minification 90.1 kB
  • After compression 87.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. Eazi.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 19 (46%)

Requests Now

41

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.eazi.com

www.eazi.com

289 ms

styles.css

styles.css

72 ms

addons.css

addons.css

143 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

287 ms

all.js

all.js

207 ms

addons.js

addons.js

359 ms

home.css

home.css

207 ms

priceformat.js

priceformat.js

208 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

25 ms

e35869c903ca48bcb0eaffbd4187e967.js

e35869c903ca48bcb0eaffbd4187e967.js

55 ms

js

js

86 ms

js

js

105 ms

css

css

46 ms

font-awesome.min.css

font-awesome.min.css

211 ms

analytics.js

analytics.js

159 ms

sale_white.png

sale_white.png

178 ms

offer_white.png

offer_white.png

588 ms

Eazi_Web_logo_40px_Blk.png

Eazi_Web_logo_40px_Blk.png

557 ms

Eazi_Web_logoTagline_40px_Blk.png

Eazi_Web_logoTagline_40px_Blk.png

557 ms

listed.png

listed.png

557 ms

agent.png

agent.png

557 ms

market_online.png

market_online.png

557 ms

schedule.png

schedule.png

872 ms

offer.png

offer.png

876 ms

sold.png

sold.png

912 ms

search_map.png

search_map.png

870 ms

cart.png

cart.png

863 ms

eaziLogo.png

eaziLogo.png

897 ms

ooba_prequal_button.png

ooba_prequal_button.png

1273 ms

fbevents.js

fbevents.js

166 ms

SKkVq5yGAPk

SKkVq5yGAPk

230 ms

bg_1.jpg

bg_1.jpg

1302 ms

ust_worker.jsp

ust_worker.jsp

112 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xDwxUD22FA.woff

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xDwxUD22FA.woff

56 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o58a-xDwxUD22FA.woff

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o58a-xDwxUD22FA.woff

73 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkKEo58a-xDwxUD22FA.woff

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkKEo58a-xDwxUD22FA.woff

79 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv58a-xDwxUD22FA.woff

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv58a-xDwxUD22FA.woff

82 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

283 ms

KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff

KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff

80 ms

KFOlCnqEu92Fr1MmSU5fBBc-AMP6lQ.woff

KFOlCnqEu92Fr1MmSU5fBBc-AMP6lQ.woff

79 ms

js

js

48 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

25 ms

base.js

base.js

46 ms

ad_status.js

ad_status.js

145 ms

om_QuI9M6WDewyV11PDqwyZXtjss-zYzBgeHLXyLCgE.js

om_QuI9M6WDewyV11PDqwyZXtjss-zYzBgeHLXyLCgE.js

99 ms

embed.js

embed.js

27 ms

KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff

KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff

22 ms

KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff

KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff

22 ms

id

id

19 ms

Create

Create

84 ms

GenerateIT

GenerateIT

12 ms

Accessibility Review

eazi.com accessibility score

42

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

eazi.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

eazi.com SEO score

74

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

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 Eazi.com 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 Eazi.com 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

eazi.com

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