7.6 sec in total
728 ms
6.4 sec
522 ms
Visit homa.su now to see the best up-to-date Homa content for Canada and also check out these interesting facts you probably never knew about homa.su
Строительство и проектирование домов из клееного бруса по типовым и индивидуальным проектам с ценами под ключ. Собственное производство бруса и опыт более 12 лет компании «ХОМА».
Visit homa.suWe analyzed Homa.su page load time and found that the first response time was 728 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
homa.su performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value30.4 s
0/100
25%
Value11.8 s
4/100
10%
Value790 ms
37/100
30%
Value0.273
45/100
15%
Value17.1 s
4/100
10%
728 ms
516 ms
1258 ms
114 ms
228 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 78% of them (87 requests) were addressed to the original Homa.su, 6% (7 requests) were made to Youtube.com and 4% (4 requests) were made to Img.youtube.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Homa.su.
Page size can be reduced by 542.2 kB (8%)
6.7 MB
6.2 MB
In fact, the total size of Homa.su main page is 6.7 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 6.0 MB which makes up the majority of the site volume.
Potential reduce by 44.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 44.2 kB or 78% of the original size.
Potential reduce by 80.2 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. Homa images are well optimized though.
Potential reduce by 97.1 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 97.1 kB or 43% of the original size.
Potential reduce by 320.7 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. Homa.su needs all CSS files to be minified and compressed as it can save up to 320.7 kB or 80% of the original size.
Number of requests can be reduced by 30 (28%)
106
76
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Homa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
homa.su
728 ms
homa.su
516 ms
www.homa.su
1258 ms
core.css
114 ms
CoreSans.css
228 ms
PTSans.css
343 ms
GothamPro.css
341 ms
owl.carousel.css
348 ms
style.css
358 ms
core_popup.css
358 ms
style.css
358 ms
styles.css
453 ms
template_styles.css
577 ms
api.js
28 ms
script.js
466 ms
core.js
605 ms
core_ajax.js
477 ms
session.js
486 ms
core_popup.js
569 ms
jquery.min.js
822 ms
jquery-fly.js
596 ms
owl.carousel.js
731 ms
jquery-migrate-1.1.1.js
682 ms
script.js
688 ms
canvas.js
714 ms
recaptcha__en.js
29 ms
watch.js
26 ms
hqdefault.jpg
70 ms
hqdefault.jpg
102 ms
hqdefault.jpg
186 ms
hqdefault.jpg
206 ms
logo.png
122 ms
icon-project.png
125 ms
icon-phone.png
121 ms
icon-mail.png
124 ms
arrow-page-up.png
124 ms
060ec52f4589eb8620fda3e0fb483942.jpg
1230 ms
fc8225424803e7672be21ace2df2c434.jpg
612 ms
eea754f149179e217b3118dbf0e7e824.jpg
521 ms
52f6c59af5228e593173f997750573db.jpg
520 ms
e6efa268d30a34e5de66785e5a02dae6.jpg
597 ms
11c408d9248c9d99c502ee78cb9bb17f.jpg
639 ms
c4bd412efc34939ea8ce373e1f4619c9.jpg
757 ms
d41f2b167330f7d1620abf31ef5f286a.jpg
750 ms
8d300765b0843ab0079db6415e0b308c.jpg
836 ms
1d46cf7b6b328fcd36de2dcfadc42223.jpg
839 ms
721e5a251fed1f9cf5f3b0eb344fac27.jpg
878 ms
abc60639dfe20ca696a746c175e944fe.jpg
977 ms
4859434a8811d712cd4b962bb8b4eae3.jpg
993 ms
670542a15a32bb88a6ad7ff81185bec8.jpg
1077 ms
7e056d73c30c57f11b1a687b45746b39.jpg
1069 ms
c8aa1fb02079cd38f3d1039cda2f7029.jpg
1117 ms
a8c2001be058a03e18453db7a04a29e8.jpg
1204 ms
a701f7136a954461047b28e6dcdebe75.jpg
1226 ms
9a61a6d02cad681a4ca211f20bc33ac5.jpg
1296 ms
46bfb65c69d6171e296c377f43498bd9.jpg
1317 ms
3a07e76be6b34806581348595c3e7e9e.jpg
1357 ms
db65324856414107870e4e8eaf6b89a2.jpg
1432 ms
4ed6f273bf3f8691ca1a4f710ea51974.jpg
1346 ms
c7e22719f18e5c5dab58994eb238e929.jpg
1465 ms
f7cf14254e194763ee8d28e1a222e0b2.jpg
1523 ms
ffc6dccee4859ee48073275c2a711d1c.jpg
1676 ms
1f21e8875dd5cc005cc5242cbd79078b.jpg
1578 ms
a8fa0872fdf1a44cf815655e70835108.jpg
1595 ms
4d552830b9627bc57c50c13ffb3be2aa.jpg
1660 ms
88593a877d5e544b40dc51a12f9e3813.jpg
1704 ms
3769e23266232d6e4cd2314ae76cb936.jpg
1732 ms
auQpt_Cnoyo
92 ms
analytics.js
13 ms
PTSans-Bold.woff
1700 ms
PTSans-Regular.woff
1722 ms
PTSans-Italic.woff
1882 ms
PTSans-BoldItalic.woff
1802 ms
e496dd05e9476709b615683b39698269.jpg
1820 ms
collect
12 ms
collect
34 ms
www-player.css
8 ms
www-embed-player.js
26 ms
base.js
49 ms
fetch-polyfill.js
24 ms
ga-audiences
132 ms
ad_status.js
117 ms
WmYtwbYsvJeTDmsuIOmqRAOrqYQ4FznKv6GQB7SOtoo.js
75 ms
embed.js
37 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
93 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
99 ms
id
60 ms
edaba439d48a3de376a9cd8fc20f65a4.jpg
1461 ms
a61d470a5c39097eb31afa86b8bc74e0.jpg
1532 ms
Create
25 ms
e0476b9171bd41025138f79099d67ef3.jpg
1484 ms
d84461f1a91aa23608bce4e05c3bde0d.jpg
1435 ms
579d9687f828a1b2ab7a6d40e43d742a.jpg
1545 ms
GenerateIT
12 ms
e816293f38642f25d6e77d367df84e78.jpg
1347 ms
39142f87d511e4065388e596950b5b7e.jpg
1476 ms
06be79c56b58a671cf7cfe8dc6dada7a.jpg
1449 ms
ff84b02412cb80788722bbdbf8eaadda.jpg
1342 ms
index-geography.jpg
1571 ms
banner-v-krivykh.png
1925 ms
banner.jpg
1773 ms
main_sliderpic_003.jpg
1710 ms
mob-owl-prev.png
1268 ms
mob-owl-next.png
1286 ms
owl-prev.jpg
1254 ms
owl-next.jpg
1297 ms
create-project.jpg
1342 ms
draw-project.png
1505 ms
smile.png
1326 ms
icon-youtube.png
1344 ms
log_event
18 ms
print.css
114 ms
homa.su 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
homa.su best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
homa.su SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Homa.su can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Homa.su 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.
homa.su
Open Graph description is not detected on the main page of Homa. 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: