Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

brightlet.com

Free Automated Property Management Software for Landlords | brightLET

Page Load Speed

2.5 sec in total

First Response

188 ms

Resources Loaded

2 sec

Page Rendered

386 ms

brightlet.com screenshot

About Website

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

brightLET is a multi-award-winning automated property management and lettings solution for landlords and tenants.

Visit brightlet.com

Key Findings

We analyzed Brightlet.com page load time and found that the first response time was 188 ms and then it took 2.3 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

brightlet.com performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value2.7 s

97/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.6 s

81/100

10%

Network Requests Diagram

brightlet.com

188 ms

www.brightlet.com

362 ms

bootstrap.min.css

19 ms

main.css

24 ms

jquery.js

47 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Brightlet.com, 88% (35 requests) were made to D1up5da8tlmkbe.cloudfront.net and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source D1up5da8tlmkbe.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 22.6 kB (5%)

Content Size

488.1 kB

After Optimization

465.5 kB

In fact, the total size of Brightlet.com main page is 488.1 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. 45% of websites need less resources to load. Images take 372.9 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 21.0 kB

  • Original 27.6 kB
  • After minification 27.6 kB
  • After compression 6.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 21.0 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 1.5 kB

  • Original 372.9 kB
  • After minification 371.4 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. BrightLET images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 108 B

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

CSS Optimization

-0%

Potential reduce by 33 B

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

Requests Breakdown

Number of requests can be reduced by 4 (11%)

Requests Now

35

After Optimization

31

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

Accessibility Review

brightlet.com accessibility score

84

Accessibility Issues

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

Buttons do not have an accessible name

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.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

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

SEO Factors

brightlet.com SEO score

90

Search Engine Optimization Advices

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 Brightlet.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 Brightlet.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 BrightLET. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: