Tools & Wizards About Us
jincha.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

jincha.jp

ジンサポ！ぎふ

Page Load Speed

15.8 sec in total

First Response

796 ms

Resources Loaded

14.7 sec

Page Rendered

278 ms

jincha.jp screenshot

About Website

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

「ジンサポ！ぎふ」は岐阜県内企業の人材確保と若者の県内定着促進を図るために設立された、岐阜県中小企業総合人材センターの情報発信を行うためのポータルサイトです。

Visit jincha.jp

Key Findings

We analyzed Jincha.jp page load time and found that the first response time was 796 ms and then it took 15 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

jincha.jp performance score

0

Network Requests Diagram

jincha.jp

796 ms

www.jincha.jp

979 ms

www.jinzai-gifu.jp

5519 ms

gtm.js

114 ms

gtm.js

132 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Jincha.jp, 71% (60 requests) were made to Jinzai-gifu.jp and 8% (7 requests) were made to Jinchare.jinzai-gifu.jp. The less responsive or slowest element that took the longest time to load (5.5 sec) relates to the external source Jinzai-gifu.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 501.7 kB (17%)

Content Size

2.9 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 35.0 kB

  • Original 43.9 kB
  • After minification 40.3 kB
  • After compression 8.9 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 35.0 kB or 80% of the original size.

Image Optimization

-15%

Potential reduce by 386.0 kB

  • Original 2.6 MB
  • After minification 2.2 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. Obviously, Jincha needs image optimization as it can save up to 386.0 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-37%

Potential reduce by 39.7 kB

  • Original 108.6 kB
  • After minification 108.6 kB
  • After compression 68.8 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 39.7 kB or 37% of the original size.

CSS Optimization

-32%

Potential reduce by 40.9 kB

  • Original 129.7 kB
  • After minification 129.6 kB
  • After compression 88.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. Jincha.jp needs all CSS files to be minified and compressed as it can save up to 40.9 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (48%)

Requests Now

79

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jincha.jp

jincha.jp

796 ms

www.jincha.jp

www.jincha.jp

979 ms

www.jinzai-gifu.jp

www.jinzai-gifu.jp

5519 ms

gtm.js

gtm.js

114 ms

gtm.js

gtm.js

132 ms

js

js

139 ms

fbevents.js

fbevents.js

72 ms

lt.js

lt.js

165 ms

ebe8c679c2.js

ebe8c679c2.js

132 ms

css2

css2

108 ms

basic.css

basic.css

498 ms

common.css

common.css

501 ms

common2021.css

common2021.css

503 ms

style.css

style.css

858 ms

style2021.css

style2021.css

518 ms

style2021_T.css

style2021_T.css

525 ms

style2021_H.css

style2021_H.css

991 ms

companiesvideo.css

companiesvideo.css

1012 ms

index.css

index.css

1016 ms

index2021.css

index2021.css

1045 ms

monthly.css

monthly.css

1053 ms

jquery.bxslider.css

jquery.bxslider.css

1370 ms

colorbox.css

colorbox.css

1480 ms

style.css

style.css

1511 ms

style.min.css

style.min.css

1715 ms

frontend.css

frontend.css

1556 ms

jquery.min.js

jquery.min.js

101 ms

common_func.js

common_func.js

1564 ms

spmenuopen.js

spmenuopen.js

1895 ms

pagetop.js

pagetop.js

2008 ms

companiesvideo.js

companiesvideo.js

2026 ms

jquery.bxslider.js

jquery.bxslider.js

2230 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

2059 ms

create_calendar.js

create_calendar.js

2207 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

2414 ms

frontend.min.js

frontend.min.js

2513 ms

remodal.js

remodal.js

2521 ms

jquery.matchHeight.js

jquery.matchHeight.js

2572 ms

aos.css

aos.css

99 ms

js

js

121 ms

ajaxzip3.js

ajaxzip3.js

96 ms

aos.js

aos.js

99 ms

aos.css

aos.css

24 ms

aos.js

aos.js

54 ms

err.gif

err.gif

672 ms

whhg.css

whhg.css

2372 ms

ab7012ea24d0e0076728fb8e486ab294.jpg

ab7012ea24d0e0076728fb8e486ab294.jpg

1874 ms

da4187947068149351dfe1fd697ba0e8.jpg

da4187947068149351dfe1fd697ba0e8.jpg

1553 ms

66c19942ab4ba346fdb64ccc04cde373.png

66c19942ab4ba346fdb64ccc04cde373.png

2277 ms

1a9d6b560bacfd066fe8bcc4d993fc6b.png

1a9d6b560bacfd066fe8bcc4d993fc6b.png

1290 ms

b9ff17fda7c08a0151d595550181c68f.png

b9ff17fda7c08a0151d595550181c68f.png

1250 ms

d1c6e75ea8a94612b12effac7acca6e7.jpg

d1c6e75ea8a94612b12effac7acca6e7.jpg

1076 ms

c97ecdf60f7fb5eee89d9aa7c8b6bc57.png

c97ecdf60f7fb5eee89d9aa7c8b6bc57.png

2149 ms

logo_h.gif

logo_h.gif

267 ms

newwindow.png

newwindow.png

178 ms

bg_fixed_menu.png

bg_fixed_menu.png

508 ms

fixed_logo.png

fixed_logo.png

850 ms

jinchare_jobseeker.gif

jinchare_jobseeker.gif

536 ms

jinchare_student.gif

jinchare_student.gif

535 ms

jinsapo02.gif

jinsapo02.gif

702 ms

shogakukin002.gif

shogakukin002.gif

947 ms

banar_gifu_220531h300w300.png

banar_gifu_220531h300w300.png

1732 ms

f56c047c330fae66a7b4eee911edeacc.jpg

f56c047c330fae66a7b4eee911edeacc.jpg

1689 ms

fcf7cf1bf92428099d53966637bde1d3.jpg

fcf7cf1bf92428099d53966637bde1d3.jpg

1751 ms

link002.jpg

link002.jpg

1381 ms

link003.jpg

link003.jpg

1522 ms

link004.jpg

link004.jpg

1607 ms

link005.jpg

link005.jpg

2064 ms

link006.jpg

link006.jpg

2043 ms

link007.jpg

link007.jpg

2259 ms

link008.jpg

link008.jpg

2182 ms

link009.jpg

link009.jpg

2241 ms

link010.jpg

link010.jpg

2266 ms

link013.jpg

link013.jpg

2538 ms

4e16f884df3ec175f44df7cb7ee52160.png

4e16f884df3ec175f44df7cb7ee52160.png

2722 ms

d7ae731fd247fa2a487b1b77d902f279.png

d7ae731fd247fa2a487b1b77d902f279.png

2862 ms

50f78fbbf3a48e6496cffbdb895e2092.jpg

50f78fbbf3a48e6496cffbdb895e2092.jpg

3772 ms

link_item02.png

link_item02.png

2763 ms

logo_f.gif

logo_f.gif

2786 ms

pagetop_mark.gif

pagetop_mark.gif

3016 ms

monthly_events.php

monthly_events.php

3978 ms

TCM_____.woff

TCM_____.woff

3320 ms

webhostinghub-glyphs.ttf

webhostinghub-glyphs.ttf

4359 ms

bg_fixed_mail.png

bg_fixed_mail.png

3249 ms

SEO Factors

jincha.jp SEO score

0

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 Jincha.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 Jincha.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

jincha.jp

Open Graph description is not detected on the main page of Jincha. 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: