Access 164s.net. 164マーケティング

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value25.5 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

164s.net

3363 ms

analytics.js

47 ms

wp-emoji-release.min.js

331 ms

styles.css

355 ms

wpp.css

356 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 70% of them (78 requests) were addressed to the original 164s.net, 8% (9 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain 164s.net.

Content Size

1.3 MB

After Optimization

1.1 MB

In fact, the total size of 164s.net main page is 1.3 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. Only a small number of websites need less resources to load. Images take 822.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 89.6 kB

Original 112.7 kB
After minification 111.8 kB
After compression 23.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 89.6 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 5.1 kB

Original 822.3 kB
After minification 817.2 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. 164 S images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 90.5 kB

Original 336.5 kB
After minification 336.3 kB
After compression 246.0 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 90.5 kB or 27% of the original size.

CSS Optimization

-31%

Potential reduce by 11.8 kB

Original 38.5 kB
After minification 38.1 kB
After compression 26.7 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. 164s.net needs all CSS files to be minified and compressed as it can save up to 11.8 kB or 31% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Serves images with low resolution

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 164s.net 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 164s.net 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

164s.net

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

164マーケティング

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)