9.2 sec in total
719 ms
8.1 sec
431 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 719 ms and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
docomo-cycle.jp performance score
name
value
score
weighting
Value21.5 s
0/100
10%
Value35.5 s
0/100
25%
Value22.6 s
0/100
10%
Value1,240 ms
19/100
30%
Value0.41
24/100
15%
Value31.5 s
0/100
10%
719 ms
742 ms
299 ms
40 ms
34 ms
Our browser made a total of 182 requests to load all elements on the main page. We found that 60% of them (109 requests) were addressed to the original Docomo-cycle.jp, 16% (29 requests) were made to Maps.googleapis.com and 4% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Docomo-cycle.jp.
Page size can be reduced by 933.2 kB (34%)
2.8 MB
1.8 MB
In fact, the total size of Docomo-cycle.jp main page is 2.8 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 1.6 MB which makes up the majority of the site volume.
Potential reduce by 56.4 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 56.4 kB or 79% of the original size.
Potential reduce by 108.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. Docomo Cycle images are well optimized though.
Potential reduce by 741.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 741.0 kB or 70% of the original size.
Potential reduce by 27.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. Docomo-cycle.jp needs all CSS files to be minified and compressed as it can save up to 27.8 kB or 80% of the original size.
Number of requests can be reduced by 55 (32%)
174
119
The browser has sent 174 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 36 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
docomo-cycle.jp
719 ms
742 ms
style.css
299 ms
js
40 ms
jquery.min.js
34 ms
common.js
475 ms
PIE.js
948 ms
jquery-2.1.4.js
1587 ms
coin-slider.min.js
697 ms
pc_portmap.js
595 ms
colorbox.css
455 ms
jquery.colorbox.js
920 ms
brand
16 ms
system.js
600 ms
brand
72 ms
reset.css
494 ms
ie.css
576 ms
base.css
780 ms
top.css
653 ms
main.css
926 ms
bookmark_button.js
299 ms
analytics.js
37 ms
button-only.gif
198 ms
logo.gif
264 ms
btn_english.png
191 ms
bnr_houjin.gif
368 ms
bnr_mobileqr.gif
192 ms
anime_banner.jpg
193 ms
slide06.png
878 ms
slide04.jpg
1038 ms
slide02.png
813 ms
icon01.png
366 ms
icon02.png
392 ms
icon03.png
547 ms
movie_PC.png
547 ms
movie_SP.png
939 ms
movie_riyou.png
980 ms
all.js
114 ms
bg_head.gif
705 ms
bg_h1.png
856 ms
bg_logo.png
961 ms
btn_search.gif
1015 ms
arrow02.gif
1032 ms
bg_main.gif
1102 ms
google_custom_search_watermark.gif
163 ms
collect
79 ms
collect
79 ms
bg_gnavi.gif
1020 ms
bg_tel.gif
1033 ms
bg_info.gif
1074 ms
bg_movie.gif
1077 ms
bg_portmap.gif
1118 ms
252 ms
widgets.js
148 ms
plusone.js
148 ms
arrow01.png
1125 ms
pagination.png
1025 ms
124 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
213 ms
cb=gapi.loaded_0
51 ms
cb=gapi.loaded_1
98 ms
fastbutton
146 ms
xd_arbiter.php
91 ms
xd_arbiter.php
185 ms
like.php
96 ms
postmessageRelay
107 ms
cb=gapi.loaded_0
73 ms
cb=gapi.loaded_1
62 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
212 ms
rU2ubZ6l1Q5.js
272 ms
LVx-xkvaJ0b.png
279 ms
api.js
153 ms
core:rpc:shindig.random:shindig.sha1.js
209 ms
2536007149-postmessagerelay.js
183 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
128 ms
jot
91 ms
common.js
765 ms
map.js
765 ms
overlay.js
72 ms
topportnavi.json
602 ms
StaticMapService.GetMapImage
425 ms
util.js
24 ms
onion.js
73 ms
openhand_8_8.cur
60 ms
ViewportInfoService.GetViewportInfo
175 ms
stats.js
40 ms
controls.js
29 ms
transparent.png
119 ms
css
125 ms
A01.jpg
360 ms
A02.jpg
364 ms
A03.jpg
363 ms
A04.jpg
363 ms
A05.jpg
524 ms
A06.jpg
482 ms
A07.jpg
594 ms
A08.jpg
786 ms
A09.jpg
630 ms
A1-10.jpg
786 ms
B01.jpg
675 ms
B02.jpg
869 ms
B03.jpg
742 ms
B04.jpg
788 ms
B05.jpg
849 ms
B06.jpg
1187 ms
B07.jpg
1099 ms
B08.jpg
940 ms
B09.jpg
1097 ms
B11.jpg
1581 ms
B12.jpg
1385 ms
A2-13.jpg
1254 ms
DS_B01.jpg
1410 ms
C01.jpg
1255 ms
C02.jpg
1333 ms
C03.jpg
1412 ms
C04.jpg
1411 ms
C05.jpg
1479 ms
C07.jpg
1556 ms
C08.jpg
1564 ms
C09.jpg
1566 ms
C10.jpg
1568 ms
C11.jpg
1628 ms
C12.jpg
1730 ms
C13.jpg
1719 ms
google4.png
72 ms
mapcnt6.png
47 ms
sv5.png
49 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
39 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
38 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
100 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
101 ms
tmapctrl.png
32 ms
vt
100 ms
vt
175 ms
tmapctrl4.png
75 ms
vt
73 ms
vt
163 ms
vt
181 ms
vt
165 ms
vt
73 ms
vt
72 ms
vt
180 ms
vt
191 ms
marker.js
36 ms
C14.jpg
1384 ms
C15.jpg
1541 ms
A3-16.jpg
1598 ms
A3-17.jpg
1582 ms
A3-18.jpg
1693 ms
AuthenticationService.Authenticate
283 ms
vt
111 ms
vt
16 ms
vt
17 ms
vt
17 ms
vt
83 ms
vt
98 ms
vt
20 ms
DS_C01.jpg
1571 ms
DS_C02.jpg
1589 ms
D01.jpg
1467 ms
D02.jpg
1463 ms
D03.jpg
1452 ms
D04.JPG
1635 ms
D05.jpg
1593 ms
DS_D01.jpg
1592 ms
DS_D02.jpg
1601 ms
DS_D03.jpg
1608 ms
E02.jpg
1641 ms
E03.jpg
1908 ms
F01.jpg
1439 ms
F02.jpg
1435 ms
F04.jpg
1352 ms
F06.jpg
1546 ms
F07.jpg
1616 ms
F08.jpg
1521 ms
F09.jpg
1632 ms
F10.jpg
1581 ms
port.png
1564 ms
port1.png
1591 ms
yujin.png
1530 ms
mujin.png
1495 ms
kiosk.png
1581 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.
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
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: