Access tokaidoor.co.jp. マンションの玄関に家族の安全を守る対震ドア2DOORデレマース

name

value

score

weighting

FCP (First Contentful Paint)

Value8.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.3 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value900 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.253

49/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

tokaidoor.co.jp

640 ms

969 ms

js

86 ms

bxi.css

180 ms

index_html.css

356 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Tokaidoor.co.jp, 69% (68 requests) were made to Taishindoor.com and 6% (6 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Taishindoor.com.

Content Size

5.5 MB

After Optimization

5.3 MB

In fact, the total size of Tokaidoor.co.jp main page is 5.5 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 5.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 30.0 kB

Original 36.5 kB
After minification 33.0 kB
After compression 6.6 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 30.0 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 104.2 kB

Original 5.1 MB
After minification 5.0 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. Tokaidoor images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 56.3 kB

Original 233.2 kB
After minification 233.2 kB
After compression 176.9 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 56.3 kB or 24% of the original size.

CSS Optimization

-27%

Potential reduce by 30.7 kB

Original 114.1 kB
After minification 114.0 kB
After compression 83.4 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. Tokaidoor.co.jp needs all CSS files to be minified and compressed as it can save up to 30.7 kB or 27% of the original size.

Requests Now

After Optimization

The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tokaidoor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 29 to 1 for CSS 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 input fields do not have accessible names

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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 experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

JA
Encoding

UTF-8

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

tokaidoor.co.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

マンションの玄関に家族の安全を守る対震ドア2DOORデレマース

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

tokaidoor.co.jp

js

bxi.css

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

tokaidoor.co.jp

js

bxi.css

index_html.css

common_style.css

style.css

top.css

jquery-1.12.0.min.js

ajaxzip3.js

bxi.js

jquery.mousewheel-3.0.6.pack.js

picturefill.js

ofi.min.js

ofi.js

modaal.min.js

modaal.css

jquery.fancybox.js

jquery.fancybox.min.js

jquery.fancybox.min.css

jquery.fancybox.css

easing.1.3.js

fitvids.js

bxslider.min.js

bxslider.css

zdo_drawer_menu.js

jquery.meanmenu.min.js

meanmenu.css

masonry.pkgd.min.js

jquery.magnific-popup.min.js

magnific-popup.css

jquery.tile.min.js

jquery.sidr.min.js

jquery.sidr.dark.css

font-awesome.min.css

all.css

all.css

slick.css

slick-theme.css

slick.min.js

jquery.fadethis.min.js

function.js

jquery.mCustomScrollbar.min.css

vue.min.js

jquery.mCustomScrollbar.concat.min.js