Tools & Wizards About Us
contact.co.jp screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

contact.co.jp

株式会社コンタクト　「CARZY」コレクタブルカーの個人間売買アプリ運営、ASPサービス運営

Page Load Speed

5.4 sec in total

First Response

580 ms

Resources Loaded

4.3 sec

Page Rendered

570 ms

contact.co.jp screenshot

About Website

Welcome to contact.co.jp homepage info - get ready to check Contact best content right away, or after learning these important things about contact.co.jp

株式会社コンタクト　「CARZY」コレクタブルカーの個人間売買アプリ運営、「おちゃのこネット」「おちゃのこさいさい」ASPサービス運営

Visit contact.co.jp

Key Findings

We analyzed Contact.co.jp page load time and found that the first response time was 580 ms and then it took 4.9 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

contact.co.jp performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value13.2 s

0/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

contact.co.jp

580 ms

jsapi

18 ms

jquery-1.4.2.min.js

358 ms

jquery.page-scroller.js

350 ms

jquery.cookie.js

375 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 159.8 kB (10%)

Content Size

1.6 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-89%

Potential reduce by 30.3 kB

  • Original 34.1 kB
  • After minification 17.7 kB
  • After compression 3.8 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 16.3 kB, which is 48% 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 30.3 kB or 89% of the original size.

Image Optimization

-3%

Potential reduce by 40.1 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. Contact images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 76.9 kB

  • Original 125.7 kB
  • After minification 109.4 kB
  • After compression 48.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 76.9 kB or 61% of the original size.

CSS Optimization

-79%

Potential reduce by 12.6 kB

  • Original 15.9 kB
  • After minification 11.1 kB
  • After compression 3.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. Contact.co.jp needs all CSS files to be minified and compressed as it can save up to 12.6 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (24%)

Requests Now

54

After Optimization

41

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

contact.co.jp

contact.co.jp

580 ms

jsapi

jsapi

18 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

358 ms

jquery.page-scroller.js

jquery.page-scroller.js

350 ms

jquery.cookie.js

jquery.cookie.js

375 ms

ui.core.js

ui.core.js

376 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

376 ms

jquery.tipsy.js

jquery.tipsy.js

384 ms

reset.css

reset.css

521 ms

fonts.css

fonts.css

531 ms

common.css

common.css

555 ms

17 ms

contact_navi_l.jpg

contact_navi_l.jpg

720 ms

ocnk_navi_t.jpg

ocnk_navi_t.jpg

575 ms

fe_part.jpg

fe_part.jpg

576 ms

op_part.jpg

op_part.jpg

671 ms

tvr_part.jpg

tvr_part.jpg

688 ms

lo_part.jpg

lo_part.jpg

717 ms

vw_part.jpg

vw_part.jpg

718 ms

po_part.jpg

po_part.jpg

740 ms

fi_part.jpg

fi_part.jpg

842 ms

se_part.jpg

se_part.jpg

859 ms

cor_part.jpg

cor_part.jpg

899 ms

af_part.jpg

af_part.jpg

899 ms

top_ocnk.jpg

top_ocnk.jpg

1085 ms

top_ocnkme.jpg

top_ocnkme.jpg

929 ms

top_garitto.jpg

top_garitto.jpg

1013 ms

top_asm.jpg

top_asm.jpg

1031 ms

contact_map.gif

contact_map.gif

1636 ms

cap_contactnavi.jpg

cap_contactnavi.jpg

1267 ms

cap_ocnknavi.jpg

cap_ocnknavi.jpg

1308 ms

cap_open.jpg

cap_open.jpg

1357 ms

cap_tvr.jpg

cap_tvr.jpg

1202 ms

cap_ferrari.jpg

cap_ferrari.jpg

1268 ms

cap_lotus.jpg

cap_lotus.jpg

1378 ms

cap_porche.jpg

cap_porche.jpg

1451 ms

cap_vw.jpg

cap_vw.jpg

1637 ms

cap_seven.jpg

cap_seven.jpg

1497 ms

cap_cor.jpg

cap_cor.jpg

1529 ms

default+en.css

default+en.css

3 ms

default+en.I.js

default+en.I.js

5 ms

cap_fiat.jpg

cap_fiat.jpg

1239 ms

cap_alfa.jpg

cap_alfa.jpg

1299 ms

cap_ocnk.jpg

cap_ocnk.jpg

1542 ms

cap_ocnkme.jpg

cap_ocnkme.jpg

1709 ms

cap_garitto.jpg

cap_garitto.jpg

1562 ms

cap_asm.jpg

cap_asm.jpg

1652 ms

inquiry_cut.jpg

inquiry_cut.jpg

1335 ms

ga.js

ga.js

34 ms

bodybg.jpg

bodybg.jpg

1635 ms

main_bg.png

main_bg.png

2225 ms

ci.gif

ci.gif

1509 ms

__utm.gif

__utm.gif

19 ms

footerbg.jpg

footerbg.jpg

2413 ms

Gfeeds

Gfeeds

683 ms

Accessibility Review

contact.co.jp accessibility score

81

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

Image elements do not have [alt] attributes

Best Practices

contact.co.jp best practices score

50

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

contact.co.jp SEO score

67

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

Image elements do not have [alt] attributes

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

contact.co.jp

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