Tools & Wizards About Us
inaken.jp screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

inaken.jp

解体工事･リフォーム･新築工事土地探しの㈱イナケン - 静岡県西部を中心に全国対応の総合建設業 -

Page Load Speed

7.2 sec in total

First Response

1.5 sec

Resources Loaded

5.6 sec

Page Rendered

175 ms

inaken.jp screenshot

About Website

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

静岡県浜松市の建設事業（事業用店舗・事務所、土木、解体工事、住宅の新築・リフォーム）、不動産業の株式会社イナケンのホームページです。

Visit inaken.jp

Key Findings

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

Performance Metrics

inaken.jp performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.034

100/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

Network Requests Diagram

inaken.jp

1488 ms

css

21 ms

style.css

345 ms

style-ayatori.css.php

1006 ms

media-queries.css

547 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 73% of them (36 requests) were addressed to the original Inaken.jp, 4% (2 requests) were made to Connect.facebook.net and 4% (2 requests) were made to B92.yahoo.co.jp. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Inaken.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 206.5 kB (27%)

Content Size

767.6 kB

After Optimization

561.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inaken.jp main page is 767.6 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 360.2 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 24.7 kB

  • Original 33.8 kB
  • After minification 32.6 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 24.7 kB or 73% of the original size.

Image Optimization

-7%

Potential reduce by 19.1 kB

  • Original 282.7 kB
  • After minification 263.6 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. Inaken images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 86.5 kB

  • Original 360.2 kB
  • After minification 352.8 kB
  • After compression 273.7 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 86.5 kB or 24% of the original size.

CSS Optimization

-84%

Potential reduce by 76.2 kB

  • Original 90.9 kB
  • After minification 64.8 kB
  • After compression 14.6 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. Inaken.jp needs all CSS files to be minified and compressed as it can save up to 76.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (85%)

Requests Now

46

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

inaken.jp

inaken.jp

1488 ms

css

css

21 ms

style.css

style.css

345 ms

style-ayatori.css.php

style-ayatori.css.php

1006 ms

media-queries.css

media-queries.css

547 ms

fancybox.css

fancybox.css

545 ms

jquery.js

jquery.js

1267 ms

all.js

all.js

13 ms

default.css

default.css

711 ms

frame.css

frame.css

363 ms

header.css

header.css

731 ms

footer.css

footer.css

563 ms

main.css

main.css

1085 ms

side.css

side.css

913 ms

widgets.css

widgets.css

1186 ms

wordpress.css

wordpress.css

1064 ms

form.css

form.css

1082 ms

s_retargeting.js

s_retargeting.js

332 ms

jquery.fancybox.js

jquery.fancybox.js

1598 ms

jquery-ui.min.js

jquery-ui.min.js

35 ms

js

js

42 ms

jquery.gmap3.js

jquery.gmap3.js

1282 ms

jquery.cookie.js

jquery.cookie.js

1423 ms

jqueryAutoHeight.js

jqueryAutoHeight.js

1431 ms

controls.js

controls.js

1623 ms

s_retargeting.js

s_retargeting.js

669 ms

all.js

all.js

45 ms

ga.js

ga.js

46 ms

hb-tel.png

hb-tel.png

343 ms

hb-line.png

hb-line.png

435 ms

hb-search.png

hb-search.png

563 ms

hb-font-minus.png

hb-font-minus.png

576 ms

hb-font-reset.png

hb-font-reset.png

704 ms

hb-font-plus.png

hb-font-plus.png

744 ms

hb-bt-rss.png

hb-bt-rss.png

770 ms

grd-white.png

grd-white.png

781 ms

ptn-border1px-white.png

ptn-border1px-white.png

908 ms

logo.png

logo.png

939 ms

TOP11.jpg

TOP11.jpg

2692 ms

blockquote.png

blockquote.png

1103 ms

20eb23318ce8303aab49c29859de343c.jpg

20eb23318ce8303aab49c29859de343c.jpg

1458 ms

dotted.gif

dotted.gif

1102 ms

SlGVmQWMvZQIdix7AFxXkHNSaA.ttf

SlGVmQWMvZQIdix7AFxXkHNSaA.ttf

40 ms

58 ms

__utm.gif

__utm.gif

14 ms

footer-ayatori-in.png

footer-ayatori-in.png

1185 ms

plusone.js

plusone.js

18 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

20 ms

print-all.css

print-all.css

183 ms

Accessibility Review

inaken.jp accessibility score

59

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

inaken.jp SEO score

83

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

High

robots.txt is not valid

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

inaken.jp

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