Tools & Wizards About Us
famitei.net screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 78

    SEO

    Google-friendlier than
    40% of websites

famitei.net

大阪で外構エクステリア庭工事　施工例13727件公開中／大阪２店舗

Page Load Speed

10.4 sec in total

First Response

1.8 sec

Resources Loaded

8.1 sec

Page Rendered

477 ms

famitei.net screenshot

About Website

Welcome to famitei.net homepage info - get ready to check Famitei best content for Japan right away, or after learning these important things about famitei.net

大阪市2244件／豊中市576件／箕面市455件／高槻市566件／吹田市469件／東大阪市495件／池田市211件／寝屋川市292件／大東市160件／守口市137件／摂津市88件／四條畷市108件／他市も実績豊富

Visit famitei.net

Key Findings

We analyzed Famitei.net page load time and found that the first response time was 1.8 sec and then it took 8.6 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

famitei.net performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.382

27/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

famitei.net

1787 ms

prototype.js

1397 ms

scriptaculous.js

371 ms

dw.js

370 ms

inq.js

555 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 67% of them (55 requests) were addressed to the original Famitei.net, 11% (9 requests) were made to Famitei.co.jp and 7% (6 requests) were made to Famitei.jp. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Famitei.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 401.8 kB (52%)

Content Size

769.0 kB

After Optimization

367.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Famitei.net main page is 769.0 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. 40% of websites need less resources to load. Javascripts take 385.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 42.2 kB

  • Original 52.7 kB
  • After minification 48.1 kB
  • After compression 10.5 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 42.2 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 18.0 kB

  • Original 283.9 kB
  • After minification 265.9 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. Famitei images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 300.1 kB

  • Original 385.7 kB
  • After minification 299.2 kB
  • After compression 85.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 300.1 kB or 78% of the original size.

CSS Optimization

-89%

Potential reduce by 41.5 kB

  • Original 46.7 kB
  • After minification 35.9 kB
  • After compression 5.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. Famitei.net needs all CSS files to be minified and compressed as it can save up to 41.5 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (25%)

Requests Now

81

After Optimization

61

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

famitei.net

famitei.net

1787 ms

prototype.js

prototype.js

1397 ms

scriptaculous.js

scriptaculous.js

371 ms

dw.js

dw.js

370 ms

inq.js

inq.js

555 ms

smoothScroll.js

smoothScroll.js

621 ms

top.css

top.css

977 ms

rightBlock.js

rightBlock.js

359 ms

builder.js

builder.js

495 ms

effects.js

effects.js

827 ms

dragdrop.js

dragdrop.js

855 ms

controls.js

controls.js

864 ms

slider.js

slider.js

529 ms

sound.js

sound.js

409 ms

analytics.js

analytics.js

54 ms

l_035369_s.jpg

l_035369_s.jpg

636 ms

user_voice2.gif

user_voice2.gif

646 ms

Logo_25wht.gif

Logo_25wht.gif

51 ms

00020667_01.jpg

00020667_01.jpg

622 ms

00020640_01.jpg

00020640_01.jpg

737 ms

00020654_01.jpg

00020654_01.jpg

786 ms

00020609_01.jpg

00020609_01.jpg

847 ms

l_035983.jpg

l_035983.jpg

1262 ms

00020666_01.jpg

00020666_01.jpg

732 ms

00020663_01.jpg

00020663_01.jpg

1331 ms

00020662_01.jpg

00020662_01.jpg

1352 ms

l_035218_s.jpg

l_035218_s.jpg

785 ms

l_034636_s.jpg

l_034636_s.jpg

822 ms

l_035475_s.jpg

l_035475_s.jpg

729 ms

all.js

all.js

44 ms

info_after.gif

info_after.gif

1184 ms

formjob185.gif

formjob185.gif

765 ms

net_header_new3.gif

net_header_new3.gif

1520 ms

net_header_moji.gif

net_header_moji.gif

1140 ms

net_header_ul03_2016.gif

net_header_ul03_2016.gif

1605 ms

net_header_ul03_kouji_2016.gif

net_header_ul03_kouji_2016.gif

1696 ms

net_header_ul04_1.gif

net_header_ul04_1.gif

1795 ms

net_head.gif

net_head.gif

1641 ms

net_side_minamiosaka.gif

net_side_minamiosaka.gif

1854 ms

cont_top1.gif

cont_top1.gif

1898 ms

cont_top1_b.gif

cont_top1_b.gif

2392 ms

jp_cnt.gif

jp_cnt.gif

2358 ms

top_pr3_under.gif

top_pr3_under.gif

2041 ms

top_pr1_under.gif

top_pr1_under.gif

2165 ms

top_pr2_under.gif

top_pr2_under.gif

2211 ms

top_pr4_under.gif

top_pr4_under.gif

2251 ms

title03.gif

title03.gif

2382 ms

top_sarea.gif

top_sarea.gif

2575 ms

jp_side_new.gif

jp_side_new.gif

2741 ms

menu_list.jpg

menu_list.jpg

2641 ms

jp_side_bk.jpg

jp_side_bk.jpg

2713 ms

jp_side_end.gif

jp_side_end.gif

2783 ms

reformclub.gif

reformclub.gif

3197 ms

jp_rside_branko.gif

jp_rside_branko.gif

3251 ms

jp_form.jpg

jp_form.jpg

980 ms

banner180_com.gif

banner180_com.gif

740 ms

mobi180.gif

mobi180.gif

779 ms

rehome180.gif

rehome180.gif

778 ms

dt-record2.gif

dt-record2.gif

598 ms

dt-record.gif

dt-record.gif

687 ms

jp_footer.jpg

jp_footer.jpg

3052 ms

footer_top.gif

footer_top.gif

2497 ms

footer_shop.gif

footer_shop.gif

3043 ms

00018694_07.jpg

00018694_07.jpg

2740 ms

00018256_05.jpg

00018256_05.jpg

3045 ms

00018041_13.jpg

00018041_13.jpg

3187 ms

footer_commobi.gif

footer_commobi.gif

666 ms

dotline-bg.gif

dotline-bg.gif

376 ms

00017906_12.jpg

00017906_12.jpg

3248 ms

linkid.js

linkid.js

82 ms

00017981_08.jpg

00017981_08.jpg

3156 ms

92 ms

collect

collect

13 ms

collect

collect

91 ms

00017987_17.jpg

00017987_17.jpg

3409 ms

00017663_06.jpg

00017663_06.jpg

3524 ms

xd_arbiter.php

xd_arbiter.php

58 ms

xd_arbiter.php

xd_arbiter.php

67 ms

00017196_09.jpg

00017196_09.jpg

3682 ms

00016778_09.jpg

00016778_09.jpg

3229 ms

00016777_07.jpg

00016777_07.jpg

3144 ms

ping

ping

42 ms

Accessibility Review

famitei.net accessibility score

79

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

famitei.net 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

famitei.net SEO score

78

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

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

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

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Famitei.net 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 Famitei.net main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

famitei.net

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