Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

apexi.co.jp

A’pexi

Page Load Speed

8.1 sec in total

First Response

537 ms

Resources Loaded

6.8 sec

Page Rendered

729 ms

apexi.co.jp screenshot

About Website

Visit apexi.co.jp now to see the best up-to-date A Pexi content for Russia and also check out these interesting facts you probably never knew about apexi.co.jp

A\'PEXiブランドのオリジナル自動車用パーツメーカー。マフラー、電子パーツ、ダンパー・ インテークなどを企画・開発・製造・販売。本社:愛知県豊明市

Visit apexi.co.jp

Key Findings

We analyzed Apexi.co.jp page load time and found that the first response time was 537 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

apexi.co.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

6/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value1,780 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

apexi.co.jp

537 ms

www.apexi.co.jp

2580 ms

smartslider.min.css

519 ms

jquery.min.js

30 ms

jquery-migrate.min.js

29 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 77% of them (49 requests) were addressed to the original Apexi.co.jp, 8% (5 requests) were made to Gstatic.com and 6% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Apexi.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (37%)

Content Size

3.2 MB

After Optimization

2.0 MB

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

HTML Optimization

-85%

Potential reduce by 715.3 kB

  • Original 844.0 kB
  • After minification 841.5 kB
  • After compression 128.7 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 715.3 kB or 85% of the original size.

Image Optimization

-16%

Potential reduce by 285.3 kB

  • Original 1.8 MB
  • After minification 1.6 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. Obviously, A Pexi needs image optimization as it can save up to 285.3 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-35%

Potential reduce by 167.5 kB

  • Original 473.4 kB
  • After minification 473.4 kB
  • After compression 305.8 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 167.5 kB or 35% of the original size.

CSS Optimization

-39%

Potential reduce by 18.1 kB

  • Original 46.7 kB
  • After minification 46.7 kB
  • After compression 28.6 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. Apexi.co.jp needs all CSS files to be minified and compressed as it can save up to 18.1 kB or 39% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (28%)

Requests Now

58

After Optimization

42

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

Accessibility Review

apexi.co.jp accessibility score

98

Accessibility Issues

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

Links do not have a discernible name

Best Practices

apexi.co.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

SEO Factors

apexi.co.jp SEO score

91

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

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 Apexi.co.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 Apexi.co.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

Open Graph data is detected on the main page of A Pexi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: