Access mobileascii.jp. mobileASCII - すべてのモバイルユーザーのための情報サイト

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value4.4 s

73/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

mobileascii.jp

8 ms

mobileascii.jp

519 ms

gtm.js

68 ms

general.css

695 ms

art.css

17 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 38% of them (30 requests) were addressed to the original Mobileascii.jp, 47% (37 requests) were made to Ascii.jp and 5% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (4.8 sec) relates to the external source Ascii.jp.

Content Size

1.4 MB

After Optimization

1.2 MB

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

HTML Optimization

-80%

Potential reduce by 35.5 kB

Original 44.4 kB
After minification 34.5 kB
After compression 9.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 9.9 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 35.5 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 70.6 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. MobileASCII images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 32.1 kB

Original 92.3 kB
After minification 92.3 kB
After compression 60.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 32.1 kB or 35% of the original size.

CSS Optimization

-19%

Potential reduce by 2.9 kB

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

Requests Now

After Optimization

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

Search Engine Optimization Advices

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

High

Links are not crawlable

High

Page is blocked from indexing

High

robots.txt is not valid

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

mobileascii.jp

Open Graph data is detected on the main page of MobileASCII. 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

mobileASCII - すべてのモバイルユーザーのための情報サイト

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

mobileascii.jp

mobileascii.jp

gtm.js

general.css

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

mobileascii.jp

mobileascii.jp

gtm.js

general.css

art.css

axyzsdk.js

jquery.min.js

fixHeight.js

control.js

cookie_optin.js

cat.css

brand

brandjs.js

js

analytics.js

collect

js

3083d7b2451b9a78.jpg

bg_general.gif

bg_tophead.gif

bg_wrap.gif

bg_admain.gif

icon_feedlink.png

1f5997b6cba6b392.png

044da2fd4bd4108e.jpg

f4550b0cb2d2a72f.jpg

2694fee7c6888509.jpg

4318ec1aa17551f7.jpg

55c0ea7a718c7caf.jpg

575bf617d3ffeca5.jpg

28ba3e920a1b6ae5.jpg

06f6217565efdcb1.jpg

f9cfbe6cfe360727.jpg

fdfe2140d92deb72.png

6299519ce6e6535a.jpg

87ed7ceb917c1930.jpg

1c55730bbf07e853.jpg

6c221cfc8689a6cf.jpg

ea44962d3fa3edf4.jpg

b87a533c498647d4.jpg

ee01fe3b03990d32.jpg

cf5c453aece13574.jpg

89023c3e3c30d983.jpg