Tools & Wizards About Us
panahome.jp screenshot

Report Summary

  • 0

    Performance

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

panahome.jp

【公式】パナソニック ホームズ（住宅・ハウスメーカー）-Panasonic

Page Load Speed

10.2 sec in total

First Response

567 ms

Resources Loaded

8.5 sec

Page Rendered

1.1 sec

panahome.jp screenshot

About Website

Visit panahome.jp now to see the best up-to-date Panahome content for Japan and also check out these interesting facts you probably never knew about panahome.jp

パナソニック ホームズの総合情報サイトです。戸建・注文住宅・賃貸住宅経営・土地活用・リフォーム・不動産流通など。「良家」づくりをめざして、大切な家族と暮らしを守り抜く「強さ」、幸せな毎日のための「暮らしやすさ」を探求し続けています。

Visit panahome.jp

Key Findings

We analyzed Panahome.jp page load time and found that the first response time was 567 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

panahome.jp performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value23.4 s

0/100

25%

SI (Speed Index)

Value17.0 s

0/100

10%

TBT (Total Blocking Time)

Value7,680 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1

2/100

15%

TTI (Time to Interactive)

Value49.4 s

0/100

10%

Network Requests Diagram

panahome.jp

567 ms

www.panahome.jp

698 ms

homes.panasonic.com

518 ms

gtm.js

46 ms

gtm.js

122 ms

Our browser made a total of 156 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Panahome.jp, 48% (75 requests) were made to Homes.panasonic.com and 13% (20 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Homes.panasonic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 676.4 kB (68%)

Content Size

996.4 kB

After Optimization

320.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Panahome.jp main page is 996.4 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. 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. Javascripts take 720.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 81.2 kB

  • Original 100.3 kB
  • After minification 90.3 kB
  • After compression 19.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 81.2 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 41 B

  • Original 10.2 kB
  • After minification 10.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. Panahome images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 455.5 kB

  • Original 720.1 kB
  • After minification 716.8 kB
  • After compression 264.6 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 455.5 kB or 63% of the original size.

CSS Optimization

-84%

Potential reduce by 139.6 kB

  • Original 165.8 kB
  • After minification 152.0 kB
  • After compression 26.2 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. Panahome.jp needs all CSS files to be minified and compressed as it can save up to 139.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 95 (86%)

Requests Now

111

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

panahome.jp

panahome.jp

567 ms

www.panahome.jp

www.panahome.jp

698 ms

homes.panasonic.com

homes.panasonic.com

518 ms

gtm.js

gtm.js

46 ms

gtm.js

gtm.js

122 ms

gtm.js

gtm.js

122 ms

gtm.js

gtm.js

187 ms

gtm.js

gtm.js

102 ms

gtm.js

gtm.js

121 ms

responsive_home.js

responsive_home.js

752 ms

slick.min.js

slick.min.js

1239 ms

top.min.js

top.min.js

253 ms

jquery.matchHeight.min.js

jquery.matchHeight.min.js

752 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

252 ms

common.min.js

common.min.js

684 ms

custom.js

custom.js

684 ms

local.min.js

local.min.js

684 ms

slick.css

slick.css

954 ms

slick-theme.css

slick-theme.css

953 ms

colorbox.css

colorbox.css

953 ms

phg_common.css

phg_common.css

953 ms

phg_common.js

phg_common.js

953 ms

phg_important_notice.min.js

phg_important_notice.min.js

1176 ms

js

js

66 ms

js

js

284 ms

js

js

441 ms

destination

destination

375 ms

ytag.js

ytag.js

1194 ms

core.js

core.js

436 ms

fbevents.js

fbevents.js

433 ms

destination

destination

427 ms

destination

destination

425 ms

destination

destination

429 ms

destination

destination

628 ms

destination

destination

626 ms

destination

destination

623 ms

local.css

local.css

995 ms

site_home.css

site_home.css

401 ms

site.js

site.js

390 ms

common.css

common.css

206 ms

basic.css

basic.css

239 ms

css2

css2

42 ms

css2

css2

58 ms

yakuhanmp-noto.min.css

yakuhanmp-noto.min.css

24 ms

basic.min.js

basic.min.js

195 ms

jquery_add.js

jquery_add.js

208 ms

jquery.js

jquery.js

398 ms

jquery-ui.js

jquery-ui.js

871 ms

jquery.scrollTo.js

jquery.scrollTo.js

190 ms

jquery_add.js

jquery_add.js

190 ms

businessmenu.min.js

businessmenu.min.js

206 ms

logo_panasonichomes.png

logo_panasonichomes.png

204 ms

img_g-bs.webp

img_g-bs.webp

616 ms

img_g-bb.webp

img_g-bb.webp

528 ms

img_g-bch.webp

img_g-bch.webp

361 ms

img_g-bn.webp

img_g-bn.webp

395 ms

img_g-br.webp

img_g-br.webp

368 ms

img_g-bre.webp

img_g-bre.webp

576 ms

img_g-bk.webp

img_g-bk.webp

556 ms

mv_tile_01_SP.webp

mv_tile_01_SP.webp

1016 ms

mv_tile_01_txt01_SP.svg

mv_tile_01_txt01_SP.svg

654 ms

mv_tile_01_mark.svg

mv_tile_01_mark.svg

732 ms

phg_important_notice.css

phg_important_notice.css

708 ms

important_notice.inc

important_notice.inc

879 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75g.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75g.woff

57 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75g.woff

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75g.woff

73 ms

bnr_vieuno.webp

bnr_vieuno.webp

1198 ms

bnr_fortina_selectpremium.webp

bnr_fortina_selectpremium.webp

1050 ms

bnr_stysafe.webp

bnr_stysafe.webp

1051 ms

bnr_web-event_20240512.webp

bnr_web-event_20240512.webp

1072 ms

bnr_sumai_jitsurei_20240511.webp

bnr_sumai_jitsurei_20240511.webp

1196 ms

bnr_lifesight.webp

bnr_lifesight.webp

2644 ms

bnr_lifeStyleMagazine202403.webp

bnr_lifeStyleMagazine202403.webp

1233 ms

bg_reform.webp

bg_reform.webp

1303 ms

bg_second.webp

bg_second.webp

1474 ms

bg_case01_sp.webp

bg_case01_sp.webp

2510 ms

bg_case02_sp.webp

bg_case02_sp.webp

1401 ms

bg_case03_sp.webp

bg_case03_sp.webp

1447 ms

bg_case04_sp.webp

bg_case04_sp.webp

1443 ms

bnr_owner_sp.webp

bnr_owner_sp.webp

1730 ms

bnr_consultation_sp.webp

bnr_consultation_sp.webp

1730 ms

icon_insta@2x.png

icon_insta@2x.png

1731 ms

icon_line@2x.png

icon_line@2x.png

1731 ms

icon_youtube@2x.png

icon_youtube@2x.png

1845 ms

bnr_SDGs.webp

bnr_SDGs.webp

1830 ms

bnr_LifeStyleMagazine.webp

bnr_LifeStyleMagazine.webp

1845 ms

group-icon01.webp

group-icon01.webp

1851 ms

group-icon02.webp

group-icon02.webp

2029 ms

cmt.js

cmt.js

388 ms

cdp.js

cdp.js

49 ms

dejam.js

dejam.js

391 ms

pmt.js

pmt.js

121 ms

uwt.js

uwt.js

28 ms

lt.js

lt.js

181 ms

bat.js

bat.js

36 ms

52017900.js

52017900.js

11 ms

adsct

adsct

103 ms

adsct

adsct

182 ms

52017900

52017900

32 ms

clarity.js

clarity.js

5 ms

im-uid.js

im-uid.js

6 ms

segment

segment

280 ms

index.js

index.js

1211 ms

get

get

261 ms

err.gif

err.gif

1002 ms

err.gif

err.gif

1000 ms

tag.js

tag.js

302 ms

bg_img01.webp

bg_img01.webp

3170 ms

bg_img02.webp

bg_img02.webp

1942 ms

bg_img03.webp

bg_img03.webp

2087 ms

bg_img04.webp

bg_img04.webp

1702 ms

icon__whatsnew__arrow__right.png

icon__whatsnew__arrow__right.png

1921 ms

ic_cmenu01.png

ic_cmenu01.png

1991 ms

ic_cmenu02.png

ic_cmenu02.png

2120 ms

ic_cmenu03.png

ic_cmenu03.png

2149 ms

pgd_icn-footer-arrow-up.gif

pgd_icn-footer-arrow-up.gif

2151 ms

YakuHanMP-Regular.woff

YakuHanMP-Regular.woff

134 ms

YakuHanMP-Medium.woff

YakuHanMP-Medium.woff

140 ms

YakuHanMP-Light.woff

YakuHanMP-Light.woff

149 ms

YakuHanMP-ExtraLight.woff

YakuHanMP-ExtraLight.woff

148 ms

YakuHanMP-SemiBold.woff

YakuHanMP-SemiBold.woff

148 ms

YakuHanMP-Bold.woff

YakuHanMP-Bold.woff

147 ms

YakuHanMP-Black.woff

YakuHanMP-Black.woff

147 ms

xn77YHs72GKoTvER4Gn3b5eMZCqNRk0.woff

xn77YHs72GKoTvER4Gn3b5eMZCqNRk0.woff

170 ms

12 ms

iframe_global_nav.css

iframe_global_nav.css

2006 ms

2111 ms

td.min.js

td.min.js

68 ms

lp.js

lp.js

88 ms

get_cookie_id

get_cookie_id

148 ms

ga.js

ga.js

14 ms

global.setting.js

global.setting.js

9 ms

lp.setting.js

lp.setting.js

3 ms

gwo.js

gwo.js

3 ms

pages.ready.js

pages.ready.js

3 ms

tags.track.js

tags.track.js

2 ms

load.body04.js

load.body04.js

91 ms

js

js

45 ms

web_pv_log

web_pv_log

714 ms

u

u

286 ms

rymouzxb

rymouzxb

287 ms

pixel.js

pixel.js

24 ms

p

p

688 ms

smallest.png

smallest.png

36 ms

rymouzxb

rymouzxb

69 ms

js

js

64 ms

loader.css

loader.css

193 ms

js

js

34 ms

chunk-vendors.js

chunk-vendors.js

102 ms

chunk-common.js

chunk-common.js

81 ms

iframe.js

iframe.js

67 ms

js

js

54 ms

analytics.js

analytics.js

33 ms

collect

collect

46 ms

collect

collect

13 ms

c.gif

c.gif

7 ms

Accessibility Review

panahome.jp accessibility score

74

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

panahome.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

panahome.jp SEO score

91

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 Panahome.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 Panahome.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

panahome.jp

Open Graph data is detected on the main page of Panahome. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: