Tools & Wizards About Us
taxi-tokyo.or.jp screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

taxi-tokyo.or.jp

東京のタクシー［一般社団法人 東京ハイヤー・タクシー協会］

Page Load Speed

6.1 sec in total

First Response

530 ms

Resources Loaded

5.2 sec

Page Rendered

329 ms

taxi-tokyo.or.jp screenshot

About Website

Click here to check amazing Taxi Tokyo content for Japan. Otherwise, check out these important facts you probably never knew about taxi-tokyo.or.jp

ハイヤータクシー事業の使命である安全輸送と接客サービスの向上を柱として「利用者向け広報活動の推進 」「利用者利便向上対策の推進」「交通事故防止対策の推進」「メセナ活動の推進」などの活動を行っています。

Visit taxi-tokyo.or.jp

Key Findings

We analyzed Taxi-tokyo.or.jp page load time and found that the first response time was 530 ms and then it took 5.5 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

taxi-tokyo.or.jp performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value16.9 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value300 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.234

53/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

taxi-tokyo.or.jp

530 ms

taxi-tokyo.or.jp

1046 ms

css

30 ms

style.css

496 ms

home.css

532 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 86% of them (48 requests) were addressed to the original Taxi-tokyo.or.jp, 5% (3 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Taxi-tokyo.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 261.0 kB (4%)

Content Size

6.0 MB

After Optimization

5.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Taxi-tokyo.or.jp main page is 6.0 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. Only a small number of websites need less resources to load. Images take 5.6 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 37.7 kB

  • Original 43.8 kB
  • After minification 36.6 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 7.2 kB, which is 16% 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 37.7 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 16.5 kB

  • Original 5.6 MB
  • After minification 5.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. Taxi Tokyo images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 145.3 kB

  • Original 212.0 kB
  • After minification 173.6 kB
  • After compression 66.7 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 145.3 kB or 69% of the original size.

CSS Optimization

-86%

Potential reduce by 61.5 kB

  • Original 71.4 kB
  • After minification 48.1 kB
  • After compression 9.9 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. Taxi-tokyo.or.jp needs all CSS files to be minified and compressed as it can save up to 61.5 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (33%)

Requests Now

51

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

taxi-tokyo.or.jp

taxi-tokyo.or.jp

530 ms

taxi-tokyo.or.jp

taxi-tokyo.or.jp

1046 ms

css

css

30 ms

style.css

style.css

496 ms

home.css

home.css

532 ms

js

js

52 ms

jquery.min.js

jquery.min.js

937 ms

slick.js

slick.js

666 ms

common.js

common.js

374 ms

foundation.css

foundation.css

339 ms

slick.css

slick.css

395 ms

slick-theme.css

slick-theme.css

377 ms

header.css

header.css

491 ms

footer.css

footer.css

502 ms

layout.css

layout.css

547 ms

btn.css

btn.css

571 ms

text.css

text.css

649 ms

object.css

object.css

664 ms

utility.css

utility.css

665 ms

js

js

105 ms

analytics.js

analytics.js

99 ms

logo.svg

logo.svg

175 ms

nav_img_01.png

nav_img_01.png

576 ms

nav_img_02.png

nav_img_02.png

946 ms

nav_img_03.png

nav_img_03.png

766 ms

nav_img_04.png

nav_img_04.png

389 ms

nav_img_05.png

nav_img_05.png

409 ms

intro_01.png

intro_01.png

1352 ms

intro_01_sp.png

intro_01_sp.png

1111 ms

ic_arrow_m_beige.png

ic_arrow_m_beige.png

595 ms

intro_02.png

intro_02.png

2630 ms

intro_02_sp.png

intro_02_sp.png

1276 ms

ic_arrow_m_green.png

ic_arrow_m_green.png

929 ms

intro_03.png

intro_03.png

2734 ms

intro_03_sp.png

intro_03_sp.png

1659 ms

ic_arrow_m_white.png

ic_arrow_m_white.png

1269 ms

content_01.png

content_01.png

1591 ms

content_01_sp.png

content_01_sp.png

1616 ms

ic_attention.png

ic_attention.png

1516 ms

ic_arrow_m_blue.png

ic_arrow_m_blue.png

1682 ms

ic_pdf.png

ic_pdf.png

1750 ms

content_02.png

content_02.png

2302 ms

content_02_sp.png

content_02_sp.png

2009 ms

ic_xls.png

ic_xls.png

1848 ms

content_03.png

content_03.png

2069 ms

content_03_sp.png

content_03_sp.png

2180 ms

bnr_04.png

bnr_04.png

2184 ms

bnr_01.png

bnr_01.png

2228 ms

bnr_02.png

bnr_02.png

2346 ms

bnr_03.png

bnr_03.png

2377 ms

ic_arrow_s.png

ic_arrow_s.png

2386 ms

ic_jump.png

ic_jump.png

2469 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj35TS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj35TS1g.ttf

80 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35TS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35TS1g.ttf

114 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk35TS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk35TS1g.ttf

140 ms

collect

collect

30 ms

Accessibility Review

taxi-tokyo.or.jp accessibility score

92

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

Best Practices

taxi-tokyo.or.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

SEO Factors

taxi-tokyo.or.jp SEO score

99

Search Engine Optimization Advices

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 Taxi-tokyo.or.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 Taxi-tokyo.or.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

taxi-tokyo.or.jp

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