17.9 sec in total
971 ms
16.5 sec
422 ms
Click here to check amazing Start Line content for Japan. Otherwise, check out these important facts you probably never knew about start-line.co.jp
中央区・湾岸エリアの賃貸/管理/購入/売却など不動産に関することならスタートラインへご相談ください。中央区を中心とした湾岸エリアに直営店を16店舗展開中。暮らしのコンシェルジュをスローガンに不動産に関することをトータル的にサポートしてまいります。
Visit start-line.co.jpWe analyzed Start-line.co.jp page load time and found that the first response time was 971 ms and then it took 16.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
start-line.co.jp performance score
name
value
score
weighting
Value11.1 s
0/100
10%
Value19.8 s
0/100
25%
Value17.3 s
0/100
10%
Value420 ms
65/100
30%
Value0
100/100
15%
Value12.0 s
16/100
10%
971 ms
3452 ms
348 ms
539 ms
26 ms
Our browser made a total of 254 requests to load all elements on the main page. We found that 51% of them (130 requests) were addressed to the original Start-line.co.jp, 18% (46 requests) were made to D3e25kotnzlv99.cloudfront.net and 4% (11 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Start-line.co.jp.
Page size can be reduced by 1.2 MB (22%)
5.3 MB
4.1 MB
In fact, the total size of Start-line.co.jp main page is 5.3 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. 80% 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 3.7 MB which makes up the majority of the site volume.
Potential reduce by 75.5 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 75.5 kB or 78% of the original size.
Potential reduce by 122.2 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. Start Line images are well optimized though.
Potential reduce by 885.1 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 885.1 kB or 64% of the original size.
Potential reduce by 93.1 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. Start-line.co.jp needs all CSS files to be minified and compressed as it can save up to 93.1 kB or 79% of the original size.
Number of requests can be reduced by 112 (46%)
244
132
The browser has sent 244 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Start Line. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 63 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
start-line.co.jp
971 ms
www.start-line.co.jp
3452 ms
import.css
348 ms
index.css
539 ms
js
26 ms
jquery.js
1083 ms
common.js
563 ms
jquery.lazyload.js
378 ms
jquery.flexslider.js
1234 ms
index.js
739 ms
default.css
570 ms
utility.css
747 ms
style.css
932 ms
print.css
746 ms
widgets.js
55 ms
site.css
1107 ms
flexslider.css
901 ms
si.js
55 ms
bookmark_button.js
395 ms
widgets.js
84 ms
conversion.js
19 ms
analytics.js
17 ms
sr.gif
552 ms
120694_710_112.jpg
2868 ms
button-only.gif
206 ms
logo_blank_off.jpg
551 ms
text_head_time.jpg
425 ms
text_head_tel.jpg
552 ms
btn_contact_mail_off.jpg
426 ms
btn_subnavi_history_off.jpg
441 ms
btn_subnavi_my_list_off.jpg
430 ms
btn_subnavi_store_off.jpg
776 ms
btn_subnavi_new_off.jpg
786 ms
btn_global_navi_rent01_home_off.jpg
809 ms
btn_global_navi_rent02_about_off.jpg
808 ms
btn_global_navi_rent03_area_off.jpg
924 ms
btn_global_navi_rent04_route_off.jpg
924 ms
btn_global_navi_rent05_map_off.jpg
1257 ms
btn_global_navi_search_off.png
1257 ms
img_main01.jpg
1729 ms
img_main02_off.jpg
2281 ms
btn_main_area_off.png
1359 ms
btn_main_route_off.png
1359 ms
btn_main_map_off.png
1541 ms
60x60_93238311a064553e1c11daf9e52d85c1.jpg
1542 ms
60x60_f20def91f304ce45b8ce38aef87ed636.jpg
1634 ms
60x60_a679de03af575f92cffccb650e71dd5b.jpg
1727 ms
60x60_9ce9a5861599c52dae1527358a8d10f4.jpg
1911 ms
60x60_60c5617081966c18175db6253275229d.jpg
1912 ms
60x60_487991a3a9ed4666d2f7b234008e4150.jpg
2004 ms
60x60_1ed36654a677bcd972d34764f9da9565.jpg
2004 ms
60x60_20663a254e071797d9e8ad9f9c090d4e.jpg
2095 ms
60x60_0069887ccc9599440bd8caf5d77d11eb.jpg
2461 ms
60x60_b65e1b34acc0c5e3970523883898db34.jpg
2279 ms
60x60_80b1e05ee09c96d0d064e394e7fe39ba.jpg
2368 ms
60x60_736541a1f6878d2c90d1ed4073891473.jpg
2460 ms
60x60_9e975eeb6a780b94ed2f444473e02af0.jpg
2460 ms
60x60_0dd81318adf2d2f6bbb374537264eb4c.jpg
2659 ms
60x60_836bf402145dfe7a7013588c458ae794.jpg
2660 ms
60x60_bb908ba6e145cb0532539e93c6290360.jpg
2753 ms
all.js
26 ms
60x60_7f7c0b44c8ee5f40526c163b75cafbde.jpg
2747 ms
smarticon
37 ms
collect
19 ms
Tn9
125 ms
457 ms
xd_arbiter.php
79 ms
xd_arbiter.php
120 ms
491 ms
plusone.js
202 ms
common.js
56 ms
map.js
69 ms
util.js
95 ms
marker.js
68 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
259 ms
StaticMapService.GetMapImage
257 ms
reset-3.3.0.css
133 ms
jquery-ui-1.10.3.custom.min-f0d57462d9adb8182bd95cab39f0efba.css
159 ms
jquery.pnotify.default-c2b4a5560b5ef39a1c7b88614feeed7c.css
166 ms
jquery.pnotify.default.icons-eeef7d45d83b2e5c30359fb7cea8bb2a.css
157 ms
jquery.pnotify.custom.org-d8401ec73c734e82e8f8bad96a09b3b4.css
166 ms
application-6609a2bab946f8dfd043b8ed75dff170.css
166 ms
base-402b6a8a77ae3a46761ccd1e2b92a1dd.css
234 ms
css
174 ms
application-f643636901b514ee44e56fbedd092be5.css
235 ms
navigation-b5b0698ecbf0ad5bcb111e51351a0ddc.css
235 ms
spheres_desktop-1f769777a44e3a9a24f70eb6cbd57dae.css
240 ms
jquery-1.10.2.min.js
239 ms
jquery.preload.min.js
238 ms
json2_20110223.min.js
260 ms
jstorage-0.3.0.min.js
261 ms
jquery.cookie-1.3.1.min.js
260 ms
jquery.mousewheel-3.0.6.min.js
262 ms
jquery.maxlength-1.2.min.js
281 ms
jquery.ah-placeholder-1.2.min.js
280 ms
jquery.textchange_20100604.min.js
281 ms
jquery.ba-outside-events-1.1.min.js
281 ms
jquery-ui-1.10.3.custom.min-736b6170a9c7c8e92e7830b81ad93f53.js
285 ms
jquery.pnotify.min-d4807d061413bcf1a9f52b575e6b83f9.js
282 ms
jquery.fullscreen-1.1.5.min.js
283 ms
application-2fd16db6e66ab147fc596aa399331c6d.js
283 ms
application-70429123ea7bd5b606c2da5d594ecd41.js
282 ms
three-74.min.js
357 ms
three-73.projector.min.js
283 ms
three-73.canvas_renderer.min.js
354 ms
sphere_viewer_camera_fov_adjuster-c78d6d19bcb2defa2aa6c063fbf5a31b.js
353 ms
sphere_viewer-ff829e8571cee6547aceed1a421f1125.js
355 ms
sphere_viewer_desktop-f466d26a48895508de73a5c44630fc71.js
353 ms
spheres_show-de5e74526352a79689c66ad39261041f.js
354 ms
jquery_ujs-649c53254c215bfc93d9898c7f29b85a.js
380 ms
analytics-06653c3ef15f847a2ab1f4be8332a33a.js
381 ms
logo_embed-bb74f0a1dc50672dbccf58bf637e8e45.png
380 ms
onion.js
36 ms
openhand_8_8.cur
78 ms
ViewportInfoService.GetViewportInfo
72 ms
stats.js
29 ms
controls.js
36 ms
spotlight-poi.png
76 ms
css
58 ms
transparent.png
42 ms
google4.png
37 ms
mapcnt6.png
38 ms
sv5.png
52 ms
221 ms
cb=gapi.loaded_0
34 ms
cb=gapi.loaded_1
118 ms
fastbutton
215 ms
btn_plus_normal-e8c2220cc9fa0ccc25ccfc4413db3634.png
254 ms
vt
82 ms
vt
78 ms
btn_minus_normal-b906a9a48dfe6bff7b5d9e68d377ed9c.png
259 ms
reset_normal-9a8df7d980c9d993c1e97bd75154fc4c.png
259 ms
like.php
415 ms
vt
101 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
61 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
63 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
63 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
64 ms
60x60_31ff170491d845a6e0eb10ec1dcc264c.jpg
2333 ms
60x60_9e9ef45fe80c715609bc9dbaecb4815f.jpg
2438 ms
60x60_d730fc849a26a6cf76c574b4ac1e55a6.jpg
2527 ms
in_progress_animation-375d303aeb661e309e8de53e94c2af01.gif
169 ms
naiken.jpg
2992 ms
AuthenticationService.Authenticate
266 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
151 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
172 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
171 ms
postmessageRelay
177 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
127 ms
cb=gapi.loaded_0
65 ms
cb=gapi.loaded_1
64 ms
text_welcome.jpg
2884 ms
photo_welcome.png
2973 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
64 ms
ASP_Conf.js
684 ms
analytics.js
103 ms
equirectangular_web_optimized
248 ms
btn_plus_over-f8e88e1b2c32cc115f098e9639a4f797.png
37 ms
btn_plus_down-d7b6d82f9864916244a8b7f8af133397.png
36 ms
btn_minus_over-17aaaa0b6f26db862cff3e7cc8056dd7.png
36 ms
btn_minus_down-a938aa79f18c3494a14f8a9da65463b5.png
36 ms
reset_over-4fc50547689e79b06977d393f092212c.png
42 ms
reset_down-33aca1fbc9528d812cdd52b7bea821ce.png
45 ms
reset.css
36 ms
entry-button.css
34 ms
button-counter.gif
3 ms
3193398744-postmessagerelay.js
27 ms
rpc:shindig_random.js
31 ms
cb=gapi.loaded_0
5 ms
dc.js
104 ms
jot
168 ms
qeKvIRsJabD.js
52 ms
LVx-xkvaJ0b.png
50 ms
icon_new01.png
2366 ms
335x200_15192dcdb9bb6a34d379bbe6ba32e87f.jpg
3190 ms
__utm.gif
19 ms
icon_360_01.png
3082 ms
335x200_6f3691a7686fe223a694f15ad8b28ef5.jpg
3345 ms
icon_new02.png
2863 ms
215x130_661d992863ed9f565c17547b9a20cb0b.jpg
3415 ms
215x130_023e546dbec790b92347c7e089b28186.jpg
2991 ms
215x130_2c7a7feb34bd3ce14583fb6c67fe1436.jpg
3454 ms
[sr].gif
375 ms
emd_pt.js
469 ms
215x130_5b608ed8e4c84c477989591342dca6f6.jpg
3160 ms
215x130_dd25b976fe8309c39ecb008bcc9592c2.jpg
3530 ms
215x130_52944e7017b4b9cb00dbddd99f12cfa8.jpg
3348 ms
icon_new03.png
3068 ms
HTTP_s.js
930 ms
icon_360_02.png
3615 ms
155x95_a732a014dda5e3ca06c8dfb4a18e03b5.jpg
3523 ms
155x95_f23dd6838c3e1ff10fc5013e833691ee.jpg
3649 ms
155x95_03e1c39a22803a0c19fdece74a1af3b6.jpg
3556 ms
155x95_d6e0c006f553ecdbd0d68fa7cc13b511.jpg
3734 ms
155x95_989e2c35b9d8f9c469d2ba1a680122d6.jpg
3555 ms
155x95_737940f93aaf0b3e3e358dce7812d0a5.jpg
3922 ms
155x95_343b06e5f4c396455c0a588042088608.jpg
3924 ms
155x95_57c9fd8b2fe5a06ba0a23928ded27739.jpg
3739 ms
155x95_7585ad077df40f7a4167e7dd183327da.jpg
3837 ms
155x95_510e00ef5d4c96ae1ecad937d740718b.jpg
3927 ms
155x95_e760563f9de2f47bff008514b8b70d7e.jpg
3836 ms
155x95_ce797aa3576bad72b7da9824f2d3fd26.jpg
4197 ms
banner_slogan_off.jpg
4672 ms
btn_side_all_off.jpg
3727 ms
btn_rss_off.jpg
3817 ms
btn_side_contact_off.jpg
4650 ms
banner_recuest_off.jpg
4378 ms
st.php
579 ms
banner_owners_off.jpg
4735 ms
theta_banner_off.jpg
4541 ms
pdficon.jpg
4072 ms
banner_voice_off.jpg
4531 ms
banner_report_off.jpg
4330 ms
free_dial.gif
4061 ms
banner_recruit_off.jpg
4595 ms
sst.php
366 ms
21000687_75_JP.gif
3974 ms
btn_page_top_off.jpg
3959 ms
series.jpg
3874 ms
parkhouse_logo_off.jpg
4049 ms
log_run.php
362 ms
parkaxis_logo_off.jpg
4062 ms
residia_logo_off.jpg
3971 ms
brillia_logo_off.jpg
3882 ms
proud_logo_off.jpg
3879 ms
branz_logo_off.jpg
4137 ms
and_more_off.jpg
3695 ms
text_foot_page_about.jpg
3780 ms
text_foot_site_about.jpg
3423 ms
text_foot_contact.jpg
3510 ms
foot_contact.jpg
3731 ms
QuotaService.RecordEvent
90 ms
btn_contact_foot_off.jpg
3641 ms
text_foot_search.jpg
3463 ms
text_foot_contents.jpg
3461 ms
copyright.jpg
3357 ms
bg_gnavi_search.png
3178 ms
bg_main.jpg
4620 ms
bg_img_shadow.png
3354 ms
img_main03.jpg
4706 ms
icon_h2_side.jpg
3174 ms
bg_new_box_first.jpg
3170 ms
bg_item_box.gif
3165 ms
loading.gif
3167 ms
bg_h2_shadow.jpg
2800 ms
icon_arw.jpg
2782 ms
icon_arw_foot.jpg
2870 ms
fb.png
2774 ms
hatena.png
2774 ms
twitter.png
2777 ms
gplus.png
2864 ms
s.gif
2865 ms
btn_main_previous_off.png
2776 ms
btn_main_next_off.png
2879 ms
start-line.co.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-hidden="true"] elements contain focusable descendents
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
start-line.co.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
start-line.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Start-line.co.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 Start-line.co.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.
start-line.co.jp
Open Graph description is not detected on the main page of Start Line. 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: