Tools & Wizards About Us
ii-ie.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ii-ie.com

「いい家」をつくる会

Page Load Speed

7.5 sec in total

First Response

520 ms

Resources Loaded

5.2 sec

Page Rendered

1.8 sec

ii-ie.com screenshot

About Website

Welcome to ii-ie.com homepage info - get ready to check Ii Ie best content for Japan right away, or after learning these important things about ii-ie.com

「いい家」をつくる会　涼温な家　外断熱　涼温換気SA-SHEの家　エアコン1台で全館空調

Visit ii-ie.com

Key Findings

We analyzed Ii-ie.com page load time and found that the first response time was 520 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

ii-ie.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value14.5 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.162

72/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

ii-ie.com

520 ms

ii-ie.com

1992 ms

gtm.js

62 ms

toppage.css

581 ms

jquery.min.js

25 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 54% of them (44 requests) were addressed to the original Ii-ie.com, 10% (8 requests) were made to Scontent-sjc3-1.cdninstagram.com and 7% (6 requests) were made to I1.ytimg.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Ii-ie.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 223.9 kB (6%)

Content Size

3.5 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ii-ie.com main page is 3.5 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. 50% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 27.5 kB

  • Original 36.5 kB
  • After minification 33.9 kB
  • After compression 9.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 27.5 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 89.4 kB

  • Original 3.3 MB
  • After minification 3.2 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. Ii Ie images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 65.3 kB

  • Original 127.3 kB
  • After minification 108.7 kB
  • After compression 62.0 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 65.3 kB or 51% of the original size.

CSS Optimization

-70%

Potential reduce by 41.8 kB

  • Original 60.1 kB
  • After minification 43.2 kB
  • After compression 18.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. Ii-ie.com needs all CSS files to be minified and compressed as it can save up to 41.8 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (47%)

Requests Now

74

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ii Ie. 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 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ii-ie.com

ii-ie.com

520 ms

ii-ie.com

ii-ie.com

1992 ms

gtm.js

gtm.js

62 ms

toppage.css

toppage.css

581 ms

jquery.min.js

jquery.min.js

25 ms

bigram.carouselBox.v4.js

bigram.carouselBox.v4.js

748 ms

iiie.js

iiie.js

575 ms

iiie.look.js

iiie.look.js

578 ms

brand

brand

24 ms

brandjs.js

brandjs.js

15 ms

js

js

53 ms

analytics.js

analytics.js

19 ms

collect

collect

14 ms

collect

collect

101 ms

js

js

79 ms

html5-doctor-reset-stylesheet.min.css

html5-doctor-reset-stylesheet.min.css

178 ms

base.css

base.css

352 ms

carousel.css

carousel.css

213 ms

all.css

all.css

27 ms

css

css

34 ms

css

css

51 ms

css2

css2

56 ms

logo.png

logo.png

184 ms

hqdefault.jpg

hqdefault.jpg

146 ms

441606521_1438520660367949_8011913629705400365_n.jpg

441606521_1438520660367949_8011913629705400365_n.jpg

619 ms

su7tt9l0u9.jpg

su7tt9l0u9.jpg

1009 ms

441437056_322002584043826_7980458395819863588_n.jpg

441437056_322002584043826_7980458395819863588_n.jpg

845 ms

441506914_1450074378982193_8013752344734994877_n.jpg

441506914_1450074378982193_8013752344734994877_n.jpg

1289 ms

441474549_394133493588500_8669666135117754338_n.jpg

441474549_394133493588500_8669666135117754338_n.jpg

1129 ms

440764995_1102196101063179_4464528512704071949_n.jpg

440764995_1102196101063179_4464528512704071949_n.jpg

1171 ms

441153178_3948246448729827_4045079270792850593_n.jpg

441153178_3948246448729827_4045079270792850593_n.jpg

1082 ms

441084243_1167727940900484_4808495839452180660_n.jpg

441084243_1167727940900484_4808495839452180660_n.jpg

1535 ms

440873427_1238030200511295_421255552384714749_n.jpg

440873427_1238030200511295_421255552384714749_n.jpg

1064 ms

20231030.pc.jpg

20231030.pc.jpg

702 ms

list_photo_132.jpg

list_photo_132.jpg

882 ms

list_photo_177.jpg

list_photo_177.jpg

695 ms

list_photo_179.jpg

list_photo_179.jpg

871 ms

list_photo_178.jpg

list_photo_178.jpg

695 ms

list_photo_180.jpg

list_photo_180.jpg

1400 ms

title.svg

title.svg

868 ms

chairman.jpg

chairman.jpg

873 ms

zenkanryouonbou.svg

zenkanryouonbou.svg

877 ms

ryuonLogo.png

ryuonLogo.png

1043 ms

bt_pickup.jpg

bt_pickup.jpg

1043 ms

book01.jpg

book01.jpg

1226 ms

book05.jpg

book05.jpg

1576 ms

book04.jpg

book04.jpg

1058 ms

book03.jpg

book03.jpg

1216 ms

book02.jpg

book02.jpg

1217 ms

pagetop.png

pagetop.png

1235 ms

hqdefault.jpg

hqdefault.jpg

159 ms

hqdefault.jpg

hqdefault.jpg

171 ms

hqdefault.jpg

hqdefault.jpg

172 ms

hqdefault.jpg

hqdefault.jpg

173 ms

hqdefault.jpg

hqdefault.jpg

171 ms

b3mfm33dk9o.jpg

b3mfm33dk9o.jpg

1357 ms

2d4ilp7ju5c.jpg

2d4ilp7ju5c.jpg

1206 ms

nbm3q7tm4fc.jpg

nbm3q7tm4fc.jpg

1042 ms

496p7589tog.jpg

496p7589tog.jpg

1047 ms

0th32t16sfs.jpg

0th32t16sfs.jpg

1412 ms

branding.png

branding.png

100 ms

bg_menu2.nr.png

bg_menu2.nr.png

1266 ms

bg_menu3.nr.png

bg_menu3.nr.png

1265 ms

bg_menu4.nr.png

bg_menu4.nr.png

1278 ms

bg_menu5.nr.png

bg_menu5.nr.png

1286 ms

bg_menu6.nr.png

bg_menu6.nr.png

1438 ms

bg_menu7.nr.png

bg_menu7.nr.png

1439 ms

bg_menu8.nr.png

bg_menu8.nr.png

1447 ms

contentsindex_bg01.png

contentsindex_bg01.png

1454 ms

contentsindex_bg02.png

contentsindex_bg02.png

1461 ms

contentsindex_bg03.png

contentsindex_bg03.png

1611 ms

bg_messBt.png

bg_messBt.png

1612 ms

mrk_arrowR.png

mrk_arrowR.png

1621 ms

review_bg.png

review_bg.png

1623 ms

review_arw.png

review_arw.png

1629 ms

column_bg.jpg

column_bg.jpg

1637 ms

undefined

undefined

1785 ms

freeDial.png

freeDial.png

1786 ms

fa-solid-900.woff

fa-solid-900.woff

14 ms

fa-regular-400.woff

fa-regular-400.woff

28 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

28 ms

Accessibility Review

ii-ie.com accessibility score

52

Accessibility Issues

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

High

Image elements do not have [alt] attributes

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ii-ie.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

ii-ie.com SEO score

83

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

Image elements do not have [alt] attributes

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ii-ie.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Ii-ie.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

ii-ie.com

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