Tools & Wizards About Us
iizukafudousan.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

iizukafudousan.co.jp

下総中山の賃貸・不動産【飯塚不動産】にお任せください！　

Page Load Speed

6 sec in total

First Response

850 ms

Resources Loaded

4.9 sec

Page Rendered

268 ms

iizukafudousan.co.jp screenshot

About Website

Welcome to iizukafudousan.co.jp homepage info - get ready to check Iizukafudousan best content right away, or after learning these important things about iizukafudousan.co.jp

下総中山の賃貸、船橋市・市川市の賃貸・売買は【飯塚不動産】へ！スタイリッシュな新築物件も多数ご用意！ご要望にぴったりのお部屋をご紹介いたします。住まい探しから駐車場までお気軽にご相談ください！

Visit iizukafudousan.co.jp

Key Findings

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

Performance Metrics

iizukafudousan.co.jp performance score

0

Network Requests Diagram

iizukafudousan.co.jp

850 ms

scripts.php

555 ms

prototype.js

1365 ms

scriptaculous.js

540 ms

js

23 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 17% of them (19 requests) were addressed to the original Iizukafudousan.co.jp, 35% (39 requests) were made to Hpbegin.jp and 29% (32 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Iizukafudousan.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 799.4 kB (29%)

Content Size

2.7 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iizukafudousan.co.jp main page is 2.7 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. 65% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 44.5 kB

  • Original 53.6 kB
  • After minification 51.9 kB
  • After compression 9.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. 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 44.5 kB or 83% of the original size.

Image Optimization

-11%

Potential reduce by 198.1 kB

  • Original 1.9 MB
  • After minification 1.7 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. Obviously, Iizukafudousan needs image optimization as it can save up to 198.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 547.4 kB

  • Original 783.1 kB
  • After minification 714.0 kB
  • After compression 235.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 547.4 kB or 70% of the original size.

CSS Optimization

-76%

Potential reduce by 9.4 kB

  • Original 12.3 kB
  • After minification 9.9 kB
  • After compression 2.9 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. Iizukafudousan.co.jp needs all CSS files to be minified and compressed as it can save up to 9.4 kB or 76% of the original size.

Requests Breakdown

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

Requests Now

105

After Optimization

68

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iizukafudousan.co.jp

iizukafudousan.co.jp

850 ms

scripts.php

scripts.php

555 ms

prototype.js

prototype.js

1365 ms

scriptaculous.js

scriptaculous.js

540 ms

js

js

23 ms

backtotop.js

backtotop.js

553 ms

lightbox.css

lightbox.css

558 ms

main.css

main.css

558 ms

style.css

style.css

592 ms

effects.js

effects.js

372 ms

builder.js

builder.js

170 ms

01310.jpg

01310.jpg

198 ms

header.gif

header.gif

186 ms

line1.gif

line1.gif

169 ms

cartview.gif

cartview.gif

178 ms

tabmenu_back.jpg

tabmenu_back.jpg

203 ms

menu_b1.gif

menu_b1.gif

185 ms

menu_b3.gif

menu_b3.gif

186 ms

menu_b4.gif

menu_b4.gif

336 ms

menu_b5.gif

menu_b5.gif

352 ms

whatsnew.gif

whatsnew.gif

367 ms

companyinfo_top.gif

companyinfo_top.gif

369 ms

companyinfo_bottom.gif

companyinfo_bottom.gif

369 ms

companyinfo_1.gif

companyinfo_1.gif

404 ms

companyinfo_2.gif

companyinfo_2.gif

506 ms

companyinfo_3.gif

companyinfo_3.gif

527 ms

Links.gif

Links.gif

549 ms

LiskMark.png

LiskMark.png

552 ms

contents_box_top.gif

contents_box_top.gif

553 ms

contents_box_bottom.gif

contents_box_bottom.gif

606 ms

contents_box_mid.gif

contents_box_mid.gif

673 ms

message_top.gif

message_top.gif

702 ms

message_bottom.gif

message_bottom.gif

729 ms

message_mid.gif

message_mid.gif

736 ms

c_e_tokusen.gif

c_e_tokusen.gif

736 ms

recomend_titleback.gif

recomend_titleback.gif

807 ms

noImage.png

noImage.png

840 ms

other_search_back.jpg

other_search_back.jpg

876 ms

newmap.gif

newmap.gif

910 ms

backtotop.gif

backtotop.gif

919 ms

footer_line.gif

footer_line.gif

920 ms

ft-bg.jpg

ft-bg.jpg

1008 ms

00129728_1.jpg

00129728_1.jpg

740 ms

00129723_1.jpg

00129723_1.jpg

903 ms

00129731_1.jpg

00129731_1.jpg

969 ms

00129732_1.jpg

00129732_1.jpg

938 ms

00129739_1.jpg

00129739_1.jpg

1330 ms

00129747_1.jpg

00129747_1.jpg

1330 ms

00129745_1.jpg

00129745_1.jpg

1109 ms

00129733_1.jpg

00129733_1.jpg

1264 ms

00129737_1.jpg

00129737_1.jpg

1312 ms

00129730_1.jpg

00129730_1.jpg

1362 ms

00129743_2.jpg

00129743_2.jpg

1297 ms

00129718_1.jpg

00129718_1.jpg

1622 ms

00129694_1.jpg

00129694_1.jpg

1670 ms

00129661_1.jpg

00129661_1.jpg

1685 ms

00130084_1.jpg

00130084_1.jpg

1711 ms

ga.js

ga.js

5 ms

common.js

common.js

9 ms

map.js

map.js

8 ms

_markers.php

_markers.php

252 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

293 ms

util.js

util.js

19 ms

onion.js

onion.js

19 ms

openhand_8_8.cur

openhand_8_8.cur

44 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

116 ms

stats.js

stats.js

33 ms

controls.js

controls.js

28 ms

transparent.png

transparent.png

24 ms

css

css

52 ms

google4.png

google4.png

39 ms

marker.js

marker.js

27 ms

mapcnt6.png

mapcnt6.png

52 ms

sv5.png

sv5.png

52 ms

tmapctrl.png

tmapctrl.png

32 ms

cb_scout5.png

cb_scout5.png

31 ms

tmapctrl4.png

tmapctrl4.png

31 ms

imgs8.png

imgs8.png

30 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

24 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

25 ms

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

25 ms

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

25 ms

vt

vt

68 ms

vt

vt

56 ms

vt

vt

73 ms

vt

vt

71 ms

vt

vt

74 ms

vt

vt

91 ms

vt

vt

105 ms

vt

vt

116 ms

vt

vt

129 ms

vt

vt

147 ms

vt

vt

125 ms

vt

vt

139 ms

vt

vt

161 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

56 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

235 ms

mm_20_blue.png

mm_20_blue.png

373 ms

vt

vt

75 ms

infowindow.js

infowindow.js

9 ms

vt

vt

8 ms

vt

vt

5 ms

vt

vt

9 ms

vt

vt

14 ms

vt

vt

14 ms

vt

vt

11 ms

vt

vt

16 ms

vt

vt

19 ms

vt

vt

17 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

190 ms

SEO Factors

iizukafudousan.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iizukafudousan.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Iizukafudousan.co.jp 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

iizukafudousan.co.jp

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