Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

update.elliman.com

Douglas Elliman | Luxury Real Estate and Homes for Sale | Homepage

Page Load Speed

227 ms in total

First Response

19 ms

Resources Loaded

148 ms

Page Rendered

60 ms

About Website

Visit update.elliman.com now to see the best up-to-date Update Elliman content for United States and also check out these interesting facts you probably never knew about update.elliman.com

Browse our wide range of luxury homes for sale and rent. Contact our real estate agents to find your dream home.

Visit update.elliman.com

Key Findings

We analyzed Update.elliman.com page load time and found that the first response time was 19 ms and then it took 208 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

update.elliman.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value21.5 s

0/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value6,140 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.186

66/100

15%

TTI (Time to Interactive)

Value22.2 s

1/100

10%

Network Requests Diagram

update.elliman.com

19 ms

challenge.js

125 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that 50% of them (1 request) were addressed to the original Update.elliman.com, 50% (1 request) were made to 249f108cb8d8.45802a9a.us-east-1.token.awswaf.com. The less responsive or slowest element that took the longest time to load (125 ms) relates to the external source 249f108cb8d8.45802a9a.us-east-1.token.awswaf.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 937 B (0%)

Content Size

292.7 kB

After Optimization

291.8 kB

In fact, the total size of Update.elliman.com main page is 292.7 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 290.6 kB which makes up the majority of the site volume.

HTML Optimization

-43%

Potential reduce by 937 B

  • Original 2.2 kB
  • After minification 2.1 kB
  • After compression 1.2 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 937 B or 43% of the original size.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 290.6 kB
  • After minification 290.6 kB
  • After compression 290.6 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.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Update Elliman. According to our analytics all requests are already optimized.

Accessibility Review

update.elliman.com accessibility score

80

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-*] attributes do not match their roles

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

[id] attributes on active, focusable elements are not unique

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

Links do not have a discernible name

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

update.elliman.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

Missing source maps for large first-party JavaScript

SEO Factors

update.elliman.com SEO score

76

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

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 doesn't use 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 Update.elliman.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 Update.elliman.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

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