4 sec in total
78 ms
2.1 sec
1.9 sec
Visit tenantpay.com now to see the best up-to-date Tenant Pay content for Canada and also check out these interesting facts you probably never knew about tenantpay.com
Canada's first loyalty program for renters. Earn points, rent drops, and credit reporting on every payment.
Visit tenantpay.comWe analyzed Tenantpay.com page load time and found that the first response time was 78 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
tenantpay.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value21.9 s
0/100
25%
Value5.4 s
56/100
10%
Value1,690 ms
11/100
30%
Value0.191
64/100
15%
Value10.6 s
23/100
10%
78 ms
56 ms
547 ms
35 ms
46 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Tenantpay.com, 69% (70 requests) were made to Assets-global.website-files.com and 7% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (662 ms) relates to the external source Assets-global.website-files.com.
Page size can be reduced by 1.5 MB (19%)
8.2 MB
6.6 MB
In fact, the total size of Tenantpay.com main page is 8.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. Only a small number of websites need less resources to load. Images take 7.7 MB which makes up the majority of the site volume.
Potential reduce by 103.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 103.6 kB or 88% of the original size.
Potential reduce by 1.4 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. Obviously, Tenant Pay needs image optimization as it can save up to 1.4 MB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.5 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.
Potential reduce by 2.4 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. Tenantpay.com has all CSS files already compressed.
Number of requests can be reduced by 12 (14%)
86
74
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tenant Pay. 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 4 to 1 for CSS and as a result speed up the page load time.
tenantpay.com
78 ms
tenantpay.com
56 ms
www.tenantpay.com
547 ms
tenantpay.webflow.ceeae726d.css
35 ms
webfont.js
46 ms
api.js
51 ms
jquery-3.5.1.min.dc5e7f18c8.js
44 ms
webflow.a5ab5b02d.js
44 ms
css
47 ms
widget.css
215 ms
widget.js
341 ms
recaptcha__en.js
212 ms
64fa3fe71f9a1d9a5d179ce9_iconoir_cancel.svg
145 ms
64edd7ea2cf2cf473a3d0e39_Group%201610.png
302 ms
64e8851843656941ab125195_logo%402x.png
248 ms
64f1c46f2b65d3c3fbddf012_new%20hero%20img.png
307 ms
64f1beb972f97d02aeb85004_Ellipse%20circle.png
304 ms
64f1beb1e6b212d8af1b8322_Group%20rent.png
255 ms
64f1beb19d95e948bb89e4bc_Group%20244.png
250 ms
64f1beb08cc8b36dcec23a0e_Group%20206.png
290 ms
64e8f8782e8054399eb03879_Group%20204.png
329 ms
64e8ab9d3588988b391e55f6_Group%201595%402x.png
462 ms
64e8e588313ea4c1e55d4663_Rectangle%2093.png
578 ms
64e8b12007c0e9b770184cac_NoPath%20-%20Copy%20(2)%402x.png
458 ms
64e8b120f8716f6512615d09_NoPath%20-%20Copy%20(4)%402x.png
460 ms
64e8b11f2684ac3602354417_NoPath%20-%20Copy%20(3)%402x.png
462 ms
64e8b1273588988b3925a492_NoPath%20-%20Copy%20(4)%402x.png
473 ms
64e8b11f210dda4df7dbbbfd_NoPath%20-%20Copy%20(5)%402x.png
473 ms
64e8b11f2e55303124b98a01_NoPath%20-%20Copy%20(6)%402x.png
481 ms
64e8b118353db67190644ffc_Mask%20Group%2025%402x.png
478 ms
64e8b118fd76913199976d7f_NoPath%20-%20Copy%402x.png
488 ms
64fb14003dc59b592accb971_Bank_of_Montreal_BMO_logo_PNG1%201.svg
484 ms
64fb1361a80abcc43ed7feee_Tangerine_Bank_logo.svg.png
482 ms
64e8b4f7e62fe95f35f8ea03_Group%20433%402x.png
582 ms
64e8b8d7042c1a1fdd3adbac_Ellipse%2039%201%20(1).png
652 ms
64e8bf64cef9e65ec80f2be3_Group%20228%402x.png
562 ms
64e8bf63ee3c2a4dfba3da50_Group%20490%402x.png
488 ms
64e8bf6372896a5caa17fea6_Group%20498%402x.png
563 ms
64e8bf62ac72876969832780_Group%20486%402x.png
578 ms
64e8bf6204cafb480dcc6a37_Group%20499%402x.png
574 ms
64e8c6759d3822bd9f153fef_Group%20611%402x.png
657 ms
64e8d109cc1ed51273261c92_Group%20514%402x.png
573 ms
64e8d10aaed1fd34a9b26c24_Group%20513%402x.png
574 ms
64e8d10a9d3822bd9f222390_Group%20512%402x.png
580 ms
64e8ca25394b2f0dc9680fb9_Group%20609%402x.png
659 ms
6654115f6227c4e555d52357_Frame%2086.svg
577 ms
66540f19b7a92b5aa4f5e5e2_SOCII.png
579 ms
66540c253f690cadd6761326_Group%2087.svg
652 ms
64e882070c88780c16c97195_Pangram-Medium.otf
251 ms
64e881fcd886f5e7abd7a51c_Pangram-Regular.otf
251 ms
64e88221ff7569e887fc9ba0_Pangram-Bold.otf
268 ms
64e88250006ccc7100e720ac_Pangram-ExtraBold.otf
455 ms
64e8819e01be021376e44477_Segoe%20UI.ttf
273 ms
64e881b03707e5fdc74cd8dc_Segoe%20UI%20Bold.ttf
285 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
145 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
181 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
197 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
195 ms
64e8cee03015d9775e72c469_Group%201592%402x.png
652 ms
anchor
65 ms
anchor
87 ms
anchor
189 ms
64e8ffe29c0ba295a71dce85_Mask%20Group%2014.png
416 ms
64e900292f67d1d41c4da00b_Rectangle%20177.png
491 ms
64e9026a41023f3b1e660a86_Group%20617.svg
444 ms
64e9df21f889e9794fefeecc_NoPath%20-%20Copy%20(4).png
407 ms
styles__ltr.css
23 ms
recaptcha__en.js
27 ms
64e9df1e2064a3f8b9e49f09_NoPath%20-%20Copy%20(5).png
402 ms
64e9df580effffde4fc49b33_NoPath%20-%20Copy%20(4).png
402 ms
64e9df5721e5907499e01167_NoPath%20-%20Copy%20(6).png
408 ms
OIgm6ct-G6hNh5i9U8xy5lNjsT6YVTG9uZdpykbdxBU.js
98 ms
webworker.js
105 ms
64fa2764707e8b338fe9369e_image2.png
354 ms
logo_48.png
78 ms
64fa27683a5342e967bbea8f_image7.png
255 ms
64fb2deb11b75356c185cddf_image4%201.svg
290 ms
64fa278fd8c9533d1323b72f_image11.png
327 ms
64fb15cf78a92d721cdee482_image19%201.png
330 ms
64fa27694f74fa69c9156e2e_image9.jpg
469 ms
64fa2764d3a5e44378ffd1d7_image5.jpg
315 ms
64fb15cf8d22031b6dcada85_image3%201.png
380 ms
64fa2765be10283632d88d32_image15.png
394 ms
64fb15cea17ddc5fdd1671d2_image10%201.png
409 ms
64fa27682323abc6734ce48f_image6.jpg
482 ms
64fa27902077f1f3c0ad7029_image13.png
459 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
84 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
85 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
85 ms
64fb15cf78a92d721cdee472_image1%2010.png
420 ms
64fa27680531918b05d41696_image18.png
376 ms
recaptcha__en.js
87 ms
64fb2d93b37f6f9b5a5bcd27_image14%201.svg
455 ms
64fb16b657ee59c978fe6950_image17%201.svg
580 ms
64fb16b6643f0e710ff9bea5_image12%201.svg
662 ms
64fa27694ab2a1ce81de2f9f_image8.png
409 ms
64e9e16319b1e5258e6a9bf3_lines.png
494 ms
64ee6a20a8a7d2975cae88d8_ep_arrow-down.svg
426 ms
64e9ed9e472574a313e7a58e_Group%20129.png
493 ms
64e9ed9d7af8da9c45491ffb_Facebook.png
496 ms
64e9ed9db82f71fb77b11c43_Instagram.png
491 ms
64e9ed9c400c941a3b93d8b6_Linkedin.png
574 ms
tenantpay.com accessibility score
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
tenantpay.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
tenantpay.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Tenantpay.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 Tenantpay.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.
tenantpay.com
Open Graph description is not detected on the main page of Tenant Pay. 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: