Tools & Wizards About Us
freshhouse.jp screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

freshhouse.jp

ドメインパーキング

Page Load Speed

28.6 sec in total

First Response

360 ms

Resources Loaded

27.5 sec

Page Rendered

743 ms

freshhouse.jp screenshot

About Website

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

リフォームするならフレッシュハウス

Visit freshhouse.jp

Key Findings

We analyzed Freshhouse.jp page load time and found that the first response time was 360 ms and then it took 28.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

freshhouse.jp performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value1.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.7 s

100/100

10%

Network Requests Diagram

freshhouse.jp

360 ms

freshhouse.jp

1371 ms

jquery.flexslider.css

316 ms

idangerous.swiper.css

430 ms

idangerous.swiper.scrollbar.css

553 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 85% of them (68 requests) were addressed to the original Freshhouse.jp, 3% (2 requests) were made to Js.ptengine.jp and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Freshhouse.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 762.5 kB (51%)

Content Size

1.5 MB

After Optimization

719.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Freshhouse.jp main page is 1.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. 45% of websites need less resources to load. Images take 946.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 50.2 kB

  • Original 60.3 kB
  • After minification 52.1 kB
  • After compression 10.1 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 8.2 kB, which is 14% 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 50.2 kB or 83% of the original size.

Image Optimization

-40%

Potential reduce by 380.6 kB

  • Original 946.8 kB
  • After minification 566.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. Obviously, Freshhouse needs image optimization as it can save up to 380.6 kB or 40% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-61%

Potential reduce by 194.3 kB

  • Original 316.4 kB
  • After minification 300.7 kB
  • After compression 122.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 194.3 kB or 61% of the original size.

CSS Optimization

-86%

Potential reduce by 137.4 kB

  • Original 158.8 kB
  • After minification 122.5 kB
  • After compression 21.5 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. Freshhouse.jp needs all CSS files to be minified and compressed as it can save up to 137.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (42%)

Requests Now

74

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

freshhouse.jp

freshhouse.jp

360 ms

freshhouse.jp

freshhouse.jp

1371 ms

jquery.flexslider.css

jquery.flexslider.css

316 ms

idangerous.swiper.css

idangerous.swiper.css

430 ms

idangerous.swiper.scrollbar.css

idangerous.swiper.scrollbar.css

553 ms

common.css

common.css

690 ms

form.css

form.css

1112 ms

layout.css

layout.css

2467 ms

jquery.min.js

jquery.min.js

2873 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

2113 ms

jquery.scrollTo.js

jquery.scrollTo.js

2113 ms

jQueryAutoHeight.js

jQueryAutoHeight.js

2220 ms

jquery.imagesloaded.js

jquery.imagesloaded.js

2449 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

2453 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

2577 ms

idangerous.swiper-2.1.min.js

idangerous.swiper-2.1.min.js

3664 ms

idangerous.swiper.scrollbar-2.1.js

idangerous.swiper.scrollbar-2.1.js

2838 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

2934 ms

common.js

common.js

3845 ms

adlpo.js

adlpo.js

4264 ms

rollover.js

rollover.js

3129 ms

conversion.js

conversion.js

242 ms

s_retargeting.js

s_retargeting.js

1101 ms

body_bg.png

body_bg.png

707 ms

clear.gif

clear.gif

111 ms

logo_n150409.png

logo_n150409.png

466 ms

icons.png

icons.png

1305 ms

339652908a0f20cf1ba4dc10ddd9c047.jpg

339652908a0f20cf1ba4dc10ddd9c047.jpg

2744 ms

reform_bath.png

reform_bath.png

1149 ms

be1be4383ef21f7f0ddc18de9aa5c615.jpg

be1be4383ef21f7f0ddc18de9aa5c615.jpg

5199 ms

reform_kitchen.png

reform_kitchen.png

1007 ms

03d7d1acbe6d5c50043ba27dda55555e.jpg

03d7d1acbe6d5c50043ba27dda55555e.jpg

2746 ms

reform_toilet.png

reform_toilet.png

1452 ms

35d13a924acf679564f83c0ad4192799.jpg

35d13a924acf679564f83c0ad4192799.jpg

4731 ms

reform_exterior.png

reform_exterior.png

1938 ms

DSC01261.jpg

DSC01261.jpg

20427 ms

reform_fullreform.png

reform_fullreform.png

2358 ms

54a06a9d804ce9e76a2a2890ebefe1cd.jpg

54a06a9d804ce9e76a2a2890ebefe1cd.jpg

3639 ms

reform_interior.png

reform_interior.png

3087 ms

3247f25311030a199a1440037e092246.jpg

3247f25311030a199a1440037e092246.jpg

4712 ms

reform_washstand.png

reform_washstand.png

3463 ms

fhp-on-anime.gif

fhp-on-anime.gif

3954 ms

prize3.jpg

prize3.jpg

4072 ms

prize2.jpg

prize2.jpg

4314 ms

prize1.jpg

prize1.jpg

4584 ms

reform_icon_next.png

reform_icon_next.png

4937 ms

reform_waterheater.png

reform_waterheater.png

5022 ms

reform_outerwall.png

reform_outerwall.png

5144 ms

reform_outside.png

reform_outside.png

5158 ms

reform_other.png

reform_other.png

5465 ms

shops.png

shops.png

5915 ms

pagetop.png

pagetop.png

5682 ms

decoration_pic01.png

decoration_pic01.png

5680 ms

decoration_pic02.png

decoration_pic02.png

5714 ms

bnr_sonpo_150409.jpg

bnr_sonpo_150409.jpg

5837 ms

piwik.php

piwik.php

6856 ms

fhp-off.jpg

fhp-off.jpg

6425 ms

prize3off.jpg

prize3off.jpg

6055 ms

prize2off.jpg

prize2off.jpg

6068 ms

pta.js

pta.js

1180 ms

analytics.js

analytics.js

250 ms

270 ms

prize1off.jpg

prize1off.jpg

6318 ms

c.js

c.js

1241 ms

collect

collect

99 ms

260 ms

onelinenews_bg.png

onelinenews_bg.png

6853 ms

collect

collect

185 ms

ga-audiences

ga-audiences

19 ms

h2_basic_bg.gif

h2_basic_bg.gif

6117 ms

newsrelease_date_bg.gif

newsrelease_date_bg.gif

5887 ms

h3_basic_bg.gif

h3_basic_bg.gif

5730 ms

7486f4a8.js

7486f4a8.js

378 ms

bg_topline.png

bg_topline.png

5744 ms

categorynav_bg.png

categorynav_bg.png

6132 ms

pn

pn

1208 ms

blindpanel_mask.png

blindpanel_mask.png

5201 ms

pc_topblindpanel_next.png

pc_topblindpanel_next.png

4794 ms

sp_form.css

sp_form.css

342 ms

sp_layout.css

sp_layout.css

860 ms

Accessibility Review

freshhouse.jp accessibility score

68

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

Best Practices

freshhouse.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

freshhouse.jp SEO score

54

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freshhouse.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Freshhouse.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

freshhouse.jp

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