Tools & Wizards About Us
wow-h.jp screenshot

Report Summary

  • 2

    Performance

    Renders faster than
    20% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

wow-h.jp

分譲住宅や新築一戸建て、土地を広島エリアでご検討ならワウハウス

Page Load Speed

9.8 sec in total

First Response

552 ms

Resources Loaded

8.7 sec

Page Rendered

481 ms

wow-h.jp screenshot

About Website

Click here to check amazing Wow H content for Japan. Otherwise, check out these important facts you probably never knew about wow-h.jp

分譲住宅など住宅のことならお任せください。一戸建てや新築、土地のことまでお気軽にご相談ください。広島エリアにてモデルハウス多数公開中。住まいのことなら、ワウハウスグループへ。

Visit wow-h.jp

Key Findings

We analyzed Wow-h.jp page load time and found that the first response time was 552 ms and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

wow-h.jp performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value19.1 s

0/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value3,880 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.731

6/100

15%

TTI (Time to Interactive)

Value23.3 s

1/100

10%

Network Requests Diagram

wow-h.jp

552 ms

wow-h.jp

2616 ms

gtm.js

62 ms

gtm.js

118 ms

reset.css

499 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 33% of them (29 requests) were addressed to the original Wow-h.jp, 6% (5 requests) were made to Cm.g.doubleclick.net and 5% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Wow-h.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 135.4 kB (19%)

Content Size

730.2 kB

After Optimization

594.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wow-h.jp main page is 730.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 461.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 55.4 kB

  • Original 64.2 kB
  • After minification 41.6 kB
  • After compression 8.8 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. This page needs HTML code to be minified as it can gain 22.6 kB, which is 35% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 55.4 kB or 86% of the original size.

Image Optimization

-6%

Potential reduce by 8.9 kB

  • Original 148.7 kB
  • After minification 139.8 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. Wow H images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 29.7 kB

  • Original 461.8 kB
  • After minification 461.3 kB
  • After compression 432.2 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

-75%

Potential reduce by 41.4 kB

  • Original 55.5 kB
  • After minification 43.5 kB
  • After compression 14.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. Wow-h.jp needs all CSS files to be minified and compressed as it can save up to 41.4 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (68%)

Requests Now

72

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wow-h.jp

wow-h.jp

552 ms

wow-h.jp

wow-h.jp

2616 ms

gtm.js

gtm.js

62 ms

gtm.js

gtm.js

118 ms

reset.css

reset.css

499 ms

common.css

common.css

510 ms

index_firstview.css

index_firstview.css

508 ms

d0b-UUJEUU9HN1lCNXxVYTVsVVN5M3V0dnEyQlhaRDM3WQ

d0b-UUJEUU9HN1lCNXxVYTVsVVN5M3V0dnEyQlhaRDM3WQ

691 ms

css2

css2

32 ms

tp.gif

tp.gif

581 ms

jquery.js

jquery.js

824 ms

common.js

common.js

548 ms

index.js

index.js

970 ms

swiper.min.js

swiper.min.js

1337 ms

lazysizes.min.js

lazysizes.min.js

997 ms

so_sg.js

so_sg.js

111 ms

so_sg.js

so_sg.js

113 ms

iconHBtn.gif

iconHBtn.gif

553 ms

bgTop02.png

bgTop02.png

595 ms

btnNextTop.png

btnNextTop.png

878 ms

btnPrevTop.png

btnPrevTop.png

1026 ms

btnNextThumb.png

btnNextThumb.png

1050 ms

btnPrevThumb.png

btnPrevThumb.png

1068 ms

bgTop01.jpg

bgTop01.jpg

1448 ms

iconArrow01.png

iconArrow01.png

1396 ms

iconTel.png

iconTel.png

1399 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

17 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

23 ms

KFOlCnqEu92Fr1MmYUtvAw.ttf

KFOlCnqEu92Fr1MmYUtvAw.ttf

39 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISWaA.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISWaA.ttf

38 ms

locate

locate

665 ms

gtm.js

gtm.js

100 ms

ee863d4b8d59df22_5034.js

ee863d4b8d59df22_5034.js

39 ms

js

js

1049 ms

tracking.min.js

tracking.min.js

4 ms

sosync

sosync

221 ms

fbevents.js

fbevents.js

13 ms

gtm.js

gtm.js

42 ms

js

js

1245 ms

index.css

index.css

515 ms

33 ms

pixel

pixel

43 ms

v2

v2

7 ms

sync

sync

581 ms

sync

sync

23 ms

30 ms

pixel

pixel

13 ms

bgSearchImg01.png

bgSearchImg01.png

491 ms

bgSearchImg02.png

bgSearchImg02.png

491 ms

iconBtn01.gif

iconBtn01.gif

505 ms

iconBtn02.gif

iconBtn02.gif

506 ms

iconInstagram.gif

iconInstagram.gif

522 ms

swiper.min.css

swiper.min.css

608 ms

sosync

sosync

457 ms

segmentation.js

segmentation.js

131 ms

headerLogo.jpg

headerLogo.jpg

725 ms

pixel

pixel

21 ms

um

um

30 ms

Pug

Pug

25 ms

hs

hs

791 ms

tap.php

tap.php

28 ms

cnt

cnt

666 ms

sync

sync

929 ms

sd

sd

5 ms

22 ms

v2

v2

21 ms

15 ms

396846.gif

396846.gif

36 ms

pi346_list.jpg

pi346_list.jpg

1023 ms

pi337_list.jpg

pi337_list.jpg

1039 ms

sd

sd

6 ms

Pug

Pug

3 ms

tap.php

tap.php

3 ms

rep

rep

169 ms

beacon.html

beacon.html

7 ms

rep

rep

319 ms

sd

sd

11 ms

pixel

pixel

16 ms

tap.php

tap.php

4 ms

Pug

Pug

5 ms

set

set

272 ms

pixel

pixel

20 ms

sync

sync

668 ms

report

report

718 ms

bounce

bounce

27 ms

bgSearch.gif

bgSearch.gif

172 ms

sync

sync

268 ms

Accessibility Review

wow-h.jp accessibility score

95

Accessibility Issues

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.

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

Links do not have a discernible name

Best Practices

wow-h.jp best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

wow-h.jp SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Wow-h.jp 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 Wow-h.jp 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

wow-h.jp

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