6.9 sec in total
310 ms
5.9 sec
687 ms
Welcome to docomo-cycle.jp homepage info - get ready to check Docomo Cycle best content for Japan right away, or after learning these important things about docomo-cycle.jp
ドコモ・バイクシェアが提供する自転車シェアリング(シェアサイクル)サービスの総合サイトです。
Visit docomo-cycle.jpWe analyzed Docomo-cycle.jp page load time and found that the first response time was 310 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
docomo-cycle.jp performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value27.7 s
0/100
25%
Value9.9 s
10/100
10%
Value1,690 ms
11/100
30%
Value2.11
0/100
15%
Value13.6 s
11/100
10%
310 ms
314 ms
70 ms
37 ms
1020 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 73% of them (56 requests) were addressed to the original Docomo-cycle.jp, 8% (6 requests) were made to Apis.google.com and 5% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Docomo-cycle.jp.
Page size can be reduced by 376.5 kB (6%)
6.0 MB
5.6 MB
In fact, the total size of Docomo-cycle.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.4 MB which makes up the majority of the site volume.
Potential reduce by 43.0 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 11.6 kB, which is 23% 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 43.0 kB or 83% of the original size.
Potential reduce by 322.4 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. Docomo Cycle images are well optimized though.
Potential reduce by 8.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. This website has mostly compressed JavaScripts.
Potential reduce by 2.3 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. Docomo-cycle.jp has all CSS files already compressed.
Number of requests can be reduced by 14 (22%)
65
51
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Docomo Cycle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
docomo-cycle.jp
310 ms
docomo-cycle.jp
314 ms
gtm.js
70 ms
all.css
37 ms
bundle.css
1020 ms
bike_share_service_logo.png
593 ms
bike_share_service_logo_white.png
609 ms
lalaport_campaign.png
900 ms
tokyo_16.png
751 ms
2023_safety_ja.jpg
728 ms
tokyo_ev.jpg
1469 ms
2023_cycle_ad.jpg
1496 ms
check_bike.png
1453 ms
common_id_ja.png
1777 ms
navitime_pass.png
1762 ms
mixway_banner.png
1602 ms
1pass.png
2169 ms
icon_title_01.png
1619 ms
img_slide_01.png
2523 ms
img_slide_02.png
2880 ms
img_slide_03.png
2606 ms
img_slide_04.png
2207 ms
img_slide_05.png
2073 ms
img_bike_01.png
2937 ms
icon_point_01.png
2319 ms
img_point_01.png
3086 ms
icon_point_02.png
2468 ms
img_point_02.png
2624 ms
icon_point_03.png
2670 ms
img_point_03.png
3466 ms
icon_point_04.png
2775 ms
img_point_04.png
2964 ms
img_phone_01.png
3506 ms
btn_google_01.png
3029 ms
btn_app_01.png
3089 ms
qr_google_01.png
3542 ms
qr_app_01.png
3178 ms
icon_title_01.png
3525 ms
icon_title_01.png
3237 ms
platform.js
32 ms
widgets.js
18 ms
js
78 ms
lib.js
3502 ms
cb=gapi.loaded_0
8 ms
cb=gapi.loaded_1
24 ms
fastbutton
21 ms
postmessageRelay
31 ms
544727282-postmessagerelay.js
24 ms
rpc:shindig_random.js
8 ms
developers.google.com
359 ms
cb=gapi.loaded_0
4 ms
common.js
3794 ms
include.js
3607 ms
bundle.js
3362 ms
index.js
3659 ms
top_img.jpg
3107 ms
dbs_logo.svg
3007 ms
NotoSansJP-Medium.woff
35 ms
NotoSansJP-Bold.woff
82 ms
NotoSansJP-Black.woff
119 ms
NotoSansCJKjp-Regular.woff
2704 ms
Montserrat-ExtraBold.woff
3220 ms
fontawesome-webfont.woff
3070 ms
bg_01.jpg
3753 ms
bg_01.png
2788 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
85 ms
portnavi.json
191 ms
bikeshare.json
186 ms
pin_red.svg
160 ms
pin_orange.svg
193 ms
pin_blue.svg
285 ms
settings
134 ms
photo_01.jpg
486 ms
photo_02.jpg
503 ms
button.856debeac157d9669cf51e73a08fbc93.js
23 ms
embeds
44 ms
follow_button.2f70fb173b9000da126c79afe2098f02.ja.html
30 ms
docomo-cycle.jp accessibility score
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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
docomo-cycle.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
docomo-cycle.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Docomo-cycle.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 Docomo-cycle.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.
docomo-cycle.jp
Open Graph data is detected on the main page of Docomo Cycle. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: