Tools & Wizards About Us
hocci.or.jp screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

hocci.or.jp

東大阪商工会議所

Page Load Speed

7.4 sec in total

First Response

2 sec

Resources Loaded

5 sec

Page Rendered

370 ms

hocci.or.jp screenshot

About Website

Visit hocci.or.jp now to see the best up-to-date Hocci content and also check out these interesting facts you probably never knew about hocci.or.jp

東大阪商工会議所は、地域商工業の振興・発達に努力し、地域経済の活性化と新しい時代に対応するよう幅広く経営に役立つサービスを提供しています。

Visit hocci.or.jp

Key Findings

We analyzed Hocci.or.jp page load time and found that the first response time was 2 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

hocci.or.jp performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

7/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

hocci.or.jp

2009 ms

styles.css

627 ms

basic.css

629 ms

menudown.css

631 ms

menu.css

635 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 96% of them (87 requests) were addressed to the original Hocci.or.jp, 2% (2 requests) were made to Google.com and 1% (1 request) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Hocci.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 321.9 kB (18%)

Content Size

1.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hocci.or.jp main page is 1.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. 50% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 86.7 kB

  • Original 99.4 kB
  • After minification 88.7 kB
  • After compression 12.7 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 10.7 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 86.7 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 95.0 kB

  • Original 1.5 MB
  • After minification 1.4 MB

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. Hocci images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 121.8 kB

  • Original 195.3 kB
  • After minification 194.3 kB
  • After compression 73.5 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 121.8 kB or 62% of the original size.

CSS Optimization

-80%

Potential reduce by 18.4 kB

  • Original 22.9 kB
  • After minification 18.5 kB
  • After compression 4.6 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. Hocci.or.jp needs all CSS files to be minified and compressed as it can save up to 18.4 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (34%)

Requests Now

89

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hocci. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hocci.or.jp

hocci.or.jp

2009 ms

styles.css

styles.css

627 ms

basic.css

basic.css

629 ms

menudown.css

menudown.css

631 ms

menu.css

menu.css

635 ms

jquery-min.js

jquery-min.js

1157 ms

news_tab.js

news_tab.js

787 ms

pagetop.js

pagetop.js

797 ms

function.js

function.js

794 ms

jquery.min.js

jquery.min.js

1479 ms

styles.css

styles.css

947 ms

brand

brand

30 ms

brandjs.js

brandjs.js

17 ms

menudown.js

menudown.js

161 ms

js

js

90 ms

logo.gif

logo.gif

168 ms

submit_bt.gif

submit_bt.gif

163 ms

home_bt_over.gif

home_bt_over.gif

170 ms

sub_gn01.gif

sub_gn01.gif

161 ms

sub_gn02.gif

sub_gn02.gif

165 ms

sub_gn03.gif

sub_gn03.gif

262 ms

sub_gn04.gif

sub_gn04.gif

322 ms

top_annai50_2.jpg

top_annai50_2.jpg

822 ms

top_annai42_2.png

top_annai42_2.png

493 ms

top_annai53_2.png

top_annai53_2.png

334 ms

top_annai44.jpg

top_annai44.jpg

337 ms

top_annai56.png

top_annai56.png

421 ms

top_annai49_3.png

top_annai49_3.png

645 ms

top_annai52.png

top_annai52.png

502 ms

bn14.jpg

bn14.jpg

525 ms

bn11.png

bn11.png

583 ms

bn15.png

bn15.png

658 ms

bn01.jpg

bn01.jpg

669 ms

bn03.jpg

bn03.jpg

862 ms

bn04.jpg

bn04.jpg

743 ms

img01_1.gif

img01_1.gif

806 ms

img01_2.gif

img01_2.gif

823 ms

img01_3.gif

img01_3.gif

837 ms

img01_4.gif

img01_4.gif

905 ms

img01_5.gif

img01_5.gif

966 ms

img01_6.gif

img01_6.gif

982 ms

img01_7.gif

img01_7.gif

987 ms

img01_8.gif

img01_8.gif

1004 ms

img01_9.gif

img01_9.gif

1032 ms

img01_10.gif

img01_10.gif

1065 ms

img01_11.gif

img01_11.gif

1127 ms

img01_12.png

img01_12.png

1143 ms

img02.gif

img02.gif

1151 ms

mem01.jpg

mem01.jpg

1847 ms

index.html

index.html

1185 ms

branding.png

branding.png

46 ms

mem02.gif

mem02.gif

1111 ms

bn20.png

bn20.png

1463 ms

bn24.png

bn24.png

1307 ms

bn02.jpg

bn02.jpg

1156 ms

bn10.png

bn10.png

1209 ms

bn08.png

bn08.png

1223 ms

bn07.png

bn07.png

1243 ms

bn19.jpg

bn19.jpg

1224 ms

bn12.jpg

bn12.jpg

1538 ms

bn22.png

bn22.png

1455 ms

f_img01.jpg

f_img01.jpg

1249 ms

icon01_1.gif

icon01_1.gif

1233 ms

icon01_2.gif

icon01_2.gif

1283 ms

icon01_3.gif

icon01_3.gif

1311 ms

icon02_1.png

icon02_1.png

1313 ms

img05_1.jpg

img05_1.jpg

1460 ms

bg01.png

bg01.png

2259 ms

mem_icon01.png

mem_icon01.png

1331 ms

mem_icon02.png

mem_icon02.png

1275 ms

icon01_4.png

icon01_4.png

1227 ms

f_img01_1.gif

f_img01_1.gif

1244 ms

f_img01_2.gif

f_img01_2.gif

1342 ms

f_img01_3.gif

f_img01_3.gif

1349 ms

f_img01_4.gif

f_img01_4.gif

1332 ms

f_img01_5.gif

f_img01_5.gif

1330 ms

f_img01_6.gif

f_img01_6.gif

1298 ms

f_img01_7.gif

f_img01_7.gif

1347 ms

f_img01_8.gif

f_img01_8.gif

1366 ms

f_img01_9.gif

f_img01_9.gif

1351 ms

f_img01_10.gif

f_img01_10.gif

1372 ms

f_img01_11.gif

f_img01_11.gif

1360 ms

f_img01_12.gif

f_img01_12.gif

1367 ms

f_img01_13.gif

f_img01_13.gif

1377 ms

f_img01_14.gif

f_img01_14.gif

1365 ms

pagetop.gif

pagetop.gif

1371 ms

bn06.jpg

bn06.jpg

1357 ms

bn11_2.png

bn11_2.png

1341 ms

bn19.png

bn19.png

1304 ms

bn21.jpg

bn21.jpg

1299 ms

bn22_3.jpg

bn22_3.jpg

1280 ms

Accessibility Review

hocci.or.jp accessibility score

60

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

hocci.or.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hocci.or.jp SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hocci.or.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 Hocci.or.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.

Social Sharing Optimization

hocci.or.jp

Open Graph data is detected on the main page of Hocci. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: