Tools & Wizards About Us
homepad.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

homepad.com

homePad - L'application mobile qui simplifie votre gestion locative

Page Load Speed

5.5 sec in total

First Response

208 ms

Resources Loaded

5.2 sec

Page Rendered

79 ms

homepad.com screenshot

About Website

Visit homepad.com now to see the best up-to-date HomePad content and also check out these interesting facts you probably never knew about homepad.com

Avec l'application homePad, oubliez vos papiers et réalisez vos états des lieux en deux fois moins de temps !

Visit homepad.com

Key Findings

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

Performance Metrics

homepad.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value19.1 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value4,100 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.23

54/100

15%

TTI (Time to Interactive)

Value19.8 s

2/100

10%

Network Requests Diagram

homepad.com

208 ms

www.homepad.com

453 ms

css

77 ms

materialdesignicons.min.css

111 ms

animate.min.css

74 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 92% of them (61 requests) were addressed to the original Homepad.com, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Homepad.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 17.1 kB (2%)

Content Size

1.0 MB

After Optimization

1.0 MB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Homepad.com main page is 1.0 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. Javascripts take 940.6 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 12.2 kB

  • Original 15.4 kB
  • After minification 15.4 kB
  • After compression 3.2 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 12.2 kB or 79% of the original size.

JavaScript Optimization

-1%

Potential reduce by 4.7 kB

  • Original 940.6 kB
  • After minification 940.3 kB
  • After compression 935.9 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 173 B

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

Requests Breakdown

Number of requests can be reduced by 62 (97%)

Requests Now

64

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

homepad.com

homepad.com

208 ms

www.homepad.com

www.homepad.com

453 ms

css

css

77 ms

materialdesignicons.min.css

materialdesignicons.min.css

111 ms

animate.min.css

animate.min.css

74 ms

v0.js

v0.js

56 ms

npm.vuetify.892d2cef.css

npm.vuetify.892d2cef.css

376 ms

app.38aa96be.css

app.38aa96be.css

413 ms

js

js

94 ms

runtime.55ca2cf2.js

runtime.55ca2cf2.js

408 ms

npm.vuetify.9d0cdcfa.js

npm.vuetify.9d0cdcfa.js

75 ms

npm.core-js.6c07b10c.js

npm.core-js.6c07b10c.js

437 ms

npm.sentry.ffc340f0.js

npm.sentry.ffc340f0.js

436 ms

npm.lodash.3c5643d1.js

npm.lodash.3c5643d1.js

438 ms

npm.axios.c331af1c.js

npm.axios.c331af1c.js

773 ms

npm.vee-validate.a7ce08d9.js

npm.vee-validate.a7ce08d9.js

764 ms

npm.recaptcha-v3.62644551.js

npm.recaptcha-v3.62644551.js

786 ms

npm.webpack.04a0c27c.js

npm.webpack.04a0c27c.js

780 ms

npm.countup.js.698ecb82.js

npm.countup.js.698ecb82.js

805 ms

npm.deepmerge.61ff5aad.js

npm.deepmerge.61ff5aad.js

441 ms

npm.node-libs-browser.c1a7e667.js

npm.node-libs-browser.c1a7e667.js

455 ms

npm.path-browserify.d23c2984.js

npm.path-browserify.d23c2984.js

830 ms

npm.tslib.ccd8637c.js

npm.tslib.ccd8637c.js

1124 ms

npm.v-click-outside.35de5cf7.js

npm.v-click-outside.35de5cf7.js

778 ms

npm.vue-carousel.591c8b29.js

npm.vue-carousel.591c8b29.js

1149 ms

npm.vue-cookie-law.ddb58e08.js

npm.vue-cookie-law.ddb58e08.js

1166 ms

npm.vue-countup-v2.0a97e615.js

npm.vue-countup-v2.0a97e615.js

1159 ms

npm.vue-i18n.7f7e11a9.js

npm.vue-i18n.7f7e11a9.js

1167 ms

npm.vue-loader.3c0277df.js

npm.vue-loader.3c0277df.js

1227 ms

npm.vue-meta.aaffb221.js

npm.vue-meta.aaffb221.js

1501 ms

npm.vue-notification.881f842e.js

npm.vue-notification.881f842e.js

1513 ms

npm.vue-recaptcha-v3.d3ae7dd5.js

npm.vue-recaptcha-v3.d3ae7dd5.js

1520 ms

npm.vue-resize-text.fd05d327.js

npm.vue-resize-text.fd05d327.js

1627 ms

npm.vue-router.17a46785.js

npm.vue-router.17a46785.js

1516 ms

npm.vue.92b49f75.js

npm.vue.92b49f75.js

1586 ms

npm.vuex.80e38196.js

npm.vuex.80e38196.js

1860 ms

app.1ff33142.js

app.1ff33142.js

1889 ms

runtime-legacy.55ca2cf2.js

runtime-legacy.55ca2cf2.js

1907 ms

npm.core-js-legacy.c990f67c.js

npm.core-js-legacy.c990f67c.js

2108 ms

npm.vuetify-legacy.b3efbf88.js

npm.vuetify-legacy.b3efbf88.js

2266 ms

npm.sentry-legacy.ffc340f0.js

npm.sentry-legacy.ffc340f0.js

2201 ms

npm.lodash-legacy.3c5643d1.js

npm.lodash-legacy.3c5643d1.js

2705 ms

npm.babel-legacy.d9012074.js

npm.babel-legacy.d9012074.js

2289 ms

npm.axios-legacy.c331af1c.js

npm.axios-legacy.c331af1c.js

2221 ms

npm.vee-validate-legacy.a7ce08d9.js

npm.vee-validate-legacy.a7ce08d9.js

2196 ms

npm.recaptcha-v3-legacy.62644551.js

npm.recaptcha-v3-legacy.62644551.js

2201 ms

npm.webpack-legacy.04a0c27c.js

npm.webpack-legacy.04a0c27c.js

2216 ms

npm.countup.js-legacy.698ecb82.js

npm.countup.js-legacy.698ecb82.js

2248 ms

npm.deepmerge-legacy.61ff5aad.js

npm.deepmerge-legacy.61ff5aad.js

1974 ms

npm.node-libs-browser-legacy.c1a7e667.js

npm.node-libs-browser-legacy.c1a7e667.js

2366 ms

npm.path-browserify-legacy.d23c2984.js

npm.path-browserify-legacy.d23c2984.js

2590 ms

npm.tslib-legacy.ccd8637c.js

npm.tslib-legacy.ccd8637c.js

2317 ms

npm.v-click-outside-legacy.35de5cf7.js

npm.v-click-outside-legacy.35de5cf7.js

2256 ms

npm.vue-carousel-legacy.591c8b29.js

npm.vue-carousel-legacy.591c8b29.js

2379 ms

npm.vue-cookie-law-legacy.ddb58e08.js

npm.vue-cookie-law-legacy.ddb58e08.js

2409 ms

npm.vue-countup-v2-legacy.0a97e615.js

npm.vue-countup-v2-legacy.0a97e615.js

2399 ms

npm.vue-i18n-legacy.7f7e11a9.js

npm.vue-i18n-legacy.7f7e11a9.js

2521 ms

npm.vue-loader-legacy.3c0277df.js

npm.vue-loader-legacy.3c0277df.js

2608 ms

npm.vue-meta-legacy.aaffb221.js

npm.vue-meta-legacy.aaffb221.js

2603 ms

npm.vue-notification-legacy.881f842e.js

npm.vue-notification-legacy.881f842e.js

2455 ms

npm.vue-recaptcha-v3-legacy.d3ae7dd5.js

npm.vue-recaptcha-v3-legacy.d3ae7dd5.js

2434 ms

npm.vue-resize-text-legacy.fd05d327.js

npm.vue-resize-text-legacy.fd05d327.js

2509 ms

npm.vue-router-legacy.17a46785.js

npm.vue-router-legacy.17a46785.js

2601 ms

npm.vue-legacy.92b49f75.js

npm.vue-legacy.92b49f75.js

2889 ms

npm.vuex-legacy.80e38196.js

npm.vuex-legacy.80e38196.js

2602 ms

app-legacy.8c2deea3.js

app-legacy.8c2deea3.js

2911 ms

Accessibility Review

homepad.com accessibility score

79

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

homepad.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

homepad.com SEO score

64

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

High

Document doesn't have a valid hreflang

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

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

High

Document uses legible font sizes

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

homepad.com

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