8.1 sec in total
787 ms
6.9 sec
471 ms
Welcome to yokohamachintai.jp homepage info - get ready to check Yokohamachintai best content for Japan right away, or after learning these important things about yokohamachintai.jp
横浜で賃貸!早開業16年!ということで7月は割引多めに更新中! 仲介手数料無料物件はもちろんのこと、更に割引できる プラスアルファ割引も好評頂いております。
Visit yokohamachintai.jpWe analyzed Yokohamachintai.jp page load time and found that the first response time was 787 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
yokohamachintai.jp performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value13.3 s
0/100
25%
Value11.7 s
4/100
10%
Value210 ms
88/100
30%
Value0.948
3/100
15%
Value13.7 s
11/100
10%
787 ms
372 ms
6 ms
9 ms
297 ms
Our browser made a total of 179 requests to load all elements on the main page. We found that 64% of them (115 requests) were addressed to the original Yokohamachintai.jp, 8% (15 requests) were made to Maps.google.com and 6% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Yokohamachintai.jp.
Page size can be reduced by 731.0 kB (45%)
1.6 MB
888.3 kB
In fact, the total size of Yokohamachintai.jp main page is 1.6 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 856.7 kB which makes up the majority of the site volume.
Potential reduce by 49.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 49.5 kB or 79% of the original size.
Potential reduce by 205.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. Obviously, Yokohamachintai needs image optimization as it can save up to 205.0 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 370.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 370.7 kB or 64% of the original size.
Potential reduce by 105.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. Yokohamachintai.jp needs all CSS files to be minified and compressed as it can save up to 105.8 kB or 84% of the original size.
Number of requests can be reduced by 90 (53%)
169
79
The browser has sent 169 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yokohamachintai. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
yokohamachintai.jp
787 ms
import.black-turquoise_blue.css
372 ms
font-awesome.min.css
6 ms
jquery.min.js
9 ms
jquery.cookie.min.js
297 ms
application.js
299 ms
comparelist.black-turquoise_blue.js
375 ms
swfobject.js
299 ms
jquery.smooth.js
438 ms
jquery.placeholder.js
591 ms
jquery.simplemodal.min.js
592 ms
js
22 ms
map.js
592 ms
conversion.js
17 ms
reset.css
296 ms
base.css
299 ms
structure.css
363 ms
clearfix.css
517 ms
component.css
520 ms
prettyPhoto.css
517 ms
hack.css
587 ms
component.css
591 ms
ga.js
20 ms
lfg_baner125_125.gif
491 ms
wrapper-bg.gif
148 ms
logo.gif
328 ms
header_sub.gif
332 ms
btn-search.gif
301 ms
main.jpg
1088 ms
information_42.jpg
474 ms
icon_youtube.gif
446 ms
icon_zero.gif
595 ms
icon_pet.gif
623 ms
icon_tower.gif
625 ms
icon_chair.gif
740 ms
icon_new.gif
770 ms
icon_smile.gif
907 ms
icon_mansion.gif
915 ms
information_39.jpg
959 ms
information_40.jpg
1082 ms
information_21.jpg
1085 ms
information_45.jpg
1236 ms
information_15.gif
1270 ms
information_14.jpg
1283 ms
information4.jpg
1448 ms
information5.jpg
1432 ms
information2.gif
1422 ms
37808100020684e_01t.jpg
1558 ms
50642300020623e_01t.jpg
1608 ms
54103700020681e_01t.jpg
1623 ms
93464400020677e_01t.jpg
1744 ms
04150200020673e_01t.jpg
1758 ms
68239300002351e_01t.jpg
1796 ms
82526300000047e_01t.jpg
1896 ms
38598700000047e_01t.jpg
1947 ms
04185700000046e_01t.jpg
1948 ms
navF-information.gif
2038 ms
navF-SiteMap.gif
2052 ms
sdk.js
269 ms
black-wrapper-bg.gif
2079 ms
header_wrapper-bg.gif
2180 ms
__utm.gif
21 ms
likebox.php
143 ms
82 ms
fontawesome-webfont.woff
20 ms
collect
78 ms
81 ms
top.json
2203 ms
35 ms
ga-audiences
32 ms
33 ms
kyEKgjk51ZE.css
293 ms
xgj7bXhJNEH.css
355 ms
1kPfZUdGrka.js
490 ms
Yuj_Y8xNH2C.js
618 ms
Mpe38fuBVZ2.js
488 ms
n8qIhCw3vMx.js
487 ms
36 ms
header_bg.gif
1943 ms
xd_arbiter.php
209 ms
xd_arbiter.php
433 ms
update-bg.png
2010 ms
update-border-bg.png
2038 ms
navG-li-bg.gif
1993 ms
navG-li-bg-on.gif
2038 ms
search-bg.gif
1983 ms
w267-top-bg.gif
2011 ms
w267-line.gif
2018 ms
w267-bot-bg.gif
1907 ms
ico-C.gif
1915 ms
302012_452904608129736_26183356_n.jpg
565 ms
59922_453130221440508_872388973_n.jpg
656 ms
10632699_332985923529352_2474303843147402994_n.jpg
749 ms
12243588_1189571731057335_6532185023503260719_n.jpg
839 ms
10354686_10150004552801856_220367501106153455_n.jpg
764 ms
wL6VQj7Ab77.png
76 ms
s7jcwEQH7Sx.png
76 ms
w267-bot-bg2.gif
1879 ms
w267-mid-bg.gif
1923 ms
ico-rank1.gif
1967 ms
ico-rank2.gif
1855 ms
ico-rank3.gif
1857 ms
w133-line.gif
1892 ms
ico-rank4.gif
1843 ms
ico-rank5.gif
1860 ms
ico-rank6.gif
1937 ms
ico-rank7.gif
1809 ms
ico-rank8.gif
1804 ms
ico-rank9.gif
1824 ms
w134-line.gif
1816 ms
ico-rank10.gif
1816 ms
ico-rank11.gif
1891 ms
VXcANLwwL5J.js
68 ms
AmlxWlqMvlv.js
72 ms
ico-rank12.gif
1782 ms
ico-rank13.gif
1772 ms
ico-rank14.gif
1771 ms
ico-rank15.gif
1771 ms
w542-bot-bg.gif
1770 ms
w542-top-bg-1.gif
1860 ms
w542-line.gif
1781 ms
w542-mid-bg.gif
1773 ms
btn-list-news-n.gif
1772 ms
w542-line-dot.gif
1771 ms
ico-D.gif
1771 ms
w177-bot-bg.gif
1770 ms
common.js
12 ms
map.js
13 ms
util.js
12 ms
marker.js
12 ms
StaticMapService.GetMapImage
263 ms
w177-top-bg-1.gif
1753 ms
w177-line.gif
1756 ms
onion.js
31 ms
openhand_8_8.cur
19 ms
stats.js
15 ms
w177-mid-bg.gif
1723 ms
ViewportInfoService.GetViewportInfo
72 ms
controls.js
11 ms
transparent.png
36 ms
css
32 ms
ico-A_sm.gif
1748 ms
google4.png
26 ms
mapcnt6.png
44 ms
sv5.png
45 ms
tmapctrl.png
14 ms
cb_scout5.png
15 ms
tmapctrl4.png
15 ms
vt
98 ms
vt
113 ms
vt
106 ms
vt
97 ms
vt
88 ms
vt
59 ms
footer_wrapper-base-bg.gif
1736 ms
vt
141 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
8 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
18 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
18 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
18 ms
yokohama_50_208.png
1770 ms
kannai_39_126.png
1771 ms
ishikawacho_34_99.png
1772 ms
bandobashi_34_96.png
1771 ms
AuthenticationService.Authenticate
190 ms
tobe_34_95.png
1771 ms
koganecho_34_94.png
1770 ms
isezakichojamachi_32_81.png
1771 ms
sakuragicho_32_80.png
1771 ms
yoshinocho_32_75.png
1773 ms
hiranumabashi_32_72.png
1772 ms
motomachi-chukagai_32_67.png
1771 ms
higashikanagawa_32_65.png
1771 ms
yamate_32_64.png
1774 ms
tanmachi_32_63.png
1770 ms
shinyokohama_32_59.png
1773 ms
takashimacho_32_59.png
1771 ms
nishiyokohama_32_57.png
1772 ms
minamiota_32_54.png
1771 ms
yokohamachintai.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
button, link, and menuitem elements do not have accessible names.
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
yokohamachintai.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
yokohamachintai.jp SEO score
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 Yokohamachintai.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 Yokohamachintai.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.
yokohamachintai.jp
Open Graph data is detected on the main page of Yokohamachintai. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: