Access fuseitaisaku.com. 不正対策.com: 転売目的やなりすましの注文を自動検知

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value15.9 s

0/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.295

40/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

fuseitaisaku.com

886 ms

import.css

343 ms

top.css

546 ms

element.js

36 ms

reset.css

172 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 44% of them (37 requests) were addressed to the original Fuseitaisaku.com, 20% (17 requests) were made to Static.xx.fbcdn.net and 12% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Fuseitaisaku.com.

Content Size

306.8 kB

After Optimization

246.4 kB

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

HTML Optimization

-75%

Potential reduce by 24.2 kB

Original 32.2 kB
After minification 27.1 kB
After compression 8.0 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 5.1 kB, which is 16% 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 24.2 kB or 75% of the original size.

Image Optimization

-5%

Potential reduce by 6.3 kB

Original 133.7 kB
After minification 127.4 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. Fuseitaisaku images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 16.0 kB

Original 120.6 kB
After minification 119.9 kB
After compression 104.6 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 16.0 kB or 13% of the original size.

CSS Optimization

-68%

Potential reduce by 13.9 kB

Original 20.3 kB
After minification 15.7 kB
After compression 6.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. Fuseitaisaku.com needs all CSS files to be minified and compressed as it can save up to 13.9 kB or 68% 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 Fuseitaisaku. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 9 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.

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

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.

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

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

Page has valid source maps

Search Engine Optimization Advices

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

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 Fuseitaisaku.com 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 Fuseitaisaku.com 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

fuseitaisaku.com

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

不正対策.com: 転売目的やなりすましの注文を自動検知

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

fuseitaisaku.com

import.css

top.css

element.js

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

fuseitaisaku.com

import.css

top.css

element.js

reset.css

base.css

sr.gif

get_flash_player.gif

p-mark.gif

logo.gif

tel.gif

gnavi.gif

ico_arrow1.gif

ttl_contact.gif

c_msg.gif

c_tel.gif

c_web.gif

btn_contact.gif

banner-afro.gif

efforts-media.gif

sBaner.gif

ttl_whatsnew.gif

ttl_conventional.gif

ttl_side_ec.gif

ttl_side_affiliat.gif

ttl_side_media.gif

ttl_jittai.gif

jittai_navi.gif

ttl_login.gif

btn_login.gif

btn_contact_red.gif

sdk.js

bg_header.gif

ico_arrow2.gif

translateelement.css

main.js

xd_arbiter.php

xd_arbiter.php

bg_gnavi.gif

btn_about.jpg

btn_faq.jpg

btn_performance.jpg

btn_media.jpg