Tools & Wizards About Us
okamotogikou.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

okamotogikou.com

プレハブ建築・ユニットハウスの施工販売｜オカモト技工

Page Load Speed

8.1 sec in total

First Response

600 ms

Resources Loaded

7.3 sec

Page Rendered

265 ms

okamotogikou.com screenshot

About Website

Click here to check amazing Okamotogikou content for Japan. Otherwise, check out these important facts you probably never knew about okamotogikou.com

理想のプレハブハウス・ユニットハウスなどプレハブ建築をお考えならプレハブのオカモト技工へ。事務所・倉庫用・工場用のプレハブなど豊富な種類のプレハブ製品情報を掲載。安心価格でご購入いただけます。お見積りは無料！他社と比較下さい。リフォームや外構工事もお任せ下さい。

Visit okamotogikou.com

Key Findings

We analyzed Okamotogikou.com page load time and found that the first response time was 600 ms and then it took 7.5 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

okamotogikou.com performance score

0

Network Requests Diagram

okamotogikou.com

600 ms

www.okamotogikou.com

1504 ms

import1.css

350 ms

jquery.min.js

27 ms

craftyslide.min.js

392 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 96% of them (73 requests) were addressed to the original Okamotogikou.com, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Okamotogikou.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 49.4 kB (8%)

Content Size

604.9 kB

After Optimization

555.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Okamotogikou.com main page is 604.9 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. 25% of websites need less resources to load. Images take 536.3 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 13.1 kB

  • Original 18.2 kB
  • After minification 17.6 kB
  • After compression 5.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 13.1 kB or 72% of the original size.

Image Optimization

-2%

Potential reduce by 9.3 kB

  • Original 536.3 kB
  • After minification 527.0 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. Okamotogikou images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 2.3 kB

  • Original 20.7 kB
  • After minification 19.6 kB
  • After compression 18.4 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 2.3 kB or 11% of the original size.

CSS Optimization

-83%

Potential reduce by 24.7 kB

  • Original 29.7 kB
  • After minification 20.4 kB
  • After compression 5.0 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. Okamotogikou.com needs all CSS files to be minified and compressed as it can save up to 24.7 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

74

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

okamotogikou.com

okamotogikou.com

600 ms

www.okamotogikou.com

www.okamotogikou.com

1504 ms

import1.css

import1.css

350 ms

jquery.min.js

jquery.min.js

27 ms

craftyslide.min.js

craftyslide.min.js

392 ms

slideshow.js

slideshow.js

393 ms

jscount.cgi

jscount.cgi

389 ms

mail.js

mail.js

369 ms

acc.js

acc.js

371 ms

ga.js

ga.js

385 ms

default.css

default.css

390 ms

side1.css

side1.css

437 ms

user.css

user.css

719 ms

navi.css

navi.css

713 ms

top.css

top.css

732 ms

tag.css

tag.css

753 ms

tel.gif

tel.gif

379 ms

logo.gif

logo.gif

207 ms

h_01.gif

h_01.gif

348 ms

h_02.gif

h_02.gif

391 ms

h_03.gif

h_03.gif

380 ms

h_04.gif

h_04.gif

387 ms

h_05.gif

h_05.gif

590 ms

post.gif

post.gif

911 ms

area.gif

area.gif

737 ms

slide1.jpg

slide1.jpg

1105 ms

slide2.jpg

slide2.jpg

1109 ms

slide3.jpg

slide3.jpg

990 ms

h_3bg.gif

h_3bg.gif

914 ms

bg_waku.gif

bg_waku.gif

1054 ms

t_prefab.gif

t_prefab.gif

1258 ms

prefab_01.jpg

prefab_01.jpg

1274 ms

prefab_02.jpg

prefab_02.jpg

1345 ms

prefab_03.jpg

prefab_03.jpg

1420 ms

prefab_04.jpg

prefab_04.jpg

1436 ms

prefab_05.jpg

prefab_05.jpg

1456 ms

prefab_06.jpg

prefab_06.jpg

1612 ms

prefab_07.jpg

prefab_07.jpg

1653 ms

prefab_08.jpg

prefab_08.jpg

1702 ms

topics.jpg

topics.jpg

1811 ms

mitsumori.gif

mitsumori.gif

1982 ms

mail1.gif

mail1.gif

1846 ms

fax1.gif

fax1.gif

1990 ms

t_exterior.gif

t_exterior.gif

2009 ms

exteria_01.jpg

exteria_01.jpg

2070 ms

exteria_02.jpg

exteria_02.jpg

2191 ms

exteria_03.jpg

exteria_03.jpg

2207 ms

t_reform.gif

t_reform.gif

2369 ms

reform_01.jpg

reform_01.jpg

2381 ms

reform_02.jpg

reform_02.jpg

2535 ms

pre.gif

pre.gif

2456 ms

prean01.jpg

prean01.jpg

2547 ms

ga.js

ga.js

10 ms

__utm.gif

__utm.gif

14 ms

tyukan.jpg

tyukan.jpg

2401 ms

prean02.jpg

prean02.jpg

2445 ms

exteria.gif

exteria.gif

2408 ms

exteria01.jpg

exteria01.jpg

2490 ms

exteria02.jpg

exteria02.jpg

2539 ms

reform.gif

reform.gif

2547 ms

reform01.jpg

reform01.jpg

2364 ms

reform02.jpg

reform02.jpg

2411 ms

annai.gif

annai.gif

2240 ms

blog.jpg

blog.jpg

2299 ms

jirei.gif

jirei.gif

2326 ms

0034-610x457.jpg

0034-610x457.jpg

2597 ms

12-610x348.jpg

12-610x348.jpg

2377 ms

002-610x457.jpg

002-610x457.jpg

2780 ms

001-610x377.jpg

001-610x377.jpg

2429 ms

0262-610x457.jpg

0262-610x457.jpg

2640 ms

btn_jirei.jpg

btn_jirei.jpg

2305 ms

bg_swaku.gif

bg_swaku.gif

2378 ms

wakuh_5.gif

wakuh_5.gif

2605 ms

h_6bg.gif

h_6bg.gif

2587 ms

acclog.cgi

acclog.cgi

2521 ms

print.css

print.css

185 ms

SEO Factors

okamotogikou.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Okamotogikou.com 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 Okamotogikou.com main page’s claimed encoding is shift_jis. 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

okamotogikou.com

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