Report Summary

  • 71

    Performance

    Renders faster than
    82% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

jibushaka.com

書籍「なぜ君たちは 就活になると みんな同じようなことばかり しゃべりだすのか。-ジブンの本当の価値を伝える技術」

Page Load Speed

4.8 sec in total

First Response

804 ms

Resources Loaded

3.6 sec

Page Rendered

347 ms

jibushaka.com screenshot

About Website

Welcome to jibushaka.com homepage info - get ready to check Jibushaka best content for Japan right away, or after learning these important things about jibushaka.com

2012年の開講以来、たくさんの大学生と仕事との出会いを支援してきたプログラムがこのたび書籍化しました。

Visit jibushaka.com

Key Findings

We analyzed Jibushaka.com page load time and found that the first response time was 804 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

jibushaka.com performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.1 s

75/100

10%

Network Requests Diagram

jibushaka.com

804 ms

import.css

384 ms

main_img.png

1533 ms

reset.css

194 ms

basefont.css

196 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 76% of them (22 requests) were addressed to the original Jibushaka.com, 10% (3 requests) were made to Platform.twitter.com and 7% (2 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 Jibushaka.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 26.9 kB (12%)

Content Size

232.9 kB

After Optimization

206.0 kB

In fact, the total size of Jibushaka.com main page is 232.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 220.4 kB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 4.2 kB

  • Original 7.0 kB
  • After minification 7.0 kB
  • After compression 2.8 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 4.2 kB or 60% of the original size.

Image Optimization

-9%

Potential reduce by 19.0 kB

  • Original 220.4 kB
  • After minification 201.4 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. Jibushaka images are well optimized though.

CSS Optimization

-68%

Potential reduce by 3.7 kB

  • Original 5.5 kB
  • After minification 4.1 kB
  • After compression 1.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. Jibushaka.com needs all CSS files to be minified and compressed as it can save up to 3.7 kB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (11%)

Requests Now

28

After Optimization

25

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

Accessibility Review

jibushaka.com accessibility score

88

Accessibility Issues

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

jibushaka.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

jibushaka.com SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jibushaka.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Jibushaka.com 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

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