7 sec in total
548 ms
5.8 sec
691 ms
Visit ooimachi.jp now to see the best up-to-date Ooimachi content for Japan and also check out these interesting facts you probably never knew about ooimachi.jp
大井町ポータルサイト。東京都品川区大井町の情報ポータルサイトです。大井どんたく夏祭り、エンジョイウォークバル、美味シュラン、和酒スクラッチなどのイベント、グルメ・ショッピング・観光・ホテルなど商店街のお店情報を掲載。NPOまちづくり大井が運営。
Visit ooimachi.jpWe analyzed Ooimachi.jp page load time and found that the first response time was 548 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.
ooimachi.jp performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value22.5 s
0/100
25%
Value16.2 s
0/100
10%
Value1,730 ms
10/100
30%
Value0.483
17/100
15%
Value19.6 s
2/100
10%
548 ms
1015 ms
180 ms
358 ms
512 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 75% of them (79 requests) were addressed to the original Ooimachi.jp, 4% (4 requests) were made to Gstatic.com and 4% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Ooimachi.jp.
Page size can be reduced by 616.1 kB (11%)
5.4 MB
4.7 MB
In fact, the total size of Ooimachi.jp main page is 5.4 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 4.0 MB which makes up the majority of the site volume.
Potential reduce by 60.6 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 12.2 kB, which is 16% 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 60.6 kB or 80% of the original size.
Potential reduce by 13.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. Ooimachi images are well optimized though.
Potential reduce by 525.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 525.7 kB or 42% of the original size.
Potential reduce by 16.5 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. Ooimachi.jp needs all CSS files to be minified and compressed as it can save up to 16.5 kB or 32% of the original size.
Number of requests can be reduced by 34 (36%)
94
60
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ooimachi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
ooimachi.jp
548 ms
ooimachi.jp
1015 ms
style.css
180 ms
style.min.css
358 ms
styles.css
512 ms
styles.css
537 ms
generic-no-float.css
182 ms
loftloader.min.css
535 ms
jquery.min.js
723 ms
jquery-migrate.min.js
543 ms
jquery.min.js
30 ms
jquery.slicknav.min.js
543 ms
slick.min.js
683 ms
api.js
45 ms
all.css
41 ms
platform.js
34 ms
scripts.js
710 ms
jquery.form.min.js
711 ms
scripts.js
723 ms
loftloader.min.js
722 ms
reset.css
680 ms
slick-theme.css
716 ms
slick.css
717 ms
slicknav.css
727 ms
style.css
731 ms
contents.css
733 ms
wp-emoji-release.min.js
191 ms
sdk.js
163 ms
gtm.js
202 ms
recaptcha__en.js
189 ms
logo.png
300 ms
menu_sagasu.png
308 ms
menu_taberu.png
308 ms
menu_kaimono.png
301 ms
menu_service.png
309 ms
menu_tomaru.png
308 ms
menu_kankou.png
480 ms
menu_kinkyu.png
485 ms
menu_shoutengai.png
486 ms
slid_l_01.jpg
1025 ms
slid_l_02.jpg
1391 ms
slid_l_03.jpg
1210 ms
slid_l_04.jpg
1333 ms
slid_s_01.png
664 ms
slid_s_02.png
665 ms
slid_s_03.png
844 ms
slid_s_04.png
844 ms
240529-1.jpg
2098 ms
03.jpg
1733 ms
bn_dontaku_230607.jpg
1210 ms
bn_marche.jpg
1391 ms
bn_shizuoka_marche.gif
1393 ms
bn_event.jpg
1504 ms
2.jpg
1572 ms
IMG_3256.jpg
1757 ms
01-1.jpg
1574 ms
20211014_035321362_iOS_2-scaled.jpg
2028 ms
main_photo.jpg
1935 ms
bn_kikaku_ooiginza_guide.jpg
1756 ms
bn_kikaku_fotocon_bn2.jpg
1911 ms
bn_kikaku_konzyaku_bn.jpg
1938 ms
bn_kikaku_shashinkan_bn.jpg
1939 ms
bn_yasaikyoshitu.jpg
2095 ms
bn_gaiyou.jpg
2118 ms
bn_gaiyou_soft_2017.jpg
2068 ms
widgets.js
215 ms
embed
180 ms
sdk.js
10 ms
slick.woff
2078 ms
131 ms
js
82 ms
analytics.js
47 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
167 ms
bn_gaiyou_hard_2017.jpg
1904 ms
bn_gaiyou_16year.jpg
1972 ms
rs=ABjfnFVpLjW0I8EN2EGujCk4wnh-Cems-Q
159 ms
css
189 ms
js
183 ms
m=gmeviewer_base
183 ms
bn_fund.gif
1965 ms
bn_top_banner2.jpg
1997 ms
bn_ooimachi-kousou.gif
1996 ms
bn_top_banner.gif
2067 ms
collect
141 ms
settings
142 ms
bn_131206.jpg
1917 ms
access_rosen.gif
1972 ms
access_meyasu.gif
1971 ms
lazy.min.js
35 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
38 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
42 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
47 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
50 ms
pr_a_yawataya.jpg
1821 ms
pr_a_taisei.jpg
1821 ms
pr_a_kanbe.jpg
1702 ms
pr_a_yokado.jpg
1733 ms
pr_1_chiyoda.jpg
1607 ms
pr_1_azumakouji.jpg
1423 ms
pr_1_rentora.jpg
1454 ms
pr_2_goldsgym.jpg
1333 ms
pr_3_artom.jpg
1327 ms
ajax-loader.gif
1461 ms
slick.ttf
681 ms
slick.svg
259 ms
ooimachi.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 input fields do not have accessible names
ARIA toggle fields do not have accessible names
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
ooimachi.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
ooimachi.jp SEO score
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 Ooimachi.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 Ooimachi.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.
ooimachi.jp
Open Graph description is not detected on the main page of Ooimachi. 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: