Tools & Wizards About Us

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

direct.propertyline.com

RealNex, The best and only Commercial Real Estate Software you need

Page Load Speed

3.2 sec in total

First Response

216 ms

Resources Loaded

2.4 sec

Page Rendered

643 ms

About Website

Visit direct.propertyline.com now to see the best up-to-date Direct Propertyline content for United States and also check out these interesting facts you probably never knew about direct.propertyline.com

RealNex Navigator includes commercial real estate industry leading CRM, Financial Analysis, Presentation, Marketing and Transaction Management. Contact us for a demo and free trial.

Visit direct.propertyline.com

Key Findings

We analyzed Direct.propertyline.com page load time and found that the first response time was 216 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster. This domain responded with an error, which can significantly jeopardize Direct.propertyline.com rating and web reputation

Performance Metrics

direct.propertyline.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value27.1 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value23.5 s

1/100

10%

Network Requests Diagram

direct.propertyline.com

216 ms

pl_home

113 ms

bootstrap.min.css

40 ms

font-awesome.min.css

51 ms

iws6ohy.js

255 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Direct.propertyline.com, 58% (25 requests) were made to Res.cloudinary.com and 7% (3 requests) were made to Realnex.com. The less responsive or slowest element that took the longest time to load (908 ms) relates to the external source Res.cloudinary.com.

Page Optimization Overview & Recommendations

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

Content Size

5.6 MB

After Optimization

4.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 88.1 kB

  • Original 105.7 kB
  • After minification 92.1 kB
  • After compression 17.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. This page needs HTML code to be minified as it can gain 13.6 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 88.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 6.7 kB

  • Original 4.7 MB
  • After minification 4.6 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. Direct Propertyline images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 260.6 kB

  • Original 403.9 kB
  • After minification 403.9 kB
  • After compression 143.3 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 260.6 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 326.2 kB

  • Original 394.5 kB
  • After minification 392.7 kB
  • After compression 68.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. Direct.propertyline.com needs all CSS files to be minified and compressed as it can save up to 326.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (25%)

Requests Now

40

After Optimization

30

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

direct.propertyline.com accessibility score

84

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

Heading elements are not in a sequentially-descending order

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

direct.propertyline.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

direct.propertyline.com SEO score

100

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Direct.propertyline.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Direct.propertyline.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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