4.5 sec in total
1.1 sec
3.1 sec
241 ms
Visit ihus.group now to see the best up-to-date IHUS content and also check out these interesting facts you probably never knew about ihus.group
Contemporary granny annexe solutions. Free consultations, planning permission and a 10-year guarantee. Build your perfect granny annexe.
Visit ihus.groupWe analyzed Ihus.group page load time and found that the first response time was 1.1 sec and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
ihus.group performance score
name
value
score
weighting
Value16.0 s
0/100
10%
Value21.7 s
0/100
25%
Value17.1 s
0/100
10%
Value570 ms
52/100
30%
Value0.022
100/100
15%
Value21.6 s
1/100
10%
1142 ms
49 ms
32 ms
216 ms
227 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 71% of them (30 requests) were addressed to the original Ihus.group, 17% (7 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Ihus.group.
Page size can be reduced by 2.0 MB (62%)
3.2 MB
1.2 MB
In fact, the total size of Ihus.group main page is 3.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. 70% of websites need less resources to load. CSS take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 41.7 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 41.7 kB or 79% of the original size.
Potential reduce by 24.4 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. IHUS images are well optimized though.
Potential reduce by 109.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 109.9 kB or 59% of the original size.
Potential reduce by 1.8 MB
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. Ihus.group needs all CSS files to be minified and compressed as it can save up to 1.8 MB or 89% of the original size.
Number of requests can be reduced by 26 (79%)
33
7
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IHUS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.ihus.group
1142 ms
js
49 ms
analytics.js
32 ms
style.min.css
216 ms
styles.css
227 ms
js_composer.min.css
713 ms
css
54 ms
main.min.css
621 ms
font-awesome.min.css
303 ms
fontello.min.css
314 ms
style.css
288 ms
custom-skin11r.css
684 ms
media-skin11r.css
363 ms
style.css
377 ms
Defaults.css
389 ms
css
53 ms
ultimate.min.css
588 ms
jquery.min.js
532 ms
jquery-migrate.min.js
463 ms
frontend-gtag.min.js
539 ms
above-the-fold.min.js
616 ms
core.min.js
642 ms
ultimate.min.js
665 ms
collect
15 ms
main.min.js
843 ms
regenerator-runtime.min.js
781 ms
wp-polyfill.min.js
781 ms
index.js
840 ms
js_composer_front.min.js
841 ms
ihus-logo-small.png
108 ms
eastbourne-changing-place-case-study.jpg
109 ms
spectrumbar-long.jpg
107 ms
ihus-Adaptations-image.jpg
277 ms
jquery.mousewheel.min.js
179 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
107 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
172 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
187 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
189 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
186 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf
185 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
188 ms
Defaults.woff
173 ms
ihus.group accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
ihus.group 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ihus.group 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 Ihus.group 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.
ihus.group
Open Graph data is detected on the main page of IHUS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: