Tools & Wizards About Us
liveazlife.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

liveazlife.com

Placester: #1 Website Builder for Real Estate Agents and Teams

Page Load Speed

8.5 sec in total

First Response

17 ms

Resources Loaded

4.7 sec

Page Rendered

3.7 sec

liveazlife.com screenshot

About Website

Click here to check amazing Liveazlife content. Otherwise, check out these important facts you probably never knew about liveazlife.com

It’s easy to do it yourself and even easier to have it done for you. On-demand assistants, robust customization, and loads of back office controls. Free 30-day Trial. Types: Broker websites, team webs...

Visit liveazlife.com

Key Findings

We analyzed Liveazlife.com page load time and found that the first response time was 17 ms and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

liveazlife.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value28.5 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value3,200 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value35.2 s

0/100

10%

Network Requests Diagram

liveazlife.com

17 ms

liveazlife.kw.com

167 ms

All.min.15eb97ea97b180107f56b49ea47aea2e.gz.css

117 ms

js

155 ms

redirects.min.0507a712f4aa8aba9a63edaa453cc9cb.gz.js

181 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Liveazlife.com, 68% (51 requests) were made to Cflare.smarteragent.com and 12% (9 requests) were made to Dims.web.production.kw-prod.brightspot.cloud. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Cflare.smarteragent.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 6.0 MB (39%)

Content Size

15.2 MB

After Optimization

9.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Liveazlife.com main page is 15.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. 70% of websites need less resources to load. Images take 7.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 339.3 kB

  • Original 398.0 kB
  • After minification 357.3 kB
  • After compression 58.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 339.3 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 105.4 kB

  • Original 7.2 MB
  • After minification 7.1 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. Liveazlife images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 4.8 MB

  • Original 6.7 MB
  • After minification 6.7 MB
  • After compression 2.0 MB

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 4.8 MB or 71% of the original size.

CSS Optimization

-86%

Potential reduce by 765.1 kB

  • Original 893.5 kB
  • After minification 882.4 kB
  • After compression 128.4 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. Liveazlife.com needs all CSS files to be minified and compressed as it can save up to 765.1 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (9%)

Requests Now

69

After Optimization

63

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

liveazlife.com

liveazlife.com

17 ms

liveazlife.kw.com

liveazlife.kw.com

167 ms

All.min.15eb97ea97b180107f56b49ea47aea2e.gz.css

All.min.15eb97ea97b180107f56b49ea47aea2e.gz.css

117 ms

js

js

155 ms

redirects.min.0507a712f4aa8aba9a63edaa453cc9cb.gz.js

redirects.min.0507a712f4aa8aba9a63edaa453cc9cb.gz.js

181 ms

webcomponents-loader.ce44f83d1399e8dd41e607b70e0642c9.gz.js

webcomponents-loader.ce44f83d1399e8dd41e607b70e0642c9.gz.js

155 ms

All.min.e1af034d0d5b726f1fa8e04279073f0d.gz.js

All.min.e1af034d0d5b726f1fa8e04279073f0d.gz.js

541 ms

email-decode.min.js

email-decode.min.js

4 ms

datadog-rum.js

datadog-rum.js

211 ms

IEPolyfills.min.8465a07f5ca79ebc454ca39edbf9d76f.gz.js

IEPolyfills.min.8465a07f5ca79ebc454ca39edbf9d76f.gz.js

51 ms

css

css

246 ms

Resizer

Resizer

657 ms

1431 ms

Resizer

Resizer

1030 ms

Resizer

Resizer

1121 ms

Resizer

Resizer

1113 ms

Resizer

Resizer

1125 ms

Resizer

Resizer

1193 ms

Resizer

Resizer

1105 ms

Resizer

Resizer

1413 ms

Resizer

Resizer

1491 ms

Resizer

Resizer

1325 ms

Resizer

Resizer

1400 ms

Resizer

Resizer

1228 ms

Resizer

Resizer

1285 ms

Resizer

Resizer

1723 ms

Resizer

Resizer

1514 ms

Resizer

Resizer

1599 ms

Resizer

Resizer

1701 ms

Resizer

Resizer

1450 ms

Resizer

Resizer

1925 ms

Resizer

Resizer

1522 ms

Resizer

Resizer

2157 ms

Resizer

Resizer

1577 ms

Resizer

Resizer

1625 ms

Resizer

Resizer

1646 ms

Resizer

Resizer

1915 ms

Resizer

Resizer

1691 ms

Resizer

Resizer

2120 ms

Resizer

Resizer

2123 ms

Resizer

Resizer

2139 ms

Resizer

Resizer

2339 ms

Resizer

Resizer

2451 ms

Resizer

Resizer

2667 ms

Resizer

Resizer

2578 ms

Resizer

Resizer

2602 ms

Resizer

Resizer

2648 ms

Resizer

Resizer

2788 ms

460 ms

313 ms

300 ms

298 ms

316 ms

869 ms

655 ms

323 ms

All.min.15eb97ea97b180107f56b49ea47aea2e.gz.css

All.min.15eb97ea97b180107f56b49ea47aea2e.gz.css

79 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

68 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

94 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

95 ms

Resizer

Resizer

2379 ms

Resizer

Resizer

2125 ms

Resizer

Resizer

1891 ms

Resizer

Resizer

2080 ms

Resizer

Resizer

1903 ms

Resizer

Resizer

2367 ms

Resizer

Resizer

2385 ms

Resizer

Resizer

2425 ms

Resizer

Resizer

2221 ms

Resizer

Resizer

2248 ms

Resizer

Resizer

2200 ms

Resizer

Resizer

2644 ms

Resizer

Resizer

2745 ms

Resizer

Resizer

2492 ms

Resizer

Resizer

2839 ms

Accessibility Review

liveazlife.com accessibility score

88

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

Best Practices

liveazlife.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

liveazlife.com SEO score

77

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

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

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

liveazlife.com

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