Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

aotaniss.com

社章 ネームプレートは青谷製作所

Page Load Speed

12.4 sec in total

First Response

532 ms

Resources Loaded

11.4 sec

Page Rendered

456 ms

About Website

Click here to check amazing Aotaniss content. Otherwise, check out these important facts you probably never knew about aotaniss.com

昭和27年創業以来、70年以上の歴史を持つ青谷製作所は、熟練の技と最新の技術を融合させ、お客様の想いを形にする金属加工の専門家です。フリクションプレスによる高度な金属加工技術を駆使し、社章、メダル、コインなど、多様な金属製品をオーダーメイドで製作。創業以来培われた確かな技術と、時代の変化に対応した柔軟な発想で、お客様にご満足いただける製品をお届けします。

Visit aotaniss.com

Key Findings

We analyzed Aotaniss.com page load time and found that the first response time was 532 ms and then it took 11.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

aotaniss.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value140 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value9.3 s

32/100

10%

Network Requests Diagram

aotaniss.com

532 ms

aotaniss.com

1339 ms

js

76 ms

base.css

1452 ms

rwd.css

527 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 92% of them (65 requests) were addressed to the original Aotaniss.com, 3% (2 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (8.3 sec) belongs to the original domain Aotaniss.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 541.4 kB (19%)

Content Size

2.8 MB

After Optimization

2.3 MB

In fact, the total size of Aotaniss.com main page is 2.8 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 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 65.4 kB

  • Original 75.3 kB
  • After minification 57.0 kB
  • After compression 9.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 18.3 kB, which is 24% 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 65.4 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 27.6 kB

  • Original 2.2 MB
  • After minification 2.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. Aotaniss images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 266.4 kB

  • Original 348.5 kB
  • After minification 347.8 kB
  • After compression 82.1 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 266.4 kB or 76% of the original size.

CSS Optimization

-88%

Potential reduce by 182.0 kB

  • Original 205.8 kB
  • After minification 159.3 kB
  • After compression 23.8 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. Aotaniss.com needs all CSS files to be minified and compressed as it can save up to 182.0 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (22%)

Requests Now

68

After Optimization

53

The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aotaniss. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

aotaniss.com accessibility score

73

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

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.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

aotaniss.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

aotaniss.com SEO score

80

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Mobile Friendly

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

Impact

Issue

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

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