Access shinoken.jp. シノケン｜アパート経営で100年時代をサポート

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.3 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

shinoken.jp

306 ms

www.shinoken.jp

498 ms

fw.css

1078 ms

common.css

1332 ms

style.css

310 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 84% of them (56 requests) were addressed to the original Shinoken.jp, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Shinoken.jp.

Content Size

2.1 MB

After Optimization

1.2 MB

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

HTML Optimization

-82%

Potential reduce by 40.6 kB

Original 49.3 kB
After minification 37.3 kB
After compression 8.7 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 12.0 kB, which is 24% 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 40.6 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 34.1 kB

Original 1.2 MB
After minification 1.1 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. Shinoken images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 190.4 kB

Original 281.7 kB
After minification 269.9 kB
After compression 91.3 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 190.4 kB or 68% of the original size.

CSS Optimization

-97%

Potential reduce by 575.8 kB

Original 594.8 kB
After minification 123.5 kB
After compression 19.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. Shinoken.jp needs all CSS files to be minified and compressed as it can save up to 575.8 kB or 97% of the original size.

Requests Now

After Optimization

The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shinoken. 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 as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

These are opportunities to improve the legibility of your content.

High

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

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.

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

High

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

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shinoken.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 Shinoken.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

shinoken.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

シノケン｜アパート経営で100年時代をサポート

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

shinoken.jp

www.shinoken.jp

fw.css

common.css

style.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

shinoken.jp

www.shinoken.jp

fw.css

common.css

style.css

load.js

gSearch.js

conveyor.js

slick.min.js

js

jquery.1.11.1.js

jquery.easing.js

jquery.j_spMenu.min.js

jquery.j_toggle.min.js

jquery.j_modal.min.js

jquery.j_autoHeight.min.js

jquery.j_delayLoader.js

fw.js

common.js

logo.png

contact_hour.png

contact_tel.png

visual_img_sp.png

loader.gif

icon_line_home.png

apart_illust_01.png

apart_illust_02.png

apart_illust_03.png

apart_illust_04.png

reason_illust_01.png

reason_illust_02.png

reason_illust_03.png

reason_illust_04.png

case_01.jpg

case_02.jpg

case_04.jpg

case_03.jpg

case_05.jpg

design_img_01.jpg

voice_img_01.jpg

voice_img_01.jpg

voice_img_01.jpg

voice_img_01.jpg