4.4 sec in total
27 ms
3.6 sec
709 ms
Visit homehome.app now to see the best up-to-date Home content and also check out these interesting facts you probably never knew about homehome.app
apple homekit smart google home Light, Garage, Switch, Thermostat, Security, Doorbell, Dimmer, Curtain Motor. automation wireless zigbee wifi
Visit homehome.appWe analyzed Homehome.app page load time and found that the first response time was 27 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
homehome.app performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value4.3 s
41/100
25%
Value5.3 s
57/100
10%
Value130 ms
96/100
30%
Value0
100/100
15%
Value7.0 s
52/100
10%
27 ms
1842 ms
72 ms
74 ms
44 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 46% of them (71 requests) were addressed to the original Homehome.app, 21% (33 requests) were made to Fonts.wp.com and 14% (21 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Homehome.app.
Page size can be reduced by 272.7 kB (25%)
1.1 MB
797.1 kB
In fact, the total size of Homehome.app main page is 1.1 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 453.6 kB which makes up the majority of the site volume.
Potential reduce by 256.0 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 256.0 kB or 83% of the original size.
Potential reduce by 0 B
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. Home images are well optimized though.
Potential reduce by 350 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 16.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. Homehome.app has all CSS files already compressed.
Number of requests can be reduced by 64 (72%)
89
25
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Home . We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 57 to 1 for CSS and as a result speed up the page load time.
homehome.app
27 ms
homehome.app
1842 ms
woocommerce-multi-currency.min.css
72 ms
mediaelementplayer-legacy.min.css
74 ms
wp-mediaelement.min.css
44 ms
blocks.css
78 ms
style.css
67 ms
woocommerce.css
43 ms
woocommerce.css
84 ms
dashicons.min.css
67 ms
checkout-blocks.css
78 ms
elementor-icons.min.css
80 ms
frontend-lite.min.css
111 ms
swiper.min.css
77 ms
post-14.css
119 ms
global.css
116 ms
post-24.css
115 ms
all.min.css
123 ms
xstore.min.css
152 ms
elementor.min.css
147 ms
back-top.min.css
118 ms
global.min.css
120 ms
contact-forms.min.css
164 ms
menu.min.css
149 ms
kirki-styles.css
165 ms
woocommerce.css
187 ms
style.css
202 ms
css
90 ms
xstore-icons.css
184 ms
bold.css
185 ms
fontawesome.min.css
170 ms
solid.min.css
175 ms
regular.min.css
197 ms
jetpack.css
188 ms
w.js
70 ms
jquery.min.js
77 ms
jquery.blockUI.min.js
419 ms
analytics.js
77 ms
widget-icon-box.min.css
182 ms
off-canvas.min.css
180 ms
cart-widget.min.css
191 ms
js
138 ms
e-202409.js
61 ms
account.min.css
410 ms
login.min.css
385 ms
search.min.css
162 ms
ajax-search.min.css
138 ms
mobile-menu.min.css
227 ms
toggles-by-arrow.min.css
357 ms
etheme-animated-headline.min.css
357 ms
etheme-text-button.min.css
352 ms
etheme-advanced-headline.min.css
380 ms
etheme-icon-list.min.css
378 ms
etheme-hotspot.min.css
345 ms
etheme-vertical-timeline.min.css
375 ms
banner.min.css
344 ms
banners-global.min.css
341 ms
blog-global.min.css
340 ms
post-33.css
726 ms
styles.css
345 ms
etheme-contact-form-7.min.css
720 ms
post-6799.css
716 ms
flags-64.min.css
693 ms
animations.min.css
302 ms
brands.min.css
725 ms
jquery.lazyload.js
673 ms
lazyload.min.js
713 ms
wp-jp-re-1.webp
614 ms
07_Review-min.jpeg
552 ms
ec.js
163 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
729 ms
font
735 ms
KFOmCnqEu92Fr1Mu7GxMKTU1Kvnz.woff
741 ms
KFOmCnqEu92Fr1Mu7WxMKTU1Kvnz.woff
963 ms
KFOmCnqEu92Fr1Mu4WxMKTU1Kvnz.woff
962 ms
KFOmCnqEu92Fr1Mu7mxMKTU1Kvnz.woff
962 ms
KFOmCnqEu92Fr1Mu5mxMKTU1Kvnz.woff
968 ms
KFOmCnqEu92Fr1Mu72xMKTU1Kvnz.woff
963 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
730 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
968 ms
KFOlCnqEu92Fr1MmEU9fChc-AMP6lbBP.woff
1076 ms
KFOlCnqEu92Fr1MmEU9fCxc-AMP6lbBP.woff
1027 ms
KFOlCnqEu92Fr1MmEU9fBxc-AMP6lbBP.woff
1027 ms
KFOlCnqEu92Fr1MmEU9fCBc-AMP6lbBP.woff
1076 ms
KFOlCnqEu92Fr1MmEU9fABc-AMP6lbBP.woff
1124 ms
KFOlCnqEu92Fr1MmEU9fCRc-AMP6lbBP.woff
1126 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
730 ms
KFOlCnqEu92Fr1MmSU5fBBc-AMP6lQ.woff
1157 ms
KFOlCnqEu92Fr1MmSU5fChc-AMP6lbBP.woff
1156 ms
KFOlCnqEu92Fr1MmSU5fCxc-AMP6lbBP.woff
1160 ms
KFOlCnqEu92Fr1MmSU5fBxc-AMP6lbBP.woff
1160 ms
KFOlCnqEu92Fr1MmSU5fCBc-AMP6lbBP.woff
1223 ms
KFOlCnqEu92Fr1MmSU5fABc-AMP6lbBP.woff
1222 ms
KFOlCnqEu92Fr1MmSU5fCRc-AMP6lbBP.woff
1222 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
731 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
729 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
730 ms
xstore-icons-bold.ttf
589 ms
xstore-icons-bold.ttf
590 ms
fa-solid-900.woff
723 ms
fa-solid-900.ttf
727 ms
fa-regular-400.woff
727 ms
fa-regular-400.ttf
727 ms
O4ZMFGj5hxF0EhjimngomvnCCtqb30OX7jTSC5_R.ttf
729 ms
O4ZMFGj5hxF0EhjimngomvnCCtqb30OX1zTSC5_R.ttf
729 ms
O4ZMFGj5hxF0EhjimngomvnCCtqb30OXsDTSC5_R.ttf
730 ms
O4ZMFGj5hxF0EhjimngomvnCCtqb30OXmTTSC5_R.ttf
730 ms
O4ZMFGj5hxF0EhjimngomvnCCtqb30OXAjPSC5_R.ttf
731 ms
O4ZMFGj5hxF0EhjimngomvnCCtqb30OXMDPSC5_R.ttf
731 ms
O4ZMFGj5hxF0EhjimngomvnCCtqb30OXbjPSC5_R.ttf
733 ms
O4ZMFGj5hxF0EhjimngomvnCCtqb30OXsDPSC5_R.ttf
731 ms
O4ZMFGj5hxF0EhjimngomvnCCtqb30OXMDLSC5_R.ttf
733 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAopxRSW3z.ttf
733 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAkJxRSW3z.ttf
733 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwA_JxRSW3z.ttf
734 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAIpxRSW3z.ttf
952 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAop1RSW3z.ttf
952 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAfJtRSW3z.ttf
952 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwARZtRSW3z.ttf
952 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAIptRSW3z.ttf
951 ms
rP2tp2ywxg089UriI5-g4vlH9VoD8CmcqZG40F9JadbnoEwAC5tRSW3z.ttf
955 ms
rP2rp2ywxg089UriCZaSExd86J3t9jz86Mvy4qCRAL19DksVat-JDV30TGI.ttf
961 ms
rP2rp2ywxg089UriCZaSExd86J3t9jz86Mvy4qCRAL19DksVat-7DV30TGI.ttf
960 ms
rP2rp2ywxg089UriCZaSExd86J3t9jz86Mvy4qCRAL19DksVat_XDV30TGI.ttf
961 ms
rP2rp2ywxg089UriCZaSExd86J3t9jz86Mvy4qCRAL19DksVat8JDV30TGI.ttf
960 ms
rP2rp2ywxg089UriCZaSExd86J3t9jz86Mvy4qCRAL19DksVat-JDF30TGI.ttf
960 ms
rP2rp2ywxg089UriCZaSExd86J3t9jz86Mvy4qCRAL19DksVat9XCl30TGI.ttf
1019 ms
rP2rp2ywxg089UriCZaSExd86J3t9jz86Mvy4qCRAL19DksVat9uCl30TGI.ttf
1117 ms
rP2rp2ywxg089UriCZaSExd86J3t9jz86Mvy4qCRAL19DksVat8JCl30TGI.ttf
1117 ms
rP2rp2ywxg089UriCZaSExd86J3t9jz86Mvy4qCRAL19DksVat8gCl30TGI.ttf
1118 ms
fa-brands-400.ttf
954 ms
fa-brands-400.woff
390 ms
g.gif
400 ms
g.gif
330 ms
logo-mail-500.png
64 ms
11.jpg
135 ms
22.jpg
185 ms
33.jpg
216 ms
44.jpg
216 ms
55.jpg
220 ms
66.jpg
283 ms
Image.jpeg
219 ms
dualr3.jpg
280 ms
dim.jpg
285 ms
homekit.jpeg
281 ms
a2-1-e1665336620567.png
284 ms
k2-e1680180086550.jpeg
285 ms
siri-Large-1.webp
348 ms
smarthome-1-scaled.webp
345 ms
500.webp
376 ms
cook.png
287 ms
collect
205 ms
xstore-icons-bold.woff
191 ms
xstore-icons-bold.woff2
131 ms
homehome.app accessibility score
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
homehome.app 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
homehome.app SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Homehome.app 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 Homehome.app 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.
homehome.app
Open Graph data is detected on the main page of Home . This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: