1.7 sec in total
23 ms
613 ms
1.1 sec
Welcome to let.us homepage info - get ready to check Let best content for Canada right away, or after learning these important things about let.us
Open your door to better renting. Online rent payments, lease applications, tenant screening, and property management.
Visit let.usWe analyzed Let.us page load time and found that the first response time was 23 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
let.us performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value7.9 s
3/100
25%
Value4.1 s
79/100
10%
Value3,340 ms
2/100
30%
Value0.002
100/100
15%
Value11.5 s
18/100
10%
23 ms
19 ms
16 ms
14 ms
43 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 47% of them (26 requests) were addressed to the original Let.us, 40% (22 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (483 ms) belongs to the original domain Let.us.
Page size can be reduced by 247.2 kB (6%)
4.2 MB
4.0 MB
In fact, the total size of Let.us main page is 4.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. 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. Images take 4.1 MB which makes up the majority of the site volume.
Potential reduce by 18.4 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 2.9 kB, which is 12% 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 18.4 kB or 76% of the original size.
Potential reduce by 224.3 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. Let images are well optimized though.
Potential reduce by 585 B
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.
Potential reduce by 4.0 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. Let.us needs all CSS files to be minified and compressed as it can save up to 4.0 kB or 26% of the original size.
Number of requests can be reduced by 15 (50%)
30
15
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Let. 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 from 4 to 1 for CSS and as a result speed up the page load time.
let.us
23 ms
normalize.css
19 ms
webflow.css
16 ms
let-us.webflow.css
14 ms
webfont.js
43 ms
weglot.min.js
97 ms
loader
129 ms
jquery-3.5.1.min.dc5e7f18c8.js
47 ms
webflow.js
32 ms
snippet.js
109 ms
css
51 ms
logo.png
27 ms
x.svg
20 ms
card.svg
7 ms
bell.svg
17 ms
gift.svg
7 ms
receipt.svg
15 ms
cal.svg
11 ms
tenants-1.png
20 ms
tenants-2.png
18 ms
stopwatch.svg
22 ms
home-heart.svg
26 ms
tenants-3.png
25 ms
tenants-4.png
483 ms
mobile.svg
34 ms
comments.svg
35 ms
smile.svg
57 ms
partners.png
324 ms
id.svg
51 ms
check.svg
69 ms
loader.min.js
220 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
13 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
8 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
13 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
12 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
16 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
16 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
16 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
19 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
19 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8WXh0ow.ttf
26 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR9WXh0ow.ttf
22 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9WXh0ow.ttf
20 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0ow.ttf
20 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXh0ow.ttf
26 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6WXh0ow.ttf
26 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0ow.ttf
27 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6WXh0ow.ttf
30 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16WXh0ow.ttf
28 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkKEo58a-xw.ttf
32 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xw.ttf
29 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o58a-xw.ttf
32 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkCEv58a-xw.ttf
60 ms
MicrosoftTeams-image-3.jpg
22 ms
MicrosoftTeams-image-1.jpg
55 ms
let.us accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
let.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
let.us SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Let.us 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 Let.us 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.
let.us
Open Graph description is not detected on the main page of Let. 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: