Tools & Wizards About Us
pnx.co.jp screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

pnx.co.jp

中古車購入は中古車販売のフェニックスへ！年間販売台数10000台以上の実績・全国直営店舗

Page Load Speed

6.4 sec in total

First Response

1.2 sec

Resources Loaded

4.8 sec

Page Rendered

336 ms

pnx.co.jp screenshot

About Website

Welcome to pnx.co.jp homepage info - get ready to check Pnx best content for Japan right away, or after learning these important things about pnx.co.jp

中古車購入は中古車販売のフェニックスへ！総在庫3000台・全国直営店舗にトヨタ、日産、ホンダ、輸入車など豊富な品揃え。最大20万円のキャッシュバックあり。

Visit pnx.co.jp

Key Findings

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

Performance Metrics

pnx.co.jp performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value23.4 s

0/100

25%

SI (Speed Index)

Value16.6 s

0/100

10%

TBT (Total Blocking Time)

Value4,860 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.309

38/100

15%

TTI (Time to Interactive)

Value30.4 s

0/100

10%

Network Requests Diagram

pnx.co.jp

1248 ms

base.css

335 ms

top.css

170 ms

tenpo.css

335 ms

contents.css

533 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 87% of them (71 requests) were addressed to the original Pnx.co.jp, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Pnx.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 446.1 kB (47%)

Content Size

944.1 kB

After Optimization

498.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pnx.co.jp main page is 944.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 350.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 61.9 kB

  • Original 78.0 kB
  • After minification 76.3 kB
  • After compression 16.1 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 61.9 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 5.4 kB

  • Original 350.9 kB
  • After minification 345.5 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. Pnx images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 166.6 kB

  • Original 258.5 kB
  • After minification 258.4 kB
  • After compression 91.9 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 166.6 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 212.3 kB

  • Original 256.7 kB
  • After minification 254.1 kB
  • After compression 44.4 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. Pnx.co.jp needs all CSS files to be minified and compressed as it can save up to 212.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (32%)

Requests Now

77

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pnx. 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

pnx.co.jp

pnx.co.jp

1248 ms

base.css

base.css

335 ms

top.css

top.css

170 ms

tenpo.css

tenpo.css

335 ms

contents.css

contents.css

533 ms

analytics.js

analytics.js

317 ms

side.html

side.html

335 ms

back.gif

back.gif

312 ms

header.gif

header.gif

318 ms

hdr_menu.gif

hdr_menu.gif

321 ms

phenix_logo.gif

phenix_logo.gif

356 ms

spacer.gif

spacer.gif

356 ms

header_1.gif

header_1.gif

357 ms

header_0.gif

header_0.gif

357 ms

header_2.gif

header_2.gif

370 ms

header_3.gif

header_3.gif

415 ms

header_4.gif

header_4.gif

558 ms

header_5.gif

header_5.gif

555 ms

header_6.gif

header_6.gif

556 ms

main_image.jpg

main_image.jpg

1813 ms

news.gif

news.gif

553 ms

sankaku.gif

sankaku.gif

616 ms

flyer150918.jpg

flyer150918.jpg

1673 ms

new1509.jpg

new1509.jpg

1567 ms

flyer150203.jpg

flyer150203.jpg

1566 ms

flyer150101.jpg

flyer150101.jpg

2162 ms

new1411.jpg

new1411.jpg

2092 ms

flyer140917.jpg

flyer140917.jpg

2089 ms

flyer140912.jpg

flyer140912.jpg

2091 ms

shop_list.gif

shop_list.gif

1840 ms

country_map.gif

country_map.gif

1970 ms

zaiko_btn2.gif

zaiko_btn2.gif

2002 ms

zaiko_btn3.gif

zaiko_btn3.gif

2134 ms

copyright.gif

copyright.gif

2168 ms

counter.cgi

counter.cgi

2342 ms

1C9J4yK7sEs

1C9J4yK7sEs

114 ms

side.css

side.css

1981 ms

tenpo_midashi.gif

tenpo_midashi.gif

2001 ms

tenpo_all.gif

tenpo_all.gif

2003 ms

spacer.jpg

spacer.jpg

2041 ms

sp_btn.jpg

sp_btn.jpg

2042 ms

banner_entry_160_45.gif

banner_entry_160_45.gif

2143 ms

tenpo_head.gif

tenpo_head.gif

2205 ms

tenpo_1.gif

tenpo_1.gif

2160 ms

tenpo_2.gif

tenpo_2.gif

2211 ms

tenpo_3.gif

tenpo_3.gif

2198 ms

collect

collect

24 ms

tenpo_4.gif

tenpo_4.gif

2186 ms

tenpo_5.gif

tenpo_5.gif

2270 ms

tenpo_6.gif

tenpo_6.gif

2284 ms

tenpo_7.gif

tenpo_7.gif

2364 ms

tenpo_7_1.gif

tenpo_7_1.gif

2329 ms

tenpo_9.gif

tenpo_9.gif

2336 ms

collect

collect

58 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

67 ms

www-embed-player.js

www-embed-player.js

91 ms

tenpo_10.gif

tenpo_10.gif

2292 ms

ga-audiences

ga-audiences

126 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

25 ms

ad_status.js

ad_status.js

34 ms

tenpo_11.gif

tenpo_11.gif

2244 ms

tenpo_23.gif

tenpo_23.gif

2246 ms

tenpo_13.gif

tenpo_13.gif

2292 ms

tenpo_14.gif

tenpo_14.gif

2324 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

43 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

47 ms

tenpo_15.gif

tenpo_15.gif

2259 ms

tenpo_16.gif

tenpo_16.gif

1355 ms

tenpo_24.gif

tenpo_24.gif

1403 ms

tenpo_17.gif

tenpo_17.gif

1287 ms

tenpo_18.gif

tenpo_18.gif

1199 ms

tenpo_22.gif

tenpo_22.gif

1208 ms

tenpo_19.gif

tenpo_19.gif

1079 ms

tenpo_20.gif

tenpo_20.gif

1118 ms

tenpo_21.gif

tenpo_21.gif

1034 ms

cap.gif

cap.gif

1054 ms

side_rent.jpg

side_rent.jpg

1250 ms

rent_head.gif

rent_head.gif

1085 ms

rent_1.gif

rent_1.gif

1071 ms

rent_3.gif

rent_3.gif

1112 ms

bnr_tcv.gif

bnr_tcv.gif

1065 ms

bnr_jumvea.gif

bnr_jumvea.gif

1020 ms

Accessibility Review

pnx.co.jp accessibility score

77

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

pnx.co.jp 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pnx.co.jp SEO score

86

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

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

pnx.co.jp

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