Access akichi.jp. 事業用地・倉庫・工場の売買｜株式会社オン・フォワード

name

value

score

weighting

FCP (First Contentful Paint)

Value8.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value17.3 s

0/100

10%

TBT (Total Blocking Time)

Value1,270 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.211

59/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

akichi.jp

555 ms

akichi.jp

1193 ms

change_sp.js

547 ms

analyze_js.php

812 ms

index.js

929 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 85% of them (79 requests) were addressed to the original Akichi.jp, 3% (3 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (11.3 sec) belongs to the original domain Akichi.jp.

Content Size

1.9 MB

After Optimization

1.5 MB

In fact, the total size of Akichi.jp main page is 1.9 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 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 20.0 kB

Original 26.8 kB
After minification 24.0 kB
After compression 6.9 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 2.8 kB, which is 11% 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 20.0 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 23.7 kB

Original 1.4 MB
After minification 1.4 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. Akichi images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 220.6 kB

Original 365.9 kB
After minification 263.0 kB
After compression 145.3 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 220.6 kB or 60% of the original size.

CSS Optimization

-85%

Potential reduce by 93.3 kB

Original 109.3 kB
After minification 78.5 kB
After compression 16.0 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. Akichi.jp needs all CSS files to be minified and compressed as it can save up to 93.3 kB or 85% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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 interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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

SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Akichi.jp 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 Akichi.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

akichi.jp

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

事業用地・倉庫・工場の売買｜株式会社オン・フォワード

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

akichi.jp

akichi.jp

change_sp.js

analyze_js.php

index.js

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

akichi.jp

akichi.jp

change_sp.js

analyze_js.php

index.js

base.css

top.css

common.css

jquery.js

show_switch.js

font-awesome.min.css

css_slide.css

pagetop.css

pagetop.js

mouseover.js

HatenaStar.js

bookmark_button.js

jquery.fadethis.min.js

jquery.min.js

pcpv.php

footprint.php

gtm.js

_jc_topshow.php

_jc_topshow.php

smart.webp

logo.webp

tel.webp

h_icon_mail.png

nav_icon01.jpg

nav_icon02.jpg

nav_icon03.jpg

nav_icon04.jpg

nav_icon05.jpg

nav_icon06.jpg

main_img01.webp

main_img02.webp

main_img03.webp

main_catch.webp

method_icon.jpg

flow_img01.webp

flow_arrow.webp

flow_img02.webp

flow_img03.webp