Tools & Wizards About Us
phoenix-japan.com screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

phoenix-japan.com

PHOENIX JAPAN | JAPANESE QUALITY VEHICLES EXPORTER . EST.1989

Page Load Speed

5 sec in total

First Response

1 sec

Resources Loaded

3.7 sec

Page Rendered

243 ms

phoenix-japan.com screenshot

About Website

Visit phoenix-japan.com now to see the best up-to-date PHOENIX JAPAN content and also check out these interesting facts you probably never knew about phoenix-japan.com

PHOENIX JAPANでは、愛知県知多郡で日本車を輸出し中古販売をしております。

Visit phoenix-japan.com

Key Findings

We analyzed Phoenix-japan.com page load time and found that the first response time was 1 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

phoenix-japan.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.9 s

100/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value0.9 s

100/100

10%

Network Requests Diagram

phoenix-japan.com

1039 ms

import.css

345 ms

jquery.js

1115 ms

script.js

899 ms

webchangercmn.css

391 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that all of those requests were addressed to Phoenix-japan.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Phoenix-japan.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 119.9 kB (11%)

Content Size

1.1 MB

After Optimization

980.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phoenix-japan.com main page is 1.1 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. 20% of websites need less resources to load. Images take 970.9 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 8.9 kB

  • Original 11.2 kB
  • After minification 7.4 kB
  • After compression 2.2 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 3.7 kB, which is 33% 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 8.9 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 22.8 kB

  • Original 970.9 kB
  • After minification 948.0 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. PHOENIX JAPAN images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 65.9 kB

  • Original 90.9 kB
  • After minification 76.2 kB
  • After compression 25.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 65.9 kB or 72% of the original size.

CSS Optimization

-82%

Potential reduce by 22.2 kB

  • Original 27.2 kB
  • After minification 22.1 kB
  • After compression 5.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. Phoenix-japan.com needs all CSS files to be minified and compressed as it can save up to 22.2 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

37

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phoenix-japan.com

phoenix-japan.com

1039 ms

import.css

import.css

345 ms

jquery.js

jquery.js

1115 ms

script.js

script.js

899 ms

webchangercmn.css

webchangercmn.css

391 ms

indexwebchanger.css

indexwebchanger.css

419 ms

wctarget.js

wctarget.js

685 ms

default.css

default.css

242 ms

lightbox.css

lightbox.css

271 ms

layout01.css

layout01.css

737 ms

wcax.js

wcax.js

372 ms

head_bg.jpg

head_bg.jpg

826 ms

header_link_bg.png

header_link_bg.png

211 ms

n01.png

n01.png

173 ms

n02.png

n02.png

181 ms

n03.png

n03.png

196 ms

n04.png

n04.png

175 ms

n05.png

n05.png

344 ms

top_link.png

top_link.png

346 ms

main.jpg

main.jpg

1079 ms

tit.gif

tit.gif

391 ms

tit_bg.gif

tit_bg.gif

627 ms

img163ak5600_1.jpg

img163ak5600_1.jpg

1713 ms

img163ak5651_1.jpg

img163ak5651_1.jpg

1209 ms

img1635i1341_1.jpg

img1635i1341_1.jpg

1944 ms

img1635i1421_1.jpg

img1635i1421_1.jpg

1463 ms

img1625e5504_1.jpg

img1625e5504_1.jpg

1854 ms

img123fl1622_1.gif

img123fl1622_1.gif

1259 ms

s_id.gif

s_id.gif

1383 ms

iphone.gif

iphone.gif

1439 ms

blackberry.gif

blackberry.gif

1556 ms

05.gif

05.gif

1619 ms

06.gif

06.gif

1672 ms

01.gif

01.gif

1728 ms

04.gif

04.gif

1799 ms

02.gif

02.gif

1880 ms

03.gif

03.gif

1882 ms

img14afb4312_1.png

img14afb4312_1.png

1900 ms

Accessibility Review

phoenix-japan.com accessibility score

83

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

Best Practices

phoenix-japan.com 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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

phoenix-japan.com SEO score

68

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

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

    EN

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phoenix-japan.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Phoenix-japan.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

phoenix-japan.com

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