Access kabe.xyz. 壁紙も自分で張ってDIYできる。おしゃれ壁紙・クロスの通販サイト

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value20.1 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value870 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.387

27/100

15%

TTI (Time to Interactive)

Value18.3 s

3/100

10%

kabe.xyz

292 ms

kabe.tomoyasu.co.jp

1052 ms

com_common.css

423 ms

com_base.css

430 ms

com_style.css

713 ms

Our browser made a total of 153 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Kabe.xyz, 74% (113 requests) were made to Kabe.tomoyasu.co.jp and 14% (22 requests) were made to Styledart.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Styledart.com.

Content Size

14.5 MB

After Optimization

13.9 MB

In fact, the total size of Kabe.xyz main page is 14.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 14.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 81.1 kB

Original 96.6 kB
After minification 75.3 kB
After compression 15.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. This page needs HTML code to be minified as it can gain 21.4 kB, which is 22% 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 81.1 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 242.8 kB

Original 14.0 MB
After minification 13.8 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. Kabe images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 79.5 kB

Original 168.8 kB
After minification 165.0 kB
After compression 89.2 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 79.5 kB or 47% of the original size.

CSS Optimization

-79%

Potential reduce by 162.8 kB

Original 206.3 kB
After minification 169.8 kB
After compression 43.5 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. Kabe.xyz needs all CSS files to be minified and compressed as it can save up to 162.8 kB or 79% of the original size.

Requests Now

145

After Optimization

128

The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kabe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 10 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-*] 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.

High

[aria-*] attributes do not have valid values

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 keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

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

N/A
Encoding

UTF-8

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

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

壁紙も自分で張ってDIYできる。おしゃれ壁紙・クロスの通販サイト

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

kabe.xyz

kabe.tomoyasu.co.jp

com_common.css

com_base.css

com_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

{{url}}

Accessibility Review

Accessibility Issues

Best Practices

Areas of Improvement

SEO Factors

Search Engine Optimization Advices

Language and Encoding

Language Detected

Language Claimed

Encoding

Social Sharing Optimization

{{og_title}}