9.2 sec in total
2 sec
7.1 sec
181 ms
Welcome to pio-ota.jp homepage info - get ready to check Pio Ota best content for Japan right away, or after learning these important things about pio-ota.jp
高度な技術の集積を誇る大田区産業をより発展させるために、構造的変化に柔軟に対応できる実施組織として設立された大田区産業振興協会のホームページです。
Visit pio-ota.jpWe analyzed Pio-ota.jp page load time and found that the first response time was 2 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
pio-ota.jp performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value23.5 s
0/100
25%
Value12.6 s
3/100
10%
Value6,250 ms
0/100
30%
Value0.001
100/100
15%
Value18.3 s
3/100
10%
1989 ms
379 ms
570 ms
570 ms
400 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 98% of them (99 requests) were addressed to the original Pio-ota.jp, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Pio-ota.jp.
Page size can be reduced by 330.1 kB (27%)
1.2 MB
879.5 kB
In fact, the total size of Pio-ota.jp main page is 1.2 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. 30% of websites need less resources to load. Images take 840.7 kB which makes up the majority of the site volume.
Potential reduce by 50.1 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 6.9 kB, which is 11% 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 50.1 kB or 83% of the original size.
Potential reduce by 58.7 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. Pio Ota images are well optimized though.
Potential reduce by 175.3 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 175.3 kB or 69% of the original size.
Potential reduce by 46.0 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. Pio-ota.jp needs all CSS files to be minified and compressed as it can save up to 46.0 kB or 84% of the original size.
Number of requests can be reduced by 17 (17%)
100
83
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pio Ota. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
pio-ota.jp
1989 ms
cmn_reset.css
379 ms
cmn_style.css
570 ms
cmn_layout.css
570 ms
flexibleSearch.css
400 ms
jquery.bxslider.css
569 ms
top.css
599 ms
jquery.js
1407 ms
jquery.cookie140.js
758 ms
hashchange.js
756 ms
flexibleSearch.js
948 ms
ui.tabs.min.js
1039 ms
des.js
947 ms
blog_ajax_json_search.js
946 ms
common.js
746 ms
linkiconimg.js
745 ms
top.js
744 ms
jquery.bxslider.min.js
849 ms
ga.js
934 ms
analytics.js
26 ms
jigyou1602_thumb.jpg
1524 ms
logo_header.png
226 ms
btn_pio.png
225 ms
btn_kyousai.png
399 ms
btn_english.png
214 ms
btn_chinese.png
187 ms
icon_search.gif
222 ms
slide01.jpg
1849 ms
slide02.jpg
1655 ms
slide03.jpg
1856 ms
slide04.jpg
1946 ms
slide05.jpg
1748 ms
btn_mainmenu_01.png
784 ms
btn_mainmenu_02.png
1372 ms
btn_mainmenu_03.png
1594 ms
btn_mainmenu_04.png
1829 ms
btn_mainmenu_05.png
2054 ms
btn_mainmenu_06.png
2158 ms
text01.gif
2028 ms
text02.gif
2016 ms
img_top_sp.jpg
2846 ms
gMenu_sp_01.png
2362 ms
gMenu_sp_02.png
2182 ms
gMenu_sp_03.png
2217 ms
gMenu_sp_04.png
2249 ms
gMenu_sp_05.png
2372 ms
gMenu_sp_06.png
2356 ms
tab01s.png
2405 ms
tab01_sp.png
2437 ms
tab02s.png
2523 ms
tab02_sp.png
2562 ms
tab03s.png
2571 ms
tab03_sp.png
2594 ms
titleKanrenSite.gif
2625 ms
tabArrow.gif
2687 ms
tsuno.png
2770 ms
jigyou1603_thumb.jpg
1471 ms
titleShigotoSagasu.png
2960 ms
collect
12 ms
b3eventban.inc
2618 ms
b2footban.inc
2641 ms
b6include.inc
2752 ms
b7include.inc
2798 ms
titleSougyouShitai.png
2640 ms
titleNews.png
2244 ms
btn_rss.png
1807 ms
btn_news_ichiran.png
1588 ms
title_kyokai.png
1560 ms
banner_commerce.png
1450 ms
title_Event.png
1604 ms
markTokusyu.png
1531 ms
markJigyou.png
1534 ms
footer_btn_pagetop.png
1422 ms
bg_mainmenu_off.png
1386 ms
spr_tab_news.png
1672 ms
iconPageTop.png
1526 ms
btn_english_on.png
1429 ms
btn_chinese_on.png
1408 ms
btn_rss_on.png
1408 ms
btn_news_ichiran_on.png
1529 ms
loading.gif
1431 ms
search_close.png
1418 ms
outer.gif
1443 ms
excel.gif
1460 ms
pdf.gif
1542 ms
icon_information.png
1445 ms
icon_review.png
1424 ms
icon_residents.png
1441 ms
icon_event.png
1444 ms
eventBanner09.gif
742 ms
eventBanner05.png
616 ms
eventBanner02.png
710 ms
eventBanner04_1.png
862 ms
footBan01.png
532 ms
footBan02.png
600 ms
footBan09.png
707 ms
footBan03.png
999 ms
footBan10.png
1019 ms
footBan05.png
858 ms
footBan07.png
1092 ms
footBan08.jpg
888 ms
pio-ota.jp accessibility score
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.
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.
pio-ota.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
pio-ota.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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pio-ota.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 Pio-ota.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.
pio-ota.jp
Open Graph description is not detected on the main page of Pio Ota. 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: