Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

brianphillips.elliman.com

Brian Phillips Real Estate Agent - NYC | Douglas Elliman

Page Load Speed

2.8 sec in total

First Response

54 ms

Resources Loaded

1.8 sec

Page Rendered

893 ms

brianphillips.elliman.com screenshot

About Website

Welcome to brianphillips.elliman.com homepage info - get ready to check Brian Phillips Elliman best content for United States right away, or after learning these important things about brianphillips.elliman.com

With a passion for excellence, Brian Phillips is here to help you find a great place to call home in NYC. Learn more about us and search our listings.

Visit brianphillips.elliman.com

Key Findings

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

Performance Metrics

brianphillips.elliman.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

70/100

25%

SI (Speed Index)

Value22.9 s

0/100

10%

TBT (Total Blocking Time)

Value31,730 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.466

0/100

15%

TTI (Time to Interactive)

Value45.0 s

0/100

10%

Network Requests Diagram

brianphillips.elliman.com

54 ms

brianphillips.elliman.com

540 ms

__maindomain-www.elliman.comnewyorkcity__,0_010000_global,d41d8cd98f00b204e9800998ecf8427e_customeasypaw,topcss,,4_19_0_324,7f065271ed5af16d41b6b24e68fec148.css

208 ms

__maindomain-www.elliman.comnewyorkcity__,0_010000_245935_page,c5d112c0f842c7a76ffd784704c45d4a_customeasypaw-27845,topcss,,4_19_0_324,d339791eb6399685770112c975ebfaa1.css

278 ms

__maindomain-www.elliman.comnewyorkcity__,0_010000_global,d41d8cd98f00b204e9800998ecf8427e_customeasypaw,topoverridescss,,4_19_0_324,7f065271ed5af16d41b6b24e68fec148.css

228 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Brianphillips.elliman.com, 38% (10 requests) were made to Static-ind-elliman-newyorkcity-production.gtsstatic.net and 12% (3 requests) were made to Static-ind-elliman-newyorkcity-production-0.gtsstatic.net. The less responsive or slowest element that took the longest time to load (655 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 134.8 kB (81%)

Content Size

165.6 kB

After Optimization

30.8 kB

In fact, the total size of Brianphillips.elliman.com main page is 165.6 kB. 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. HTML takes 165.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 134.8 kB

  • Original 165.2 kB
  • After minification 161.9 kB
  • After compression 30.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 134.8 kB or 82% of the original size.

Image Optimization

-19%

Potential reduce by 77 B

  • Original 401 B
  • After minification 324 B

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, Brian Phillips Elliman needs image optimization as it can save up to 77 B or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 15 (83%)

Requests Now

18

After Optimization

3

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

Accessibility Review

brianphillips.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-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

[aria-*] attributes do not have valid values

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

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

brianphillips.elliman.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

brianphillips.elliman.com SEO score

83

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 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 Brianphillips.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 Brianphillips.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 data is detected on the main page of Brian Phillips Elliman. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: