Tools & Wizards About Us
tokyoelevator.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

tokyoelevator.com

東京エレベーター株式会社 - エレベーター改修・リニューアル、点検、保守

Page Load Speed

8.3 sec in total

First Response

910 ms

Resources Loaded

6.1 sec

Page Rendered

1.3 sec

tokyoelevator.com screenshot

About Website

Welcome to tokyoelevator.com homepage info - get ready to check Tokyoelevator best content right away, or after learning these important things about tokyoelevator.com

エレベーター点検、エレベーター保守、エレベーターリニューアル及びメンテナンスを行う独立系エレベーター管理会社です。全メーカー各機種のエレベーターに対応致します。安心安全第一！豊富な部品在庫。交換工事費用も大幅削減！見積り迅速対応。地震や故障時も安心の24時間365日対応です！

Visit tokyoelevator.com

Key Findings

We analyzed Tokyoelevator.com page load time and found that the first response time was 910 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

tokyoelevator.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value15.1 s

0/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.407

24/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

tokyoelevator.com

910 ms

simple-line-icons.min.css

45 ms

k2.css

183 ms

css

47 ms

bootstrap.min.css

370 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 87% of them (77 requests) were addressed to the original Tokyoelevator.com, 6% (5 requests) were made to Googletagmanager.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Tokyoelevator.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 491.0 kB (6%)

Content Size

8.1 MB

After Optimization

7.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tokyoelevator.com main page is 8.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. 65% of websites need less resources to load. Images take 7.8 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 38.8 kB

  • Original 49.0 kB
  • After minification 45.2 kB
  • After compression 10.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. 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 38.8 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 385.7 kB

  • Original 7.8 MB
  • After minification 7.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. Tokyoelevator images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 42.9 kB

  • Original 119.3 kB
  • After minification 119.2 kB
  • After compression 76.3 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 42.9 kB or 36% of the original size.

CSS Optimization

-29%

Potential reduce by 23.5 kB

  • Original 82.3 kB
  • After minification 82.3 kB
  • After compression 58.8 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. Tokyoelevator.com needs all CSS files to be minified and compressed as it can save up to 23.5 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (31%)

Requests Now

87

After Optimization

60

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tokyoelevator.com

tokyoelevator.com

910 ms

simple-line-icons.min.css

simple-line-icons.min.css

45 ms

k2.css

k2.css

183 ms

css

css

47 ms

bootstrap.min.css

bootstrap.min.css

370 ms

font-awesome.min.css

font-awesome.min.css

532 ms

legacy.css

legacy.css

553 ms

template.css

template.css

555 ms

preset1.css

preset1.css

562 ms

frontend-edit.css

frontend-edit.css

563 ms

default.css

default.css

563 ms

jquery.min.js

jquery.min.js

888 ms

jquery-noconflict.js

jquery-noconflict.js

732 ms

jquery-migrate.min.js

jquery-migrate.min.js

735 ms

k2.frontend.js

k2.frontend.js

749 ms

caption.js

caption.js

749 ms

bootstrap.min.js

bootstrap.min.js

750 ms

jquery.sticky.js

jquery.sticky.js

913 ms

main.js

main.js

916 ms

frontend-edit.js

frontend-edit.js

935 ms

js

js

67 ms

default.css

default.css

961 ms

pad.css

pad.css

963 ms

sp.css

sp.css

1117 ms

js

js

96 ms

LOGO2.png

LOGO2.png

282 ms

logo.png

logo.png

282 ms

logo@2x.png

logo@2x.png

282 ms

tel2.png

tel2.png

283 ms

js

js

78 ms

analytics.js

analytics.js

19 ms

collect

collect

86 ms

slider01_left.jpg

slider01_left.jpg

1093 ms

slider01op.png

slider01op.png

370 ms

slider01_right.png

slider01_right.png

985 ms

title_02.png

title_02.png

270 ms

merit01.png

merit01.png

633 ms

merit02.png

merit02.png

631 ms

merit03.png

merit03.png

1003 ms

merit04.png

merit04.png

541 ms

merit05.png

merit05.png

1072 ms

merit06.png

merit06.png

1192 ms

merit11.png

merit11.png

821 ms

merit07.png

merit07.png

1390 ms

bnr_title.png

bnr_title.png

1167 ms

bnr_text.png

bnr_text.png

1190 ms

banner1-L.jpg

banner1-L.jpg

1254 ms

banner1-R.jpg

banner1-R.jpg

1274 ms

bnr_text2.png

bnr_text2.png

1348 ms

title_04.png

title_04.png

1398 ms

img01.png

img01.png

1592 ms

img02.png

img02.png

1614 ms

bnr_title.png

bnr_title.png

1456 ms

bnr_text.png

bnr_text.png

1530 ms

banner2-L.jpg

banner2-L.jpg

1577 ms

banner2-R.jpg

banner2-R.jpg

1589 ms

title_05.png

title_05.png

1641 ms

image_1s.jpg

image_1s.jpg

1712 ms

image_2s.jpg

image_2s.jpg

1769 ms

image_3s.jpg

image_3s.jpg

1784 ms

bnr_title.png

bnr_title.png

1786 ms

bnr_text.png

bnr_text.png

1791 ms

banner3-L.jpg

banner3-L.jpg

1824 ms

embed

embed

292 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1832 ms

banner3-R.jpg

banner3-R.jpg

1798 ms

title_03.png

title_03.png

1818 ms

05_icon01.png

05_icon01.png

1818 ms

05_icon02.png

05_icon02.png

1825 ms

js

js

71 ms

js

js

50 ms

collect

collect

24 ms

05_icon03.png

05_icon03.png

1723 ms

js

js

52 ms

05_icon04.png

05_icon04.png

1728 ms

05_icon05.png

05_icon05.png

1608 ms

05_icon06.png

05_icon06.png

1543 ms

title_07.png

title_07.png

1542 ms

img01.jpg

img01.jpg

1366 ms

img03.png

img03.png

1395 ms

bnr_title.png

bnr_title.png

1277 ms

bnr_text.png

bnr_text.png

1272 ms

banner4-L.jpg

banner4-L.jpg

1271 ms

banner4-R.jpg

banner4-R.jpg

1196 ms

LOGO4.png

LOGO4.png

1174 ms

bnr_background.jpg

bnr_background.jpg

1467 ms

bnr_background.jpg

bnr_background.jpg

1659 ms

bnr_background.jpg

bnr_background.jpg

2208 ms

bnr_background.jpg

bnr_background.jpg

1587 ms

Accessibility Review

tokyoelevator.com accessibility score

82

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

tokyoelevator.com best practices score

75

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

SEO Factors

tokyoelevator.com SEO score

84

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

Links do not have descriptive text

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 Tokyoelevator.com 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 Tokyoelevator.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

tokyoelevator.com

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