Tools & Wizards About Us
timesplus.jp screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

timesplus.jp

カーシェアリングのタイムズカー（旧：タイムズカーシェア）

Page Load Speed

6.4 sec in total

First Response

645 ms

Resources Loaded

5.6 sec

Page Rendered

221 ms

timesplus.jp screenshot

About Website

Click here to check amazing Timesplus content. Otherwise, check out these important facts you probably never knew about timesplus.jp

タイムズのカーシェアリングサービス「タイムズカー」！料金や使い方、場所、メリットを分かりやすくご説明。法人、学生なら月額基本料金は無料。旧タイムズカーシェア

Visit timesplus.jp

Key Findings

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

Performance Metrics

timesplus.jp performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value23.5 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value2,780 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.329

35/100

15%

TTI (Time to Interactive)

Value21.0 s

1/100

10%

Network Requests Diagram

timesplus.jp

645 ms

plus.timescar.jp

635 ms

share.timescar.jp

1221 ms

reset.css

175 ms

common.css

379 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Timesplus.jp, 73% (74 requests) were made to Share.timescar.jp and 3% (3 requests) were made to Ntt-static-integrations.inbenta.services. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Share.timescar.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 133.9 kB (21%)

Content Size

636.4 kB

After Optimization

502.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 30.8 kB

  • Original 41.1 kB
  • After minification 38.1 kB
  • After compression 10.3 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 30.8 kB or 75% of the original size.

Image Optimization

-6%

Potential reduce by 24.4 kB

  • Original 388.3 kB
  • After minification 364.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. Timesplus images are well optimized though.

JavaScript Optimization

-38%

Potential reduce by 72.5 kB

  • Original 189.5 kB
  • After minification 188.8 kB
  • After compression 117.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 72.5 kB or 38% of the original size.

CSS Optimization

-36%

Potential reduce by 6.3 kB

  • Original 17.5 kB
  • After minification 17.3 kB
  • After compression 11.2 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. Timesplus.jp needs all CSS files to be minified and compressed as it can save up to 6.3 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (42%)

Requests Now

98

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

timesplus.jp

timesplus.jp

645 ms

plus.timescar.jp

plus.timescar.jp

635 ms

share.timescar.jp

share.timescar.jp

1221 ms

reset.css

reset.css

175 ms

common.css

common.css

379 ms

top.css

top.css

696 ms

orchestrator.js

orchestrator.js

28 ms

jquery.js

jquery.js

1295 ms

jquery.cookie.js

jquery.cookie.js

524 ms

common.js

common.js

525 ms

url.js

url.js

560 ms

ajax.js

ajax.js

580 ms

errorHandler.js

errorHandler.js

707 ms

ajaxCustomize.js

ajaxCustomize.js

759 ms

ajaxCommon.js

ajaxCommon.js

799 ms

mouseover.js

mouseover.js

768 ms

velocity.min.js

velocity.min.js

1117 ms

top.js

top.js

925 ms

login.js

login.js

925 ms

changeSp.js

changeSp.js

1061 ms

explain.js

explain.js

1061 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1124 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

1123 ms

widgets.js

widgets.js

159 ms

1.73.2.js

1.73.2.js

10 ms

common_ic004.gif

common_ic004.gif

454 ms

common_ic005.gif

common_ic005.gif

525 ms

common_ic006.gif

common_ic006.gif

571 ms

top_ic014.gif

top_ic014.gif

632 ms

top_ic015.gif

top_ic015.gif

632 ms

top_bt004_a.png

top_bt004_a.png

646 ms

top_bt015.png

top_bt015.png

711 ms

top_bt005.png

top_bt005.png

744 ms

top_bt006.png

top_bt006.png

767 ms

top_bt007.png

top_bt007.png

775 ms

top_bn009.png

top_bn009.png

775 ms

index_bn009.gif

index_bn009.gif

829 ms

index_bn032.png

index_bn032.png

901 ms

index_bn006.gif

index_bn006.gif

922 ms

index_bn011.gif

index_bn011.gif

937 ms

index_bn029.png

index_bn029.png

946 ms

index_bn033.png

index_bn033.png

953 ms

index_bn034.png

index_bn034.png

1003 ms

top_bt013.png

top_bt013.png

1100 ms

top_bt014.png

top_bt014.png

1114 ms

footer_bt003.png

footer_bt003.png

1111 ms

gtm.js

gtm.js

118 ms

logo_text.png

logo_text.png

1132 ms

common_ic003.gif

common_ic003.gif

1120 ms

top_bg016.gif

top_bg016.gif

1172 ms

common_ic008.png

common_ic008.png

1319 ms

integration.js

integration.js

8 ms

footer_ex002.gif

footer_ex002.gif

1245 ms

footer_ex003.gif

footer_ex003.gif

1235 ms

js

js

68 ms

ytag.js

ytag.js

682 ms

analytics.js

analytics.js

48 ms

destination

destination

164 ms

AdMatrixAnalyze.min.js

AdMatrixAnalyze.min.js

729 ms

lt.js

lt.js

157 ms

events.js

events.js

155 ms

linkid.js

linkid.js

109 ms

collect

collect

65 ms

collect

collect

70 ms

main.MTIyYzc3NzllMA.js

main.MTIyYzc3NzllMA.js

76 ms

err.gif

err.gif

783 ms

ga-audiences

ga-audiences

33 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

63 ms

teeda.ajax

teeda.ajax

695 ms

sliderMainData.json

sliderMainData.json

696 ms

sliderContData.json

sliderContData.json

763 ms

teeda.ajax

teeda.ajax

1177 ms

ld.js

ld.js

17 ms

settings

settings

96 ms

syncframe

syncframe

13 ms

event

event

648 ms

event

event

657 ms

top_slider100.png

top_slider100.png

388 ms

top_slider029.png

top_slider029.png

182 ms

top_bg_slider083.png

top_bg_slider083.png

181 ms

top_bg_slider090.png

top_bg_slider090.png

516 ms

top_bg_slider023.png

top_bg_slider023.png

266 ms

top_bn034.png

top_bn034.png

284 ms

top_bn004.png

top_bn004.png

384 ms

top_bn003.png

top_bn003.png

456 ms

top_bn017.png

top_bn017.png

498 ms

top_bn031.png

top_bn031.png

567 ms

top_bn005.png

top_bn005.png

600 ms

top_bn033.png

top_bn033.png

633 ms

top_bn007.png

top_bn007.png

648 ms

top_bn018.png

top_bn018.png

643 ms

top_bn024.png

top_bn024.png

697 ms

top_bn019.png

top_bn019.png

771 ms

top_bn008.png

top_bn008.png

778 ms

top_bn015.png

top_bn015.png

816 ms

top_bn030.png

top_bn030.png

821 ms

top_bn032.png

top_bn032.png

825 ms

bx-prev.png

bx-prev.png

891 ms

bx-next.png

bx-next.png

946 ms

beacon.gif

beacon.gif

166 ms

teeda.ajax

teeda.ajax

517 ms

Accessibility Review

timesplus.jp accessibility score

60

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

timesplus.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

timesplus.jp SEO score

83

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

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

timesplus.jp

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